BIND 9.3.6 - server failure error code 2

C

cp2011

New member
Joined
Jul 26, 2011
Messages
3
I started to review the logs in BIND and noticed that there are entries for server failure error code 2.

1) Why is causes these errors, even if the URL queried are valid?
2) How can I investigate the cause of these errors?
3) Is this a normal happening in BIND? I am seeing about 0.5% error rate.
4) What is considered normal rate?

Anyone has any statistic showing the max query per second that can be handled by BIND?
 
Check /var/log/messages for errors and fix the errors.
 
cat /var/log/messages | grep -i named

Post the errors here and we can help you fix them.
 
here it is.


[root@58 ~]# cat /var/log/messages | grep -i named
Jul 25 19:01:30 DNSSVR named[5725]: starting BIND 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 -u named -t /var/named/chroot
Jul 25 19:01:30 DNSSVR named[5725]: adjusted limit on open files from 1024 to 1048576
Jul 25 19:01:30 DNSSVR named[5725]: found 16 CPUs, using 16 worker threads
Jul 25 19:01:30 DNSSVR named[5725]: using up to 4096 sockets
Jul 25 19:01:30 DNSSVR named[5725]: loading configuration from '/etc/named.conf'
Jul 25 19:01:30 DNSSVR named[5725]: using default UDP/IPv4 port range: [1024, 65535]
Jul 25 19:01:30 DNSSVR named[5725]: using default UDP/IPv6 port range: [1024, 65535]
Jul 25 19:01:30 DNSSVR named[5725]: listening on IPv6 interfaces, port 53
Jul 25 19:01:30 DNSSVR named[5725]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 25 19:01:30 DNSSVR named[5725]: listening on IPv4 interface eth0, 10.19.1.11#53
Jul 25 19:01:30 DNSSVR named[5725]: listening on IPv4 interface eth1, 10.71.132.11#53
Jul 25 19:01:30 DNSSVR named[5725]: listening on IPv4 interface virbr0, 10.16.122.1#53
Jul 25 19:01:30 DNSSVR named[5725]: binding TCP socket: address in use
Jul 25 19:01:30 DNSSVR named[5725]: command channel listening on 127.0.0.1#953
Jul 25 19:01:30 DNSSVR named[5725]: command channel listening on ::1#953
Jul 25 19:01:30 DNSSVR named[5725]: the working directory is not writable
Jul 27 02:31:10 DNSSVR named[1761]: starting BIND 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 -u named -t /var/named/chroot
Jul 27 02:31:10 DNSSVR named[1761]: adjusted limit on open files from 1024 to 1048576
Jul 27 02:31:10 DNSSVR named[1761]: found 16 CPUs, using 16 worker threads
Jul 27 02:31:10 DNSSVR named[1761]: using up to 4096 sockets
Jul 27 02:31:10 DNSSVR named[1761]: loading configuration from '/etc/named.conf'
Jul 27 02:31:10 DNSSVR named[1761]: using default UDP/IPv4 port range: [1024, 65535]
Jul 27 02:31:10 DNSSVR named[1761]: using default UDP/IPv6 port range: [1024, 65535]
Jul 27 02:31:10 DNSSVR named[1761]: listening on IPv6 interfaces, port 53
Jul 27 02:31:10 DNSSVR named[1761]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 27 02:31:10 DNSSVR named[1761]: listening on IPv4 interface eth0, 10.19.1.11#53
Jul 27 02:31:10 DNSSVR named[1761]: listening on IPv4 interface eth1, 10.71.132.11#53
Jul 27 02:31:10 DNSSVR named[1761]: listening on IPv4 interface virbr0, 10.16.122.1#53
Jul 27 02:31:10 DNSSVR named[1761]: binding TCP socket: address in use
Jul 27 02:31:10 DNSSVR named[1761]: command channel listening on 127.0.0.1#953
Jul 27 02:31:10 DNSSVR named[1761]: command channel listening on ::1#953
Jul 27 02:31:10 DNSSVR named[1761]: the working directory is not writable
[root@58 ~]#
 
Make sure you dont have bind-chroot installed.

rpm -aq | grep -i bind-chroot

If you do find it installed you need to remove it with: rpm -e --nodeps <filename>

Also there are no errors there.

Try:

rndc reload

Then look in /var/log/messages for any errors.
 
You must log in or register to reply here.
Back
Top