Named dont reload after customer made changes on dns (code=exited, status=226/NAMESPACE)

leolage

Verified User
Joined
Jul 2, 2019
Messages
6
Hello,

We have directadmin with CloudLinux 8.5 and when customer make any changes on dns zones, named dont reload, and we need to restart named service. All times, when we check service named status, ExecReload process is failed with this error:


[root@xxxxx ~]# service named status
Redirecting to /bin/systemctl status named.service
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/etc/systemd/system/named.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2022-03-23 10:35:24 -03; 1 weeks 1 days ago
Process: 1436088 ExecReload=/bin/sh -c if /usr/sbin/rndc null > /dev/null 2>&1; then /usr/sbin/rndc reload; else /bin/kill -HUP $MAINPID; fi (code=exited, status=226/NAMESPACE)
Main PID: 2830895 (named)
Tasks: 9 (limit: 62379)
Memory: 384.5M
CGroup: /system.slice/named.service
└─2830895 /usr/sbin/named -u named -c /etc/named.conf

anybody already see this error?
 
I presume you have enough space left on the device.

You could try this. Stop the named service, then use this command via SSH.

rndc reload
see if that throws any errors.

Also check your logfile if there is anything extra to see there.
 
After I tried the command, the problem persist
Yes, but the command did try to restart bind, right? If yes, than that part is good.

Normally in /var/log/messages (RH and Centos) or in /var/log/syslog (Debian and alike) there should always be a log when named is restarted or being tried to restart.

Did you by any chance made a symlink from /var/tmp to /tmp? I've read on the net that this also sometimes causes those "namespace" errors.

If not, then we have to wait until somebody else helps, or if you're on a monthly account, you might send in a ticket.
 
Back
Top