• 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

Named/Bind will not start

  • Thread starter networkthinking
  • Start date
Hello,
I have the same error than
VictorySaber with the same message.
Can anybody help me ?
 
Having the exact same problem, tried all fixes that I've found on this forum and still no luck, this is kinda ridiculous.

Plesk says this when trying to start named:
ERROR

Unable to make action: Unable to manage service by dnsmng: dnsmng: Service named failed to start
0: /usr/local/psa/admin/htdocs/server/restart_services.php:28 psaerror(string "Unable to make action: Unable to manage service by dnsmng: dnsmng: Service named failed to start")

/var/log/messages has:

Nov 5 22:42:29 EXFAST393 named[30414]: starting BIND 9.2.5 -u named -c /etc/named.conf -u named -t /var/named/run-root
Nov 5 22:42:29 EXFAST393 named[30414]: using 2 CPUs
Nov 5 22:42:29 EXFAST393 named[30414]: loading configuration from '/etc/named.conf'
Nov 5 22:42:29 EXFAST393 named[30414]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 5 22:42:29 EXFAST393 named[30414]: listening on IPv4 interface eth0, xxx#53
Nov 5 22:42:29 EXFAST393 named[30414]: listening on IPv4 interface eth0:1, xxx#53
Nov 5 22:42:29 EXFAST393 named[30414]: listening on IPv4 interface eth0:2, xxx#53
Nov 5 22:42:29 EXFAST393 named[30414]: listening on IPv4 interface eth0:3, xxx#53
Nov 5 22:42:29 EXFAST393 named[30414]: listening on IPv4 interface eth0:4, xxx#53
Nov 5 22:42:29 EXFAST393 named[30414]: command channel listening on 127.0.0.1#953
Nov 5 22:42:29 EXFAST393 named[30414]: could not open entropy source /dev/random: permission denied
Nov 5 22:42:29 EXFAST393 kernel: audit(1131252149.325:0): avc: denied { read } for pid=30416 exe=/usr/sbin/named name=random dev=dm-0 ino=8177079 scontext=root:system_r:named_t tcontext=root:eek:bject_r:named_zone_t tclass=chr_file
Nov 5 22:42:29 EXFAST393 named[30414]: couldn't open pid file '/var/named/run-root/var/named/named.pid': No such file or directory
Nov 5 22:42:29 EXFAST393 named[30414]: exiting (due to early fatal error)
Nov 5 22:42:29 EXFAST393 named: named startup failed

plz help! :confused:
 
I was having the exact same problem. Just installed Plesk 7.5.4 on a clean Fedora Core 3. After searching for hours on this forum without finding any working answer I did a search on google. I found a page that say this :

why "service named restart" fails? So I asked Plesk support and fortunatly they told me something helpful:

"RedHat distributes RHEL with SElinux enabled by default. So default SElinux policy denies apache to manage bind (named). You should edit some boleans of selinux or switch selinux off for resolving of your issue."

I disabled the SElinux by editing /etc/sysconfig/selinux and setting SELINUX flag to Permissive.

And the problem resolved.

If you want to your SElinux enabled in enforing mode you should run the fillowing commands to tune some Booleans:

# setsebool -P named_write_master_zones=1
# setsebool -P named_disable_trans=1
# setsebool -P httpd_disable_trans=1
# setsebool -P mysql_disable_trans=1

On my side I switch SeLinux to permissive then rebooted my server and voila it's finally working.

Hope this help others in the same situation I was.
 
ah yes that makes sense. I'll keep it in mind for future FC3 Plesk installs, but this one I reinstalled the server with CentOS 3.4 and everything worked fine from the start, I Think I'll be avoiding FC3 for Plesk.
 
Originally posted by Ronny
No one has a solutioN?
Hi Ronny, you are coming into this thread a bit late and you did not say which exact problem you are having, nor what Linux distro and version you are using. This thread has several things mixed into it, and at least one or two person's problems solved (one was corrupted named.conf, the other was running SELinux)

Please clarify your exact problem and OS and OS version, exact Plesk version would help also.
 
Same error for me :(

Nov 22 05:56:09 server named[18156]: could not configure root hints from '/var/named/run-root/var/named.root': file not found
Nov 22 05:56:09 server named[18156]: loading configuration: file not found
Nov 22 05:56:09 server named[18156]: exiting (due to fatal error)

but the file is there

Edit: Seems to be working now.
 
exiting (due to fatal error)
Mostly this would occur if there were something wrong in the /etc/named.conf file, or if the file was edited on a WIndows PC and uploaded (CR-LF problem). I say 'mostly' because there could be other problems which may also cause named to not start.
 
Sorry to bump this old topic but I'm having the same problem. I tried the suggestion and I got the same message as VictorySaber. When I check the messages file this is what I get.

Oct 18 05:46:00 www named[8892]: starting BIND 9.2.4 -u named -c /etc/named.conf -u named -t /var/named/run-root
Oct 18 05:46:00 www named[8892]: using 1 CPU
Oct 18 05:46:00 www named[8892]: loading configuration from '/etc/named.conf'
Oct 18 05:46:00 www named[8892]: no IPv6 interfaces found
Oct 18 05:46:00 www named[8892]: listening on IPv4 interface lo, 127.0.0.1#53
Oct 18 05:46:00 www named[8892]: listening on IPv4 interface eth0, 66.90.73.182#53
Oct 18 05:46:00 www named[8892]: command channel listening on 127.0.0.1#953
Oct 18 05:46:00 www named[8892]: couldn't open pid file '/var/run/named/named.pid': Permission denied
Oct 18 05:46:00 www named[8892]: exiting (due to early fatal error)
Oct 18 05:46:00 www named: named startup failed
 
Ok I fixed the problem. The dir named inside /var/named/run-root/var/run/named was owned by root. I was doing chown on the wrong directory.
 
Originally posted by networkthinking
Sorry, I got the first part with no problem but the last line...

4) for x in `ls`; do /usr/local/psa/admin/sbin/dnsmng update $x; done;/etc/init.d/named restart

This is throwing me for a loop. Does all of that go on one line? Sorry, in advance I'm not getting this part. i typed and got the following

/usr/local/psa/admin/sbin/dnsmng update $x; done;/etc/init.d.named restart

bash: syntax error near unexpected token `done'

I really dont understand this line either. Can anyone help.

Getting bash: syntax error near unexpected token `done'
 
don't you loose all domains in the named.conf

does this method mean I have to renter al domains into named.conf? any easy way to let Plesk automatically pick up all domains on the server onto named.conf? did I miss sothing?

Help appreciated. Godaddy is useless by all means
 
Back
Top