named dead but subsys locked

[agriz]

I tried to restart named. But it is still displaying the same message when i type

 service named status 
  

centos 6 64 bit.
Please let me know how to fix this

[Irithori]

That means, that bind crashed or was shutdown uncleanly and there is a stale lock file /var/lock/subsys/named


Make sure, bind is not running, delete the lock file,
then start the service.

[agriz]

How do i delete the lock?
Bind means, named right?

[agriz]

I was having problem with chroot.
So i uninstalled that. Now just running bind without chroot.

I found this.

 root  root     25 Jan 23 16:16 named.pid -> //var/run/named/named.pid 
  

under /var/run/

It is in red color.

 /var/run/named/named.pid 
  

is not exist

Is it ln with /var/run/named/named.pid?
How do we fix this?

[Irithori]

Try deleting /var/run/named/named.pid and starting bind.

[agriz]

Try deleting /var/run/named/named.pid and starting bind.

The file is not there actually.

1) I created a new file named.pid in /var/run/named/ and gave root:named with 755 permission and restarted.
2) Removed symlink to /var/run/named.pid and restarted.

Whenever i restart the named, /var/run/named.pid is getting linked with /var/run/named/named.pid
Not fixed

[atreyu]

Do you have yum configured, and an internet connection? If so, how about reinstalling the package? Maybe permissions got fubar.

First a little clean-up:

service named stop
rm -rf /var/run/named*
rm -f /var/lock/subsys/named

Then remove and install:

rpm -e bind --nodeps
yum install bind

[agriz]

named.conf contains /var/run/named.pid as location
init.d contains /var/run/named/named.pid

I changed the location in named.conf to /var/run/named/named.pid
Now it is running.