Websites Not Reachable After Upgrade
Hi,
I just completed the latest WHM upgrade everything is down and not accessible accept the WHM via IP address.
I received the attached email.
How can I get this corrected quickly?
Thank you.
-
Hi, It did not correct the issue ... this is the message I am getting: Waiting for "pdns" to start "Waiting for named,mydns,nsd,pdns_server to shutdown ... not running. "failed. Cpanel::Exception::Services::StartError Service Status undefined status from Cpanel::ServiceManager::Services::Pdns Service Error (XID hx7tbn) The "pdns" service failed to start. Startup Log Mar 04 19:41:31 host.myserver.org systemd[1]: Failed to start PowerDNS Authoritative Server. Mar 04 19:41:31 host.myserver.org systemd[1]: Unit pdns.service entered failed state. Mar 04 19:41:31 host.myserver.org systemd[1]: pdns.service failed. Mar 04 19:41:32 host.myserver.org systemd[1]: pdns.service holdoff time over, scheduling restart. Mar 04 19:41:32 host.myserver.org systemd[1]: Stopped PowerDNS Authoritative Server. Mar 04 19:41:32 host.myserver.org systemd[1]: Starting PowerDNS Authoritative Server... Mar 04 19:41:32 host.myserver.org systemd[1]: pdns.service: main process exited, code=exited, status=218/CAPABILITIES Mar 04 19:41:32 host.myserver.org systemd[1]: Failed to start PowerDNS Authoritative Server. Mar 04 19:41:32 host.myserver.org systemd[1]: Unit pdns.service entered failed state. Mar 04 19:41:32 host.myserver.org systemd[1]: pdns.service failed. 0 -
I corrected the issue by changing it back to BIND and everything is working correctly. Thank you. 0 -
That was going to be my next short-term recommendation, switching the system to BIND. If you'd like us to investigate directly you're always welcome to submit a ticket to our team so we can check that out, as we're happy to work during non-peak hours for your system and users. 0 -
I have this exact issue, but the workaround you have linked to above no longer opens. I also switched back to BIND. 0 -
@ariehkovler - since this is a defect article, you have to be signed into our ticket system in order to access that link. Switching to BIND would also get things working if your provider is not able to update the kernel. 0 -
Switching to BIND did, indeed, get things working. What kernel should I be asking my provider to update? 0 -
I'm glad that's working well :D While there isn't a specific kernel version, they would need to ensure it supports IPv6. 0 -
Mismo problema tras actualizar a V94.0.2. Probada la soluci"n de a"adir en /etc/pdns/pdns.conf la linea: local-address=0.0.0.0 pero no resuelve la incidencia. Cambiado a BIND vuelta a la normalidad Same problem after upgrading to V94.0.2. Tried the solution of adding in /etc/pdns/pdns.conf the line: local-address=0.0.0.0.0 but it does not solve the issue. Switched to BIND and back to normal. 0 -
@sdmg - Es probable que su problema est" relacionado con el kernel de la m"quina. "Tu anfitri"n no puede actualizarlo? Si no es as", puede probar las soluciones alternativas mencionadas aqu": or you can keep the system on BIND until they are able to update the kernel. 0 -
Hello guys, same issue here. It only got fixed by switching to Bind. Should I worry if this server is part of a cluster where every other member and the master itself are using powerdns? 0 -
@Kent Brockman - what kernel is the system running? It doesn't really matter if it's part of a cluster or not. 0 -
@Kent Brockman - what kernel is the system running? It doesn't really matter if it's part of a cluster or not.
# uname -r 3.10.0-229.20.1.el7.centos.plus.x86_64
Do you know what kernel versions are the best to workaround this issue?0 -
Ok, I'll talk with datacenter's staff. Thanks! 0 -
I just checked a CentOS 7 box that had recently been updated and I show this: # uname -r 3.10.0-1160.15.2.el7.x86_640 -
Hi guys, same issue here on a dedicated server after upgrade to 94.0.4 switched to BIND 0
Please sign in to leave a comment.
Comments
18 comments