nrpe dead but subsys locked error
service dead but subsys locked
check if the port used by nrpe is already used by other processess like xinetd
netstat -tulnp | grep 5666
or
lsof -ni udp:5666
lsof -ni tcp:5666
service dead but subsys locked
check if the port used by nrpe is already used by other processess like xinetd
netstat -tulnp | grep 5666
or
lsof -ni udp:5666
lsof -ni tcp:5666
This means the service was running at one time, but has crashed.
When you start a service, it creates a "lock" file to indicate that the service is running. This helps avoid multiple instances of the service. When you stop a service, this lock file is removed.
When a running service crashes, the lock file exists but the process no longer exists. Thus, the message.
Look at the two areas
http://serverfault.com/questions/26276/what-does-service-name-dead-but-subsys-locked-mean
http://www.linuxquestions.org/questions/linux-networking-3/service-dead-but-subsys-locked-376488/
When you start a service, it creates a "lock" file to indicate that the service is running. This helps avoid multiple instances of the service. When you stop a service, this lock file is removed.
When a running service crashes, the lock file exists but the process no longer exists. Thus, the message.
Look at the two areas
/var/run/*.pid and /var/lock/subsys/*. These are expected to agree with each other. That is, if the (emtpy file) lockfile /var/lock/subsys/crond exists, then the first line of the file /var/run/crond.pid
is expected to contain the PID of the process running for this service.
If no such process is running, then something is wrong. If a process
is indeed running (as you see) but it is not that PID, then something is probably confused.http://serverfault.com/questions/26276/what-does-service-name-dead-but-subsys-locked-mean
http://www.linuxquestions.org/questions/linux-networking-3/service-dead-but-subsys-locked-376488/
No comments:
Post a Comment