named service problems after yum...

H

hpman28

Verified User
Joined
Aug 11, 2006
Messages
15
Hi All,

First, i read all the messages and http://help.directadmin.com/item.php?id=128.

I couldn't slove it. Now my main name server is down. luckily im using multi admin setup (the directadmin option), so i have secondary nameservers with duplicated data.

The problems started after doing yum upgrade from centos 4.5 to centos 4.6

My problem is that:
1. yum update. i saw it's installing new bind-9.2.4-28
2. tried to do services restart to make sure everything is working as expected. the named service wont do restart. i can even stop it with kill -9 #pid!
3. I can't restart the named anyway. checked /var/log/messages after issuing service named restart:

Code: 
Jan  9 06:54:00 server named: named -TERM succeeded
Jan  9 06:54:00 server named:  succeeded
Jan  9 06:54:02 server named:  failed

4. output of ps aux
Code: 
root@server sysconfig]# ps aux | grep named
named     4467  0.0  0.0     0    0 ?        Zs    2007  21:39 [named] <defunct>
root     26101  0.0  0.0     0    0 ?        Zs   06:20   0:00 [named] <defunct>
root     32287  0.0  0.0  5132  672 pts/0    S+   07:33   0:00 grep named
I can't kill these services! tried with kill -9 4467 and nothing
 
Last edited:
Check /etc/sysconfig/named

You've probably got the chroot variable set.
If so you need to look in a different location. like /var/named/chroot/var/named
 
Nope. i looked in that config settings

also /var/named/chroot/ doesn't exists , so it's not chroot issue
 
hpman28 said:
My problem is that:
1. yum update. i saw it's installing new bind-9.2.4-28
2. tried to do services restart to make sure everything is working as expected. the named service wont do restart. i can even stop it with kill -9 #pid!
3. I can't restart the named anyway. checked /var/log/messages after issuing service named restart
Click to expand...
It is difficult to say without looking into your server. It could be named.conf; bind is not installed properly or wasn't completed successfully; ownership or permission. I suggest you seek help from your host, or seek professional help.
 
We've never had a problem with the BIND boot script in CentOS, any version.

We have had problems with using a chrooted BIND, because DirectAdmin doesn't expect it, and puts file where they should be if BIND isn't chrooted.

Jeff
 
You must log in or register to reply here.
Back
Top