• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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