Bind Inicia e em seguida Para

lclementino18
(usa Debian)

Enviado em 24/10/2017 - 08:26h

Olá,
Tenho o bind9 instalado no Debian, quando inicio o bind, ele não dá nenhuma mensagem de erro, mas em seguida se dou um bind9 status ele mostra o como fail e não rodando. Segue o syslog.

Oct 23 19:48:48 fw-cobrecom named[3311]: loading configuration from '/etc/bind/named.conf'
Oct 23 19:48:48 fw-cobrecom named[3311]: reading built-in trusted keys from file '/etc/bind/bind.keys
Oct 23 19:48:48 fw-cobrecom named[3311]: using default UDP/IPv4 port range: [1024, 65535]
Oct 23 19:48:48 fw-cobrecom named[3311]: using default UDP/IPv6 port range: [1024, 65535]
Oct 23 19:48:48 fw-cobrecom named[3311]: no IPv6 interfaces found
Oct 23 19:48:48 fw-cobrecom named[3311]: listening on IPv4 interface lo, 127.0.0.1#53
Oct 23 19:48:48 fw-cobrecom named[3311]: listening on IPv4 interface eth0, 192.168.14.2#53
Oct 23 19:48:48 fw-cobrecom named[3311]: listening on IPv4 interface eth1, 201.72.18.50#53
Oct 23 19:48:48 fw-cobrecom named[3311]: listening on IPv4 interface eth2, 192.168.1.1#53
Oct 23 19:48:48 fw-cobrecom named[3311]: generating session key for dynamic DNS
Oct 23 19:48:48 fw-cobrecom named[3311]: set up managed keys zone for view _default, file 'managed-ke
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 254.169.IN-ADDR.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: D.F.IP6.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 8.E.F.IP6.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 9.E.F.IP6.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: A.E.F.IP6.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: B.E.F.IP6.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Oct 23 19:48:48 fw-cobrecom named[3311]: command channel listening on 127.0.0.1#953
Oct 23 19:48:48 fw-cobrecom named[3311]: zone 0.in-addr.arpa/IN: loaded serial 1
Oct 23 19:48:48 fw-cobrecom named[3311]: zone 127.in-addr.arpa/IN: loaded serial 1
Oct 23 19:48:48 fw-cobrecom named[3311]: zone 1.168.192.in-addr.arpa/IN: loaded serial 1
Oct 23 19:48:48 fw-cobrecom named[3311]: zone 10.168.192.in-addr.arpa/IN: loaded serial 1
Oct 23 19:48:48 fw-cobrecom named[3311]: zone 3.168.192.in-addr.arpa/IN: loaded serial 1
Oct 23 19:48:48 fw-cobrecom named[3311]: zone 255.in-addr.arpa/IN: loaded serial 1
Oct 23 19:48:48 fw-cobrecom named[3311]: zone cobrecom/IN: loaded serial 1
Oct 23 19:48:48 fw-cobrecom named[3311]: zone localhost/IN: loaded serial 2
Oct 23 19:48:48 fw-cobrecom named[3311]: zone rede03/IN: loaded serial 1
Oct 23 19:48:48 fw-cobrecom named[3311]: managed-keys-zone ./IN: loading from master file managed-key
Oct 23 19:48:48 fw-cobrecom named[3311]: managed-keys-zone ./IN: loaded serial 0
Oct 23 19:48:48 fw-cobrecom named[3311]: zone cobrecom/IN: sending notifies (serial 1)
Oct 23 19:48:48 fw-cobrecom named[3311]: running
Oct 23 19:48:48 fw-cobrecom named[3311]: zone rede03/IN: sending notifies (serial 1)
Oct 23 19:48:48 fw-cobrecom named[3311]: zone 1.168.192.in-addr.arpa/IN: sending notifies (serial 1)
Oct 23 19:48:48 fw-cobrecom named[3311]: zone 10.168.192.in-addr.arpa/IN: sending notifies (serial 1)
Oct 23 19:48:48 fw-cobrecom named[3311]: zone 3.168.192.in-addr.arpa/IN: sending notifies (serial 1)


Alguma dica ou sugestão?

SMarcell
(usa Slackware)

Enviado em 24/10/2017 - 10:16h

Rode o Bind em modo debug:

# named -g -d 3 

E veja o que ocorre.

lclementino18
(usa Debian)

Enviado em 24/10/2017 - 14:30h

O resultado de alguns segundos rodando o comando.

24-Oct-2017 14:25:07.175 client @0x7f02ac1101d0: free
24-Oct-2017 14:25:07.175 client @0x7f02ac11e390: shutdown
24-Oct-2017 14:25:07.175 client @0x7f02ac11e390: free
24-Oct-2017 14:25:07.175 client @0x7f02b44d46b0: shutdown
24-Oct-2017 14:25:07.175 client @0x7f02b44d46b0: free
24-Oct-2017 14:25:07.175 client @0x7f02b44e2870: shutdown
24-Oct-2017 14:25:07.175 client @0x7f02b44e2870: free
24-Oct-2017 14:25:07.175 client @0x7f02ac12c550: shutdown
24-Oct-2017 14:25:07.175 client @0x7f02ac12c550: free
24-Oct-2017 14:25:07.175 zone_shutdown: 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/IN: shutting down
24-Oct-2017 14:25:07.175 zone_shutdown: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: shutting down
24-Oct-2017 14:25:07.175 zone_shutdown: zone 8.E.F.IP6.ARPA/IN: shutting down
24-Oct-2017 14:25:07.175 zone_shutdown: managed-keys-zone ./IN: shutting down
24-Oct-2017 14:25:07.175 calling free_rbtdb(.)
24-Oct-2017 14:25:07.175 done free_rbtdb(.)
24-Oct-2017 14:25:07.175 zone_shutdown: zone cobrecom/IN: shutting down
24-Oct-2017 14:25:07.175 calling free_rbtdb(cobrecom)
24-Oct-2017 14:25:07.175 adjust_quantum -> 325
24-Oct-2017 14:25:07.175 zone_shutdown: zone localhost/IN: shutting down
24-Oct-2017 14:25:07.175 calling free_rbtdb(localhost)
24-Oct-2017 14:25:07.175 done free_rbtdb(localhost)
24-Oct-2017 14:25:07.175 zone_shutdown: zone id.server/CH: shutting down
24-Oct-2017 14:25:07.175 zone_shutdown: zone version.bind/CH: shutting down
24-Oct-2017 14:25:07.175 zone_shutdown: zone 9.E.F.IP6.ARPA/IN: shutting down
24-Oct-2017 14:25:07.175 zone_shutdown: zone A.E.F.IP6.ARPA/IN: shutting down
24-Oct-2017 14:25:07.175 zone_shutdown: zone hostname.bind/CH: shutting down
24-Oct-2017 14:25:07.175 res 0x7f02b8032198: detach
24-Oct-2017 14:25:07.175 res 0x7f02b8032198: destroy
24-Oct-2017 14:25:07.175 client @0x7f02ac0d7ad0: free
24-Oct-2017 14:25:07.175 clientmgr @0x7f02bef59010: clientmgr_destroy
24-Oct-2017 14:25:07.175 dns_requestmgr_detach: 0x7f02b80351c8: eref 0 iref 0
24-Oct-2017 14:25:07.175 mgr_destroy
24-Oct-2017 14:25:07.175 calling free_rbtdb(.)
24-Oct-2017 14:25:07.175 done free_rbtdb(.)
24-Oct-2017 14:25:07.175 done free_rbtdb(cobrecom)
24-Oct-2017 14:25:07.175 zone_shutdown: zone rede03/IN: shutting down
24-Oct-2017 14:25:07.176 res 0x7f02b8032010: detach
24-Oct-2017 14:25:07.176 res 0x7f02b8032010: destroy
24-Oct-2017 14:25:07.176 dns_requestmgr_detach: 0x7f02b8035010: eref 0 iref 0
24-Oct-2017 14:25:07.176 mgr_destroy
24-Oct-2017 14:25:07.176 calling free_rbtdb(.)
24-Oct-2017 14:25:07.176 done free_rbtdb(.)
24-Oct-2017 14:25:07.176 calling free_rbtdb(.)
24-Oct-2017 14:25:07.176 adjust_quantum -> 325
24-Oct-2017 14:25:07.176 calling free_rbtdb(rede03)
24-Oct-2017 14:25:07.176 done free_rbtdb(rede03)
24-Oct-2017 14:25:07.177 adjust_quantum -> 493
24-Oct-2017 14:25:07.177 adjust_quantum -> 619
24-Oct-2017 14:25:07.177 adjust_quantum -> 714
24-Oct-2017 14:25:07.177 adjust_quantum -> 785
24-Oct-2017 14:25:07.177 done free_rbtdb(.)
24-Oct-2017 14:25:07.178 Unregistering DLZ_stub driver.
24-Oct-2017 14:25:07.178 Unregistering SDLZ driver.
24-Oct-2017 14:25:07.178 Unregistering DLZ driver.
24-Oct-2017 14:25:07.178 Unregistering DLZ filesystem driver.
24-Oct-2017 14:25:07.178 Unregistering SDLZ driver.
24-Oct-2017 14:25:07.178 Unregistering DLZ driver.
24-Oct-2017 14:25:07.178 Unregistering DLZ bdb driver.
24-Oct-2017 14:25:07.178 Unregistering SDLZ driver.
24-Oct-2017 14:25:07.178 Unregistering DLZ driver.
24-Oct-2017 14:25:07.178 Unregistering DLZ bdbhpt driver.
24-Oct-2017 14:25:07.178 Unregistering SDLZ driver.
24-Oct-2017 14:25:07.178 Unregistering DLZ driver.
24-Oct-2017 14:25:07.178 Unregistering DLZ ldap driver.
24-Oct-2017 14:25:07.178 Unregistering SDLZ driver.
24-Oct-2017 14:25:07.178 Unregistering DLZ driver.
24-Oct-2017 14:25:07.178 exiting


Aparentemente está normal, somente o serviço que fica como se tivesse falhado.