• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Solving 2 Bind Errors

E

EdwardDekker

Guest
Yesterday, I have updated BIND to version 9.9.0-1.

Only when i reboot the named service than i see this error.

[root@server ~]# service named restart
Stopping named: . [ OK ]
ls: /var/named/run-root/etc/named: No such file or directory
mount: mount point /var/named/run-root/etc/named does not exist
ls: /var/named/run-root/usr/lib/bind: No such file or directory
mount: mount point /var/named/run-root/usr/lib/bind does not exist
Starting named: [ OK ]
How could I fix these errors :)
 
Last edited by a moderator:
2 years later, still no reply.

same issue here, started after migrating from centos 5 to centos 6.

[root@ns2 ~]# /etc/init.d/named restart
Stopping named: . [ OK ]
ls: cannot access /var/named/run-root/etc/named: No such file or directory
mount: mount point /var/named/run-root/etc/named does not exist
ls: cannot access /var/named/run-root/var/named: No such file or directory
mount: mount point /var/named/run-root/var/named does not exist
ls: cannot access /var/named/run-root/usr/lib64/bind: No such file or directory
mount: mount point /var/named/run-root/usr/lib64/bind does not exist
Starting named: [ OK ]
[root@ns2 ~]#
 
Back
Top