Bind9 can´t be actualized

Virtualmin
1

I have problem upgrading TWO virtualmin-debian servers. I alrady earlier found out that bind9 didn´t automatically restart on a server restart. But I found out that I can restart BIND on the Webmin-Interface manually. This did the job.

I don´t play around with the servers and have the same problem in two servers. So I think that this must be a known issue, but I didn´t find a solution on in the forum.

I would be glad to receive advise/help from someone who had the same problem.

Message from putty:

bind9 (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) wird eingerichtet (will be set up)
[FAIL] Starting domain name service…: bind9 failed!
invoke-rc.d: initscript bind9, action “start” failed.
dpkg: Fehler beim Bearbeiten von bind9 (–configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

((“dpkg: error on bind9 (–configure):
Subprocess installed post-installation-Skript showed the error 1”))

2

Howdy,

When you receive that message in Putty, do you see any BIND or named errors in /var/log/syslog?

I’m wondering if a more descriptive error is listed there that will help us figure out why that isn’t starting for you.

-Eric

3

Hi Eric

Thank you for your help and sorry for my late reply:

Here I send you the content of the logfile concerning Bind.

I hope, due to your experience you will be able to find the mistake.

Thank you in advance for your help.

Oct 15 05:33:26 hXXXXXXXX named[15476]: starting BIND 9.8.4-rpz2+rl005.12-P1 -u bind Oct 15 05:33:26 hXXXXXXXX named[15476]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' Oct 15 05:33:26 hXXXXXXXX named[15476]: ---------------------------------------------------- Oct 15 05:33:26 hXXXXXXXX named[15476]: BIND 9 is maintained by Internet Systems Consortium, Oct 15 05:33:26 hXXXXXXXX named[15476]: Inc. (ISC), a non-profit 501(c)(3) public-benefit Oct 15 05:33:26 hXXXXXXXX named[15476]: corporation. Support and training for BIND 9 are Oct 15 05:33:26 hXXXXXXXX named[15476]: available at https://www.isc.org/support Oct 15 05:33:26 hXXXXXXXX named[15476]: ---------------------------------------------------- Oct 15 05:33:26 hXXXXXXXX named[15476]: adjusted limit on open files from 4096 to 1048576 Oct 15 05:33:26 hXXXXXXXX named[15476]: found 1 CPU, using 1 worker thread Oct 15 05:33:26 hXXXXXXXX named[15476]: using up to 4096 sockets Oct 15 05:33:26 hXXXXXXXX named[15476]: loading configuration from '/etc/bind/named.conf' Oct 15 05:33:26 hXXXXXXXX named[15476]: reading built-in trusted keys from file '/etc/bind/bind.keys' Oct 15 05:33:26 hXXXXXXXX named[15476]: using default UDP/IPv4 port range: [1024, 65535] Oct 15 05:33:26 hXXXXXXXX named[15476]: using default UDP/IPv6 port range: [1024, 65535] Oct 15 05:33:26 hXXXXXXXX named[15476]: listening on IPv6 interfaces, port 53 Oct 15 05:33:26 hXXXXXXXX named[15476]: listening on IPv4 interface lo, 127.0.0.1#53 Oct 15 05:33:26 hXXXXXXXX named[15476]: listening on IPv4 interface venet0:0, 85.214.46.185#53 Oct 15 05:33:26 hXXXXXXXX named[15476]: generating session key for dynamic DNS Oct 15 05:33:26 hXXXXXXXX named[15476]: sizing zone task pool based on 7 zones Oct 15 05:33:26 hXXXXXXXX named[15476]: using built-in root key for view _default Oct 15 05:33:26 hXXXXXXXX named[15476]: set up managed keys zone for view _default, file 'managed-keys.bind' Oct 15 05:33:26 hXXXXXXXX named[15476]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 254.169.IN-ADDR.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: D.F.IP6.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 8.E.F.IP6.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 9.E.F.IP6.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: A.E.F.IP6.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: B.E.F.IP6.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Oct 15 05:33:26 hXXXXXXXX named[15476]: command channel listening on 127.0.0.1#953 Oct 15 05:33:26 hXXXXXXXX named[15476]: command channel listening on ::1#953 Oct 15 05:33:26 hXXXXXXXX named[15476]: isc_stdio_open '/var/log/bind/lamers.log' failed: permission denied Oct 15 05:33:26 hXXXXXXXX named[15476]: configuring logging: permission denied Oct 15 05:33:26 hXXXXXXXX named[15476]: loading configuration: permission denied Oct 15 05:33:26 hXXXXXXXX named[15476]: exiting (due to fatal error)
4

Howdy,

Hmm, it looks like you may be seeing a permissions problem.

What is the output of this command:

ls -la /var/log/bind/

5

Hi, thank you for your quick reply.

The output of the command is:

insgesamt 72
drwxr-xr-x 2 root root 4096 Okt 12 05:47 .

drwxr-xr-x 14 root root 4096 Okt 15 05:47 …

-rw-r–r-- 1 root root 2664 Okt 15 05:33 lamers.log

-rw-r–r-- 1 root root 0 Okt 5 05:47 lamers.log.1

-rw-r–r-- 1 root root 0 Sep 28 05:47 lamers.log.2

-rw-r–r-- 1 root root 56855 Sep 27 09:09 lamers.log.3

-rw-r–r-- 1 root root 0 Sep 14 05:47 lamers.log.4

-I put the empty lines in between the lines of the log output, for better inspection
-The crazy thing about the bind server is, that I am able to start it out of the virtualmin-aplication, but it seems that it doesn´t start by its own.

6

Howdy,

Well, first question – was it your intention to setup a custom logging location for BIND?

It appears to be attempting to log to a non-standard location. It looks like that location may not allow it to write to it.

What you may want to try doing though is to set the lamers.log file to be owned by the user “bind”.

After doing that, are you able to launch BIND normally?

-Eric

7

Hi Eric

Thank you for your help.

Thank to you folks help I was able to fix the problem. I just took out the bind logging and then I was able to upgrade the system via apt-get upgrade.

Greetings,

Ernesto