Skip to main content

After reboot the service nameserver fails

HowardE
As the title suggests, every time I reboot (graceful) I receive Service Name nameserver Service Status failed ? Notification The service "nameserver" appears to be down. Service Check Method The system"s command to check or to restart this service failed. Number of Restart Attempts 1 Service Check Raw Output The subprocess "/usr/local/cpanel/scripts/restartsrv_named" reported error number 9 when it ended.
This is followed by an email: The service "nameserver" is now operational. Service Check Raw Output The 'pdns' service passed the check: pdns (/usr/sbin/pdns_server --daemon --guardian=yes) is running as root with PID 2709 (pidfile+/proc check method).
This has been happening for probably at least a year now, but I only reboot occasionally like when there is a kernel update to centOS. I thought I'd post here before I submitted a ticket, as I didn't think it was ticket worthy as it stands. Thanks.

Comments

7 comments

Date Votes
  • rpvw
    I see exactly the same whenever I reboot ! Service Check Raw Output The subprocess "/usr/local/cpanel/scripts/restartsrv_named" reported error number 9 when it ended.
    After waiting a few minutes, the system reports The service "nameserver" is now operational. Service Check Raw Output The 'pdns' service passed the check: pdns (/usr/sbin/pdns_server --daemon --guardian=yes) is running as root with PID xxxx (pidfile+/proc check method).
    The problem started immediately after I switched from bind to use pdns, and has been consistently irritating ever since :(
    0
  • cPanelMichael
    Hello, Are these systems using CentOS/RHEL 6.x? If so, please post the output from the following commands:
    chkconfig --list named chkconfig --list pdns
    Thank you.
    0
  • rpvw
    My server is a Cloudlinux 6.9 with cPanel 66.0.23 all fully patched and updated
    [root@server ~]# chkconfig --list named named 0:off 1:off 2:on 3:on 4:on 5:on 6:off [root@server ~]# chkconfig --list pdns pdns 0:off 1:off 2:off 3:off 4:off 5:off 6:off
    0
  • cPanelMichael
    Hello, You can address this issue by ensuring the PDNS service starts at system boot time instead of the Named service. EX:
    chkconfig pdns on --level 2345 chkconfig named off --level 2345
    Thank you.
    0
  • rpvw
    Thank you Michael, that seems to have worked perfectly :-D Was/is there some glitch in the changeover scripting from Bind to pdns ? and if so, maybe it needs looking at, and adding to the bottom of what is sure to a be a (very) long list; to address it ? I don't know if it's relevant, I think I changed over from Bind to PowerDNS at version 60 to take advantage of the DNSSEC. The Nameserver failures at reboot started immediately following that change. The change was made in WHM >> Service Configuration >> Nameserver Selection by simply selecting the PowerDNS radio button and clicking "Save" Everything went OK and we were able to add a DNSSEC record without issue, and I noticed that whenever I called /usr/local/cpanel/scripts/restartsrv_bind or /usr/local/cpanel/scripts/restartsrv_named .... the daemon that was restarted was the /usr/sbin/pdns_server*** so I guessed that the script was now linked to the pdns instead of Bind Hope some of my rambling helps someone ! o_O
    0
  • HowardE
    Thank you... This solved it.
    0
  • cPanelMichael
    Was/is there some glitch in the changeover scripting from Bind to pdns ? and if so, maybe it needs looking at, and adding to the bottom of what is sure to a be a (very) long list; to address it ?

    Hello, I tested switching from Bind to PowerDNS on cPanel version 66.0.23 (with CloudLinux 6) using "WHM Home " Service Configuration " Nameserver Selection". Here's the chkconfig output before the conversion:
    # chkconfig --list named named 0:off 1:off 2:off 3:on 4:off 5:on 6:off # chkconfig --list pdns error reading information on service pdns: No such file or directory
    Here's the chkconfig output after the conversion:
    # chkconfig --list named named 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig --list pdns pdns 0:off 1:off 2:off 3:on 4:off 5:on 6:off
    As you can see, the conversion correctly disables "named" and enables "pdns" at system startup time. It's possible the issue you faced relates to an internal case that was already solved, like the one referenced on the below thread: PowerDNS - YUM EPEL Repo Thank you.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post