We get the same behavior on our lab controllers. However, beaker-proxy
is running despite the lack of a PID.
[ ~]# service beaker-proxy status
beaker-proxy dead but subsys locked
[ ~]# ps auxx | grep beaker-proxy
apache 25757 0.0 0.9 170700 9912 ? Sl 10:27 0:00
root 25776 0.0 0.0 61176 712 pts/0 R+ 10:29 0:00 grep
It looks like the init script for beaker-proxy isn't creating a pid in
/var/run, but is creating a lock file in /var/run/lock/subsys, so the
'status' query will fail.
On Mon, Aug 16, 2010 at 12:52:03PM +0800, 钧友 杨 wrote:
I want to setup lab controller as
Beaker-0.5-Administration_Guide-en-US.pdf, but when it comes to the step :
"$ sudo chkconfig beaker-watchdog on
$ sudo chkconfig beaker-proxy on
$ sudo service beaker-watchdog start
$ sudo service beaker-proxy start"
It's just failed because that when I use the command "service
beaker-watchdog status" to see the status of beaker-watchdog,it shows that
"beaker-watchdog dead but subsys locked".
Manager Engineering Operations, Westford +1 978 392 2442