Upgrading From 9.7.2 to 9.8.1 startup failed (due to fatal error)

Ken Schweigert shawing at gmail.com
Fri Sep 16 14:45:06 UTC 2011


I've been running a bind server for many years and have never had a
problem with upgrading until last night.  My needs for the bind server
are pretty meager, just hosting a few hundred zones without DNSSEC.
It is set up in a chroot jail according to a linux howto I found years
ago.

When compiling, the only thing different that I did was that I added
"--with-openssl=/usr/local/ssl" to use a compiled-from-source version
of openssl instead of the packaged version.  It did the 'configure'
fine and also the 'make' and 'make test'.  After doing the 'make
install' I stopped the running bind and then tried to restart with the
newly installing bind and got a startup failure.  The output from
/var/log/messages is below (lightly sanitized) but failed with this
error:

Sep 15 16:42:52 ns1 named[2234]: isc_file_isplainfile '/dev/null'
failed: invalid file

Thinking maybe something happened to these devices, I listed them out
and didn't see anything obviously wrong:

[root at ns1 dev]# ls -l /dev/null
crw-rw-rw-  1 root root 1, 3 Apr  8 14:46 /dev/null
[root at ns1 dev]# ls -l /chroot/named/dev/null
crw-rw-rw-  1 named named 1, 3 Jan  4  2006 /chroot/named/dev/null
[root at ns1 dev]#

Looking through my named.conf the only reference I have to /dev/null is:

logging {
...
     channel "dev_null_log" {
        file "/dev/null";
     };
…
category lame-servers { dev_null_log; };
…

I'd really like to not lose this channel because of how many lame
servers get reported.

Any ideas what may be my problem with this upgrade and what I can do
to get this version installed?

Regards,
-ken


bind-9.7.2-P2
bind-9.8.1


Sep 15 16:42:49 ns1 named: named shutdown succeeded
Sep 15 16:42:52 ns1 named[2234]: starting BIND 9.8.1 -u named -t
/chroot/named -c /etc/named.conf
Sep 15 16:42:52 ns1 named[2234]: built with '--with-openssl=/usr/local/ssl'
Sep 15 16:42:52 ns1 named[2234]: using up to 4096 sockets
Sep 15 16:42:52 ns1 named[2234]: loading configuration from '/etc/named.conf'
Sep 15 16:42:52 ns1 named[2234]: using default UDP/IPv4 port range:
[1024, 65535]
Sep 15 16:42:52 ns1 named[2234]: using default UDP/IPv6 port range:
[1024, 65535]
Sep 15 16:42:52 ns1 named[2234]: listening on IPv4 interface eth0,
aa.bb.cc.dd#53
Sep 15 16:42:52 ns1 named[2234]: listening on IPv4 interface eth0:0,
ee.ff.gg.hh#53
Sep 15 16:42:52 ns1 named[2234]: generating session key for dynamic DNS
Sep 15 16:42:52 ns1 named[2234]: sizing zone task pool based on 1244 zones
Sep 15 16:42:52 ns1 named[2234]: set up managed keys zone for view
_default, file 'managed-keys.bind'
Sep 15 16:42:52 ns1 named[2234]: Warning:
'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918
empty zones
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: 0.IN-ADDR.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: 127.IN-ADDR.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: 254.169.IN-ADDR.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone:
255.255.255.255.IN-ADDR.ARPA
Sep 15 16:42:52 ns1 named[2234]: 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
Sep 15 16:42:52 ns1 named[2234]: 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
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: D.F.IP6.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: 8.E.F.IP6.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: 9.E.F.IP6.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: A.E.F.IP6.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: B.E.F.IP6.ARPA
Sep 15 16:42:52 ns1 named[2234]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Sep 15 16:42:52 ns1 named[2234]: command channel listening on 127.0.0.1#953
Sep 15 16:42:52 ns1 named[2234]: isc_file_isplainfile '/dev/null'
failed: invalid file
Sep 15 16:42:52 ns1 named[2234]: configuring logging: invalid file
Sep 15 16:42:52 ns1 named[2234]: loading configuration: invalid file
Sep 15 16:42:52 ns1 named[2234]: exiting (due to fatal error)
Sep 15 16:42:52 ns1 named: named startup failed



More information about the bind-users mailing list