named has failed, please contact the sysadmin (result was "named is not running").

[NDP]

Hey

I am using Fedora OS with CPanel/WHM. I am getting regular emails about the DNS Service failing. I have tried to restart it but get:

named has failed, please contact the sysadmin (result was "named is not running").

I have tried to restart, stop and start, through ssh but this doesnt work. Although no errors come up (except when i run stop it fails)

Any ideas why this can be?

Thanks in advance!!

 

[AndyReed]

named has failed, please contact the sysadmin (result was "named is not running").

To troubleshoot named problems, the first thing you need to do is to check the log files for errors. Then run:
/scripts/fixnamed
/scripts/fixndc
/scripts/restartsrv_named

 

[dreamwiz]

I had similar issues yesterday. Check that there is no named-related processes running in the server, then try to restart named. If you have DNS Cluster, allow some time for it to sync...

tail -f /var/log/messages

My named still fails like 2-3 times in a day, for unknown reason. It can take up to 30 mins to sync with cluster after restart. This might be cpanel-related problem, any ideas what is causing it?

EDIT:

I found the following from /var/log/messages
---
named[19210]: errno2result.c:109: unexpected error:
named[19210]: unable to convert errno to isc_result: 14: Bad address
named[19210]: UDP client handler shutting down due to fatal receive error: unexpected error

 

[NDP]

Thanks for the advice, however, i still have not made any progress. My log files do not show anything to do with named! It just seems someone from Taiwan has tried to access my SSH and failed to get in.

Also, I ran the three commands as suggested.

Results

1. /scripts/fixnamed

Nothing happens. Just goes back to command line and waits for next instruction!?

2. /scripts/fixndc

Slightly more interesting/worrying! I get a whole list of errors, literally 100s of lines long! A snippet off what i got is here:

chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: No such file or directory while reading flags on /var/named/chroot/proc/
chattr: No such file or directory while reading flags on /var/named/chroot/proc/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: No such file or directory while reading flags on /var/named/chroot/proc/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Invalid argument while reading flags on /var/named/chroot/proc/19255/mou
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/
chattr: Inappropriate ioctl for device while reading flags on /var/named/chroot/

I am totally confused and lost!!!! What does this mean? What has gone wrong?! I havent actually changed any settings!

3. /scripts/restartsrv_named

[email protected] [~]# /scripts/restartsrv_named
Starting named: named: already running [FAILED]

This is the error as i had previously got and so was no surprise!


I am taking a wild guess and will say its probably the 2nd stage i should take a look further into. But where do i begin? Any ideas?

Thanks in Advance!!

 

[NDP]

I finally get somewhere! (I think!)

Now when i try to restart BIND i get this:

named has failed, please contact the sysadmin (result was "named is not running"). Jun 28 18:35:42 new named[21633]: starting BIND 9.3.1 -u named -t /var/named/chroot Jun 28 18:35:42 new named[21633]: found 1 CPU, using 1 worker thread Jun 28 18:35:43 new named[21633]: loading configuration from '/etc/named.conf' Jun 28 18:35:43 new named[21633]: /etc/named.conf:1: open: /etc/rndc.key: permission denied Jun 28 18:35:43 new named[21633]: loading configuration: permission denied Jun 28 18:35:43 new named[21633]: exiting (due to fatal error)

 

[dreamwiz]

I finally get somewhere! (I think!)

Now when i try to restart BIND i get this:

You seem to have problems with the permissions. Try to check those out, also reinstalling Bind might help. You can do it thru WHM's install RPM.

 

[NDP]

I tried a CPanel update and now cant access cpanel or whm at all - http://forums.cpanel.net/showthread.php?p=258318

 

[Glasswalker]

I just experienced the same problem...

I restored /etc/named.conf and /var/named from whm backups made (I make full server backups daily) but it didn't help... then I ran the above scripts, and WHAM fixed...

My question is... What the heck caused this? This is a known issue? (since the scripts exist). How is this acceptable?

If my server reboots for some reason, I don't want named to randomly corrupt itself... that isn't cool... This appears to be specific to cpanel, because others I have spoken with have never encountered this. And most point the finger immediatly at cpanel...

 

[hitekweb]

Named & RNDC Not Working

Ok I have had this problem for the for time and I must say it was a pain in the @$$ but here is the best way that I have found to take care of the progblem.

REINSTALL BIND

You are thinking awsome a answer how do I reinstall bind easy just do


yum remove bind
It will ask you at the bottom to hit Y or N HIT Y for each of them
then
yum remove bind-libs
It will ask you at the bottom to hit Y or N HIT Y for each of them
then
yum remove bind-utils
It will ask you at the bottom to hit Y or N HIT Y for each of them



Then you will want to install them again so you login to whm as root and on your left scroll down til you see SOFTWARE and look for the link that says Install A RPM

You will then want to install all of the three that your removed.


Hope this help you guys

 

[aykfounder]

The above works, just don't forget to copy the backed up named.conf file or none of your sites will resolve.

Also, you can try /scripts/fixndc after the above if necessary.

 

[aykfounder]

Also, just a note on this. Reply from one of Cpanel reps:

The most common issue with fresh install is this one in the installed RPMS for bind: bind-chroot-9.2.4-24.EL4

Once you un-install that, it runs fine afterwards. Cpanel do not work well with bind-chroot installations. I have removed that and restarted bind, so you are all set for this.

We asked them specifically and this is certainly much quicker than uninstalling everything and then reinstalling it again. Hope this helps!

EDIT: To uninstall just use rpm -e bind-chroot-9.2.4-24.EL4

 

[aykfounder]

One other quick edit. We also got the following sometimes:

named has failed, please contact the sysadmin (result was "named is not running"). May 9 18:41:15 fast named[28235]: starting BIND 9.3.4 -u named May 9 18:41:15 fast named[28235]: found 1 CPU, using 1 worker thread May 9 18:41:15 fast named[28235]: loading configuration from '/etc/named.conf' May 9 18:41:15 fast named[28235]: /etc/named.conf:1: open: /etc/rndc.key: permission denied May 9 18:41:15 fast named[28235]: loading configuration: permission denied May 9 18:41:15 fast named[28235]: exiting (due to fatal error)

And that was after trying all of the above options. To fix this, we did the following:

chown named.named /etc/rndc.key
chown named.named /etc/named.conf

That fixed the problem and named was able to start.

 

[unomateo]

We are getting the same error:

named has failed, please contact the sysadmin (result was "named is not running"). May 10 23:07:12 14423-26474 named[20830]: starting BIND 9.3.1 -u named -t /var/named/chroot May 11 06:07:12 14423-26474 named[20830]: found 4 CPUs, using 4 worker threads May 11 06:07:12 14423-26474 named[20830]: loading configuration from '/etc/named.conf' May 11 06:07:12 14423-26474 named[20830]: none:0: open: /etc/named.conf: permission denied May 11 06:07:12 14423-26474 named[20830]: loading configuration: permission denied May 11 06:07:12 14423-26474 named[20830]: exiting (due to fatal error)

I tried all the above solutions but nothing has worked. We do not have an old named.conf file so i haven't tried that,

I tried chmod 777 /etc/named.conf
but didn't work.

I removed bind, and then reinstalled, didn't work.

we installed the fedora core 4, and then I upgraded WHM to 11

Please help

 

[aykfounder]

Why not go with FC5 as it's more compatible with Cpanel? Also, downgrade to Cpanel 10.9, not 11 would be my other advice.

If you have tried everything above, contact Cpanel directly for assistance.

 

[Snowman30]

ihave the same issue on a new cento 4.5 cpanel 11 install

ive tried all the suggested fixes and run an fsck and still no joy

anyone have a working solution?

 

[cPanelKenneth]

Why not go with FC5 as it's more compatible with Cpanel? Also, downgrade to Cpanel 10.9, not 11 would be my other advice.

If you have tried everything above, contact Cpanel directly for assistance.

Fedora Core 5 is nearing it's end of life.

Fedora Core 6, has a few months left.

Fedora 7 just emereged.

Fedora 8 is slated for October

Use CentOS.

ihave the same issue on a new cento 4.5 cpanel 11 install

ive tried all the suggested fixes and run an fsck and still no joy

anyone have a working solution?

Please post:

1. The ls -la output of /etc/named.*
2. The las -la output of /etc/rndc.*
3. Any output from the console or logs when attempting to start named (bind)
4. The output of rpm -qa | grep bind
5. The output of rpm -qa | grep name


Thanks.

 

[Ramgo]

so... more ideas?

 

[Snowman30]

Please post:

1. The ls -la output of /etc/named.*
2. The las -la output of /etc/rndc.*
3. Any output from the console or logs when attempting to start named (bind)
4. The output of rpm -qa | grep bind
5. The output of rpm -qa | grep name


Thanks.

ls -la /etc/named.*

-rw-r--r-- 1 root root 2209 Jun 12 14:04 /etc/named.conf
-rw-r--r-- 1 root root 2209 Jun 12 14:04 /etc/named.conf.fixrndc
-rw-r--r-- 1 root root 2209 Jun 12 14:04 /etc/named.conf.prefixrndc
-r--r--r-- 1 root root 5571 Jun 12 10:50 /etc/named.conf,v


ls -la /etc/rndc.*


-rw------- 1 named named 479 Jun 5 11:39 /etc/rndc.conf
-rw------- 1 root named 77 Jun 5 11:39 /etc/rndc.key
-rw-r----- 1 root named 77 Feb 7 21:35 /etc/rndc.key.rpmnew


rpm -qa | grep bind

no output


rpm -qa | grep name
caching-nameserver-7.3-3

Any output from the console or logs when attempting to start named (bind)
service named start
Starting named: [FAILED]

 

[nilesh_kolte]

Hello,

Try to use following steps.

cd /scripts;
service named stop
killall -9 named
mv /etc/named.conf /etc/named.old
./rebuildnamedconf > /etc/named.conf
./fixndc
./fixndc
ndc status

 

[duranduran]

Also, just a note on this. Reply from one of Cpanel reps:





We asked them specifically and this is certainly much quicker than uninstalling everything and then reinstalling it again. Hope this helps!

EDIT: To uninstall just use rpm -e bind-chroot-9.2.4-24.EL4

Perfect ! Worsk for me