1

Ever since I've upgraded to ubuntu 9.10, bind9 won't start:

Setting up bind9 (1:9.6.1.dfsg.P1-3ubuntu0.2) ...
 * Starting domain name service... bind9                                 [fail] 
invoke-rc.d: initscript bind9, action "start" failed.
dpkg: error processing bind9 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 bind9
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any ideas?

Overmind
  • 3,076
  • 2
  • 16
  • 25
Logikdev
  • 11
  • 1
  • 3

4 Answers4

2

Have you had the bind9 package installed before, done a non-purge removal and then afterwards removed files from /etc/bind/? If so, the solution is doing a full purge removal, allowing apt till reinstall configuration files)

$ sudo apt-get remove --purge bind9
$ sudo apt-get install bind9
andol
  • 6,938
  • 29
  • 43
0

try reinstall bind package

alexus
  • 13,112
  • 32
  • 117
  • 174
0

Found the solution, partially...

I had to remove a reference to bind9 in /etc/insserv.conf in order for the purge and re-install to work.

I say partially though because now sendmail isn't working and bind9 still wont correctly start. I'll post another seperate question as this may have more to do with my sendmail config than bind9.

Thanks for the help!

Logikdev
  • 11
  • 1
  • 3
0

Try starting bind with AppArmor off. If that works, you're probably experiencing this bug, like myself. Another hint would be a line like this in /var/log/syslog:

Dec 23 02:27:15 Pantheon kernel: [10704.337741] type=1503 audit(1261549635.405:346): operation="inode_permission" requested_mask="::r" denied_mask="::r" fsuid=116 name="/etc/ssl/openssl.cnf" pid=1383 profile="/usr/sbin/named"

You can try clearing the AppArmor cache directory (/etc/apparmor.d/cache), touching /etc/apparmor.d/usr.sbin.named, and making sure bind's apparmor config (/etc/apparmor.d/usr.sbin.named) contains the following:

# ssl
/etc/ssl/openssl.cnf r,

None of this worked for me, however. Even putting usr.sbin.named into the force-complain directory (where rules are only supposed to be noted, not enforced) and rebooting did not allow bind to run. The configuration is correct, but apparmor is still managing to enforce old, outdated configuration that prevents the new bind from running.

Until version 2.3.1+1403-0ubuntu27.3 of apparmor (karmic-proposed, urgency=low) hits the repositories, or unless you enable proposed updates, all you can do is disable apparmor.

HonoredMule
  • 187
  • 11