# rpm -V bind
SM5...GT. c /etc/named.conf
S.5....T. c /etc/sysconfig/named
# cat /etc/sysconfig/named
Description of problem:
On startup ("service named start"), the following message is sent to stderr:
/etc/init.d/named: line 150: /var/named/chroot/var/run/named/named.pid: No such file or directory
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. service named [re]start
The service seems to be running. The command, "service named status" produces:
CPUs found: 2
worker threads: 2
number of zones: 6
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named dead but subsys locked
Those last two lines are unsettling. How can the service be "up and
running" and "dead" at the same time? I presume the locked complaint is
related to the stderr message produced at startup.
Would it be possible to tell me if you have "ROOTDIR" variable in /etc/sysconfig/named set and if you have "pid-file" directive in your named.conf, please?
As indicated in the Environment section of this report, I suspected the package had been corrupted. I deleted it and re-installed. The problem is now gone so I can't answer the question. Thanks for your response and I apologize for the noise.
(In reply to comment #2)
> As indicated in the Environment section of this report, I suspected the package
> had been corrupted. I deleted it and re-installed. The problem is now gone so I
> can't answer the question. Thanks for your response and I apologize for the
Thanks for feedback, closing.