Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am experiencing issues getting Bind9 to start.

Output from "tail /var/log/messages":

Aug 15 06:50:30 iceweb kernel: [125973.964184] type=1400 audit(1313409030.779:50): 
    apparmor="DENIED" operation="open" parent=7227 profile="/usr/sbin/named" 
    name="/var/lib/named/etc/bind/named.conf" pid=7229 comm="named" 
    requested_mask="r" denied_mask="r" fsuid=103 ouid=0

Also here is the output from "/etc/init.d/bind9/restart:

* Stopping domain name service... bind9 

rndc: connect failed: 127.0.0.1#953: connection refused [OK]

* Starting domain name service... bind9     [fail}

What could be wrong?

share|improve this question
    
That looks like an audti log entry from AppArmor. Something in your apparmor configuration is preventing named reading the named.conf file from its current location (Is it perhaps configured to allow it from a different path, perhaps?) –  SmallClanger Aug 15 '11 at 12:10

1 Answer 1

cmiiw, check you named.conf and make sure the zones directory, log, etc allowed (rw) on /etc/apparmor.d/usr.sbin.named

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.