Operating System & Version
CloudLinux 7.9
cPanel & WHM Version
98.0.6

ankeshanand

Well-Known Member
Mar 29, 2021
193
58
103
India
cPanel Access Level
Root Administrator
Hello Community,

I've setup a stable server which was running from last 45 Days without any issues. Its load is also always below 2. Today, PDNS has stopped working completely.
When restarting, It shows this:
Code:
[[email protected] ~]# /scripts/restartsrv_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 25764) 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 25777) 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 mgqwas) The “pdns” service failed to start.

Startup Log
        Sep 15 18:05:40 server5 systemd[1]: Failed to start PowerDNS Authoritative Server.
        Sep 15 18:05:40 server5 systemd[1]: Unit pdns.service entered failed state.
        Sep 15 18:05:40 server5 systemd[1]: pdns.service failed.

pdns has failed. Contact your system administrator if the service does not automagically recover.
There have been no Modifications in its Configuration or Any Other Configuration. Journalctl Shows:
Code:
[[email protected] ~]# journalctl -xe
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pdns.service has begun starting up.
Sep 15 18:02:35 server5 systemd[2740]: Failed at step NAMESPACE spawning /usr/sbin/pdns_server: Invalid argument
-- Subject: Process /usr/sbin/pdns_server could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/sbin/pdns_server could not be executed and failed.
--
-- The error number returned by this process is 22.
Sep 15 18:02:35 server5 systemd[1]: pdns.service: main process exited, code=exited, status=226/NAMESPACE
Sep 15 18:02:35 server5 systemd[1]: Failed to start PowerDNS Authoritative Server.
-- Subject: Unit pdns.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pdns.service has failed.
--
-- The result is failed.
Sep 15 18:02:35 server5 systemd[1]: Unit pdns.service entered failed state.
Sep 15 18:02:35 server5 systemd[1]: pdns.service failed.
This Log shows problem is:
Code:
 Failed at step NAMESPACE spawning /usr/sbin/pdns_server: Invalid argument
Uptill now, I haven't got solution to this problem.
I have tried the Following:
1. Changed Nameserver Selection to BIND and changed it again to PowerDNS.(Currently, Server is running on BIND)
2. YUM UPDATE
3. UPCP Update from Version 96 to Version 98
4. Rebooted server

This problem happened randomly without even interference to Configurations or any Modifications. Anyone who can suggest what am I missing here?
 

cPJustinD

Administrator
Staff member
Jan 12, 2021
285
45
103
Houston
cPanel Access Level
Root Administrator
Hello! Unfortunately, the error doesn't provide much information as to why exactly it failed aside from the namespace error. I think it would be best to open a support ticket so that our analysts can review the issue more thoroughly and determine what exactly is occurring. You can submit a support request using the "Submit a ticket" link in my signature below.

Please be sure to link this thread when opening the ticket and provide the ticket number here so that we can track the issue appropriately. If possible, please post the resolution on this thread as it may help other community members with similar issues.