Upgrading to Power DNS fails
Hi,
I've tried to upgrade to power dns on a server multiple times now and it keeps failing. Here is the errors, but I can't tell of something that I can change to fix them.
Service Error
(XID 7uzu5z) The "pdns" service failed to start.
Startup Log
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: TCP server bound to 0.0.0.0:53
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: TCPv6 server bound to [::]:53
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: PowerDNS Authoritative Server 4.1.5 (C) 2001-2018 PowerDNS.COM BV
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: Using 64-bits mode. Built using gcc 4.8.2 20140120 (Red Hat 4.8.2-16) on Nov 28 2018 11:44:40 by root@rpmbuild-64-centos-7.dev.cpanel.net.
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it according to the terms of the GPL version 2.
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: Creating backend connection for TCP
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: [bindbackend] Parsing 14695 domain(s), will report when done
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: [bindbackend] Warning! Skipping zone '.' because type 'hint' is invalid
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: [bindbackend] Warning! Skipping zone '.' because type 'hint' is invalid
Dec 15 15:14:52 lv41.webhost.pro pdns_server[11983]: [bindbackend] Warning! Skipping zone '.' because type 'hint' is invalid
pdns has failed. Contact your system administrator if the service does not automagically recover.
Building global cache for cpanel...Done
Nameserver conversion complete
-
Those warnings aren't indicative of what cause pdns to fail - pdns doesn't recognize BIND's "hint" zones. You can read about what these are here: IANA " Root Files It looks like the conversion does complete though per the end message. When you start/restart pdns what is the output? /scripts/restartsrv_pdns
0 -
I get this messge: [root@xxx ~]# /scripts/restartsrv_pdns warn [restartsrv_pdns] The system is unable to find systemd configuration for the 'pdns' service... (XID 2jny52) The "pdns" service is not configured. But I changed back to bind when the conversion failed. I need to work. Are you saying I should convert then try the restart to check for errors? 0 -
Yes, pdns wouldn't start in the instance you switched back to bind. I mean when you run the conversion and if it fails, what is the output when you attempt to restart the service. I'd like to see the error. Also, if you run the following does the service start: /scripts/rebuilddnsconfig
This will rebuild the configuration and restart the nameserver0 -
Sorry for the delay /scripts/rebuilddnsconfig warn [rebuilddnsconfig] 66.249.137.140 is an IP address, not a domain name warn [rebuilddnsconfig] stellarphone domain name must have a valid TLD label warn [rebuilddnsconfig] 66.249.128.164 is an IP address, not a domain name warn [rebuilddnsconfig] moorestatenet domain name must have a valid TLD label warn [rebuilddnsconfig] 66.249.137.15 is an IP address, not a domain name info [rebuilddnsconfig] Error encountered by "/usr/bin/pdns_control" when running command: "bind-remove-zone -- 66.249.137.15" info [rebuilddnsconfig] The "/usr/bin/pdns_control bind-remove-zone -- 66.249.137.15" command (process 13121) reported error number 1 when it ended.: Fatal error: Unable to connect to remote '/var/run/pdns.controlsocket': Connection refused. info [rebuilddnsconfig] Error encountered by "/usr/bin/pdns_control" when running command: "bind-remove-zone -- 66.249.137.140" info [rebuilddnsconfig] The "/usr/bin/pdns_control bind-remove-zone -- 66.249.137.140" command (process 13122) reported error number 1 when it ended.: Fatal error: Unable to connect to remote '/var/run/pdns.controlsocket': Connection refused. info [rebuilddnsconfig] Error encountered by "/usr/bin/pdns_control" when running command: "bind-remove-zone -- 66.249.128.164" info [rebuilddnsconfig] The "/usr/bin/pdns_control bind-remove-zone -- 66.249.128.164" command (process 13123) reported error number 1 when it ended.: Fatal error: Unable to connect to remote '/var/run/pdns.controlsocket': Connection refused. Waiting for "pdns" to restart "info [restartsrv_pdns] systemd failed to start the service "pdns" (The "/usr/bin/systemctl restart pdns.service --no-ask-password" command (process 13135) 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. "Gracefully terminating process: pdns_serve with pid 13280 and owner named. Waiting for 13280 to shutdown ........ terminated. 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 13286) 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 pdns (/usr/sbin/pdns_server --guardian=no --daemon=no --disable-syslog --log-timestamp=no --write-pid=no) is running as named with PID 13124 (systemd+/proc check method). Service Error (XID keu6h9) The "pdns" service failed to start. Startup Log Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: TCP server bound to 0.0.0.0:53 Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: TCPv6 server bound to [::]:53 Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: PowerDNS Authoritative Server 4.1.10 (C) 2001-2018 PowerDNS.COM BV Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: Using 64-bits mode. Built using gcc 4.8.2 20140120 (Red Hat 4.8.2-16) on Sep 4 2019 10:30:59 by root@rpmbuild-64-centos-7.dev.cpanel.net. Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it according to the terms of the GPL version 2. Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: Creating backend connection for TCP Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: [bindbackend] Parsing 14725 domain(s), will report when done Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: [bindbackend] Warning! Skipping zone '.' because type 'hint' is invalid Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: [bindbackend] Warning! Skipping zone '.' because type 'hint' is invalid Feb 12 15:15:13 666.webhost.pro pdns_server[13297]: [bindbackend] Warning! Skipping zone '.' because type 'hint' is invalid pdns has failed. Contact your system administrator if the service does not automagically recover.
This is a funny typo: automagically. I wish it would automagically fix itself.0 -
Hello, I'm curious, it notes it's parsing 14,725 zones and I wonder if part of the issue is a timeout (or the script not having a long enough timeout for a response) or if something else is listening on 53 when you're attempting the switch. - That being said, when you do switch (right after) what is the output of the following:
netstat -plan |grep :53 |awk '{print $7}'
- Then when you rebuild the dns config what is the output of the following:
journalctl -f -u pdns
- (alternatively you could run
journalctl -xe
)
- (alternatively you could run
- As well as the output of these:
systemctl status pdns
systemctl status named
0 - That being said, when you do switch (right after) what is the output of the following:
Please sign in to leave a comment.
Comments
5 comments