[solved] bind not reloading/restarting on slave

Discussion in 'ISPConfig 3 Priority Support' started by ressel, Nov 20, 2015.

  1. ressel

    ressel Member

    Hello,
    I have 1 master and 4 slaves in dns.
    on first slave I have following problem:
    I edit or add something ind dns, after job is run, and I see it disapear in job queue it will not use newest zone changes in bind on this slave, all other dns servers work fine.
    When I look into the zone file it self, everything is good, if I ssh into the server and run /etc/init.d/bind9 restart everything is working again.
    So I have tried run some dns changes in debug mode, but I can't see what the problem should be here.

    Code:
    /usr/local/ispconfig/server/server.sh
    20.11.2015-14:16 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    20.11.2015-14:16 - DEBUG - Found 2 changes, starting update process.
    20.11.2015-14:16 - DEBUG - Replicated from master: REPLACE INTO dns_soa (`id`,`sys_userid`,`sys_groupid`,`sys_perm_user`,`sys_perm_group`,`sys_perm_other`,`server_id`,`origin`,`ns`,`mbox`,`serial`,`refresh`,`retry`,`expire`,`minimum`,`ttl`,`active`,`xfer`,`also_notify`,`update_acl`) VALUES ('487','104','104','riud','riud','','9','nordiccomposite.dk.','dns1.dk.','support.borndata.dk.','2015112002','28800','7200','604800','86400','86400','Y','','','')
    20.11.2015-14:16 - DEBUG - Calling function 'soa_update' from plugin 'bind_plugin' raised by event 'dns_soa_update'.
    20.11.2015-14:16 - DEBUG - Writing BIND domain file: /etc/bind/pri.nordiccomposite.dk
    20.11.2015-14:16 - DEBUG - Writing BIND named.conf.local file: /etc/bind/named.conf.local
    20.11.2015-14:16 - DEBUG - Processed datalog_id 94683
    20.11.2015-14:16 - DEBUG - Replicated from master: REPLACE INTO dns_rr (`id`,`sys_userid`,`sys_groupid`,`sys_perm_user`,`sys_perm_group`,`sys_perm_other`,`server_id`,`zone`,`name`,`type`,`data`,`aux`,`ttl`,`active`,`stamp`,`serial`) VALUES ('4677','104','104','riud','riud','','9','487','mx','A','87.118.74.24','0','86400','Y','2015-11-20 15:16:44','2015112001')
    20.11.2015-14:16 - DEBUG - Calling function 'rr_insert' from plugin 'bind_plugin' raised by event 'dns_rr_insert'.
    20.11.2015-14:16 - DEBUG - Writing BIND domain file: /etc/bind/pri.nordiccomposite.dk
    20.11.2015-14:16 - DEBUG - Writing BIND named.conf.local file: /etc/bind/named.conf.local
    20.11.2015-14:16 - DEBUG - Processed datalog_id 94684
    20.11.2015-14:16 - DEBUG - Calling function 'restartBind' from module 'dns_module'.
    20.11.2015-14:16 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    finished.
    
    What should be next place to look into, to fix the issue?
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The debug log looks fine. any zone files with .err ending in the bind zone file directory? Any bind errors in syslog related to the changed zone?

    If you can't find something there, you should consider to try a reboot of this DNS node. Sometimes Linux is just like windows ;)
     
  3. ressel

    ressel Member

    This is from syslog.

    Nov 20 15:34:08 dns2 systemd[1]: bind9.service: control process exited, code=exited status=1
    Nov 20 15:34:08 dns2 systemd[1]: Reload failed for BIND Domain Name Server.
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok, and no other errors? Normally bind reports why it is not able to reload.
     
  5. ressel

    ressel Member

    /etc/init.d/bind9 reload
    [....] Reloading bind9 configuration (via systemctl): bind9.serviceJob for bind9.service failed. See 'systemctl status bind9.service' and 'journalctl -xn' for details.
    failed!

    But when I run systemctl status bind9.service or journalctl -xn I don't find any useful related to errors in bind.
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you try the server restart?
     
  7. ressel

    ressel Member

    yes, I have tried /etc/init.d/bind9 restart when I do this, everything looks fine. new zone changes is then active.
    And tried reboot the whole server.
     
  8. ressel

    ressel Member

    Could this have something to do with the problem?
    Nov 20 15:28:21 dns2 named[19580]: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
    Nov 20 15:28:21 dns2 named[19580]: managed-keys-zone: unable to synchronize managed keys: unexpected error
     
  9. ressel

    ressel Member

    Hello again
    I have fixed the issue.
    This is what I did:
    apt-get remove --purge bind9*
    rm -Rf /etc/bind/
    apt-get install bind9 bind9-host bind9utils dnsutils host libbind9-90 nfs-common rpcbind
    then I ran update script for ispconfig.
    And at last I have been into tools and synced all DNS records again.
    Now everything works as it should.

    I think it's some configs from upgrade Wheezy to Jessie that might have messed this server up.
     

Share This Page