Bind9 failed to start after server restart

Discussion in 'Installation/Configuration' started by laptop_user, Sep 30, 2011.

  1. laptop_user

    laptop_user Member

    Hello,

    I has a vps and the server restart a few time. I dunno what happen but my provider says they are having problem with the node.

    OK now the problem is every service started automatically after reboot but bind9 failed to kicked in. So the node reboot a few time and thats also mean I had to ssh'd in to start bind9 manually.


    Code:
    root@server1:~# /etc/init.d/bind9 status
    could not access PID file for bind9 ... failed!
    root@server1:~# /etc/init.d/bind9 restart
    Stopping domain name service...: bind9rndc: connect failed: 127.0.0.1#953: connection refused
    .
    Starting domain name service...: bind9.

    Is there anyway I could solve this problem? or maybe this problem is an isolated case?

    Thanks in advance,
     
    Last edited: Sep 30, 2011
  2. falko

    falko Super Moderator

    What are the error messages in your logs?
     
  3. laptop_user

    laptop_user Member

    Code:
    Sep 30 21:35:01 server1 named[17522]: client 93.113.174.225#15660: query (cache) 'adobe.com/A/IN' denied
    Sep 30 21:35:01 server1 named[17522]: client 93.113.174.225#50969: query (cache) 'adobe.com/A/IN' denied
    Sep 30 23:39:56 server1 named[17522]: received control channel command 'stop -p'
    Sep 30 23:39:56 server1 named[17522]: shutting down: flushing changes
    Sep 30 23:39:56 server1 named[17522]: stopping command channel on 127.0.0.1#953
    Sep 30 23:39:56 server1 named[17522]: stopping command channel on ::1#953
    Sep 30 23:39:56 server1 named[17522]: no longer listening on ::#53
    Sep 30 23:39:56 server1 named[17522]: no longer listening on 127.0.0.1#53
    Sep 30 23:39:56 server1 named[17522]: no longer listening on 127.0.0.2#53
    Sep 30 23:39:56 server1 named[17522]: no longer listening on 63.223.107.125#53
    Sep 30 23:39:56 server1 named[17522]: exiting
    Sep 30 23:39:57 server1 named[28386]: starting BIND 9.7.3 -u bind
    Sep 30 23:39:57 server1 named[28386]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS='
    Sep 30 23:39:57 server1 named[28386]: adjusted limit on open files from 1024 to 1048576
    Sep 30 23:39:57 server1 named[28386]: found 1 CPU, using 1 worker thread
    Sep 30 23:39:57 server1 named[28386]: using up to 4096 sockets
    Sep 30 23:39:57 server1 named[28386]: loading configuration from '/etc/bind/named.conf'
    Sep 30 23:39:57 server1 named[28386]: reading built-in trusted keys from file '/etc/bind/bind.keys'
    Sep 30 23:39:57 server1 named[28386]: using default UDP/IPv4 port range: [1024, 65535]
    Sep 30 23:39:57 server1 named[28386]: using default UDP/IPv6 port range: [1024, 65535]
    Sep 30 23:39:57 server1 named[28386]: listening on IPv6 interfaces, port 53
    Sep 30 23:39:57 server1 named[28386]: listening on IPv4 interface lo, 127.0.0.1#53
    Sep 30 23:39:57 server1 named[28386]: listening on IPv4 interface venet0, 127.0.0.2#53
    Sep 30 23:39:57 server1 named[28386]: listening on IPv4 interface venet0:0, 63.223.107.125#53
    Sep 30 23:39:57 server1 named[28386]: generating session key for dynamic DNS
    Sep 30 23:39:57 server1 named[28386]: set up managed keys zone for view _default, file 'managed-keys.bind'
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: 254.169.IN-ADDR.ARPA
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
    Sep 30 23:39:57 server1 named[28386]: 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 30 23:39:57 server1 named[28386]: 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 30 23:39:57 server1 named[28386]: automatic empty zone: D.F.IP6.ARPA
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: 8.E.F.IP6.ARPA
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: 9.E.F.IP6.ARPA
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: A.E.F.IP6.ARPA
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: B.E.F.IP6.ARPA
    Sep 30 23:39:57 server1 named[28386]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
    Sep 30 23:39:57 server1 named[28386]: command channel listening on 127.0.0.1#953
    Sep 30 23:39:57 server1 named[28386]: command channel listening on ::1#953
    Sep 30 23:39:57 server1 named[28386]: zone 0.in-addr.arpa/IN: loaded serial 1
    Sep 30 23:39:57 server1 named[28386]: zone 127.in-addr.arpa/IN: loaded serial 1
    Sep 30 23:39:57 server1 named[28386]: zone 255.in-addr.arpa/IN: loaded serial 1
    Sep 30 23:39:57 server1 named[28386]: zone localhost/IN: loaded serial 2
    Sep 30 23:39:57 server1 named[28386]: zone cheapantivirus.me/IN: loaded serial 2011092903
    Sep 30 23:39:57 server1 named[28386]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
    Sep 30 23:39:57 server1 named[28386]: managed-keys-zone ./IN: loaded serial 0
    Sep 30 23:39:57 server1 named[28386]: running
    Sep 30 23:39:57 server1 named[28386]: zone cheapantivirus.me/IN: sending notifies (serial 2011092903)
    Oct  1 12:12:47 server1 named[28386]: received control channel command 'stop -p'
    Oct  1 12:12:47 server1 named[28386]: shutting down: flushing changes
    Oct  1 12:12:47 server1 named[28386]: stopping command channel on 127.0.0.1#953
    Oct  1 12:12:47 server1 named[28386]: stopping command channel on ::1#953
    Oct  1 12:12:47 server1 named[28386]: no longer listening on ::#53
    Oct  1 12:12:47 server1 named[28386]: no longer listening on 127.0.0.1#53
    Oct  1 12:12:47 server1 named[28386]: no longer listening on 127.0.0.2#53
    Oct  1 12:12:47 server1 named[28386]: no longer listening on 63.223.107.125#53
    Oct  1 12:12:47 server1 named[28386]: exiting
    Oct  1 12:12:48 server1 named[21925]: starting BIND 9.7.3 -u bind
    Oct  1 12:12:48 server1 named[21925]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS='
    Oct  1 12:12:48 server1 named[21925]: adjusted limit on open files from 1024 to 1048576
    Oct  1 12:12:48 server1 named[21925]: found 1 CPU, using 1 worker thread
    Oct  1 12:12:48 server1 named[21925]: using up to 4096 sockets
    Oct  1 12:12:48 server1 named[21925]: loading configuration from '/etc/bind/named.conf'
    Oct  1 12:12:48 server1 named[21925]: reading built-in trusted keys from file '/etc/bind/bind.keys'
    Oct  1 12:12:48 server1 named[21925]: using default UDP/IPv4 port range: [1024, 65535]
    Oct  1 12:12:48 server1 named[21925]: using default UDP/IPv6 port range: [1024, 65535]
    Oct  1 12:12:48 server1 named[21925]: listening on IPv6 interfaces, port 53
    Oct  1 12:12:48 server1 named[21925]: listening on IPv4 interface lo, 127.0.0.1#53
    Oct  1 12:12:48 server1 named[21925]: listening on IPv4 interface venet0, 127.0.0.2#53
    Oct  1 12:12:48 server1 named[21925]: listening on IPv4 interface venet0:0, 63.223.107.125#53
    Oct  1 12:12:48 server1 named[21925]: generating session key for dynamic DNS
    Oct  1 12:12:48 server1 named[21925]: set up managed keys zone for view _default, file 'managed-keys.bind'
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: 254.169.IN-ADDR.ARPA
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
    Oct  1 12:12:48 server1 named[21925]: 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  1 12:12:48 server1 named[21925]: 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  1 12:12:48 server1 named[21925]: automatic empty zone: D.F.IP6.ARPA
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: 8.E.F.IP6.ARPA
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: 9.E.F.IP6.ARPA
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: A.E.F.IP6.ARPA
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: B.E.F.IP6.ARPA
    Oct  1 12:12:48 server1 named[21925]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
    Oct  1 12:12:48 server1 named[21925]: command channel listening on 127.0.0.1#953
    Oct  1 12:12:48 server1 named[21925]: command channel listening on ::1#953
    Oct  1 12:12:48 server1 named[21925]: zone 0.in-addr.arpa/IN: loaded serial 1
    Oct  1 12:12:48 server1 named[21925]: zone 127.in-addr.arpa/IN: loaded serial 1
    Oct  1 12:12:48 server1 named[21925]: zone 255.in-addr.arpa/IN: loaded serial 1
    Oct  1 12:12:48 server1 named[21925]: zone localhost/IN: loaded serial 2
    Oct  1 12:12:48 server1 named[21925]: zone cheapantivirus.me/IN: loaded serial 2011092903
    Oct  1 12:12:48 server1 named[21925]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
    Oct  1 12:12:48 server1 named[21925]: managed-keys-zone ./IN: loaded serial 0
    Oct  1 12:12:48 server1 named[21925]: running
    Oct  1 12:12:48 server1 named[21925]: zone cheapantivirus.me/IN: sending notifies (serial 2011092903)
    
    theres nothing much in error log but here is something I found related to bind in daemon.log

    I'm installing bind with this command:

    Code:
    apt-get install bind9
    Should I make any change if I want to set bind to run upon reboot. I thought it configures automatically like apache, mysql, ftp services?

    Thanks for your time falko.


    UPDATE

    I rebooted my vps just to see whether bind will start upon reboot. After restart on solusvm

    Code:
    root@server1:/# /etc/init.d/bind9 status
    could not access PID file for bind9 ... failed!
    indeed it failed to start. Other services works fine though.
    [​IMG]



    UPDATE
    Alhamdullilah. After a day googling and tinkering with my vps the solution is rather simple:

    Code:
    apt-get remove bind9
    and after that install it again
    Code:
    apt-get install bind9
    Bind9 is now start at reboot. Hope it helps :)
     
    Last edited: Oct 1, 2011

Share This Page