Skip to main content

Power Dns issue after update

ribo
Hello, yesterday i updated in my centos 7 vps cpanel from 92.0.11 to 94.0.2. The power dns was updated to 4.3.1 After that power dns was down and it couldlnt restart So to can have my domains up i use Bind. Why happened that?

Comments

19 comments

Date Votes
  • ffeingol
    With no logs, it would be really hard to help you. Since you have root access a cPanel support ticket is prob. the fastest way to get a resolution.
    0
  • ribo
    Do you know where logs of powerdns are located?
    0
  • ribo
    This what i had when i was try to restart pdns Waiting for "pdns" to start ""info [restartsrv_pdns] systemd failed to start the service "pdns" (The "/usr/bin/systemctl restart pdns.service --no-ask-password" command (process 23719) reported error number 1 when it ended.): Job for pdns.service failed because the control process exited with error code. See "systemctl status pdns.service" and "journalctl -xe" for details. "Waiting for named,mydns,nsd,pdns_server to shutdown ... not running. info [restartsrv_pdns] systemd failed to start the service "pdns" (The "/usr/bin/systemctl restart pdns.service --no-ask-password" command (process 23725) reported error number 1 when it ended.): Job for pdns.service failed because the control process exited with error code. See "systemctl status pdns.service" and "journalctl -xe" for details. "failed. Cpanel::Exception::Services::StartError Service Status undefined status from Cpanel::ServiceManager::Services::Pdns Service Error (XID 4udhrc) The "pdns" service failed to start. Startup Log Mar 03 04:56:55 server1 systemd[1]: Failed to start PowerDNS Authoritative Server. Mar 03 04:56:55 server1 systemd[1]: Unit pdns.service entered failed state. Mar 03 04:56:55 server1 systemd[1]: pdns.service failed. pdns has failed. Contact your system administrator if the service does not automagically recover
    0
  • jimlongo
    Same exact thing here when trying to restart DNS server. Tried restarting because I keep getting alerts that
    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 102
    Service Check Raw Output (XID t3pmen) The "pdns" service is down. The subprocess "/usr/local/cpanel/scripts/restartsrv_named" reported error number 255 when it ended.
    0
  • cPanelLauren
    Hello, What kernel version is running on the affected system? If it's an older version this may be related to a recent case CPANEL-35848 which points out an incompatibility with very old kernels. There is some further information and a workaround supplied here as well:
    0
  • ribo
    I saw 2.6.32-042stab140.1
    0
  • cPanelLauren
    I saw 2.6.32-042stab140.1

    That's an old kernel version Download/kernel/rhel6/042stab140.1 - OpenVZ Virtuozzo Containers Wiki if the steps provided in the article linked above don't provide assistance or if you're unsure how to complete them please open a support request.
    0
  • jimlongo
    my kernel is 2.6.32-042stab141.3
    0
  • cPRex Jurassic Moderator
    @jimlongo - could you speak with your host (if this is a VPS system) and see if they are able to update that kernel?
    0
  • jimlongo
    Checking, will post when I get some resolution. Sent them the article cPanel
    0
  • jimlongo
    @cPRex they said, [quote]we are not allowed to update the kernel since we use OpenVZ virtualization technique in which all the containers shares the same kernel of node server. As an alternative measure to bring DNS online, you may consider trying to change from pdns to named.
    0
  • jimlongo
    Per my understanding of the article, After disabling DNSSEC at the registrar for the domains using my nameservers, I restarted the dns service # /scripts/setupnameserver bind named is running again.
    0
  • peterk
    Hello, I have identical issue like Ribo. My kernel is: 2.6.32-042stab134.8 cPanel/WHM: v94.0.2 Now i'm switch to Bind...
    0
  • cPRex Jurassic Moderator
    If your hosting provider isn't able to update the kernel, it would be best to switch to BIND in order to get things working normally.
    0
  • peterk
    I still have a question, the answer to which will be important for some of this thread. I cannot update the kernel, but I can change the machine that has the newer kernel. Can switching from 2.6.32-042stab134.8 to 3.10.0-1127.18.2.vz7.163.46 cause any problems with server?
    0
  • cPRex Jurassic Moderator
    That should take care of the issue. The kernel you mentioned is from November 2020, while the older version is from 2018.
    0
  • peterk
    I'll check it out next week and let me know if it fixes the problem.
    0
  • peterk
    Ok, my server is move to machine with new kernel verion (3.10.0-1127.18.2.vz7.163.46) and everything work fine now. I'm switch back to PowerDNS and it runs without any errors.
    0
  • cPRex Jurassic Moderator
    I'm glad to hear things are working well for you now!
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post