Hi I use pacemaker 1.0.11 and pingd RA. Occasionally, pingd's first monitor is failed after start.
It seems that the main cause is pingd daemon returns 0 before creating pidfile
and RA doesn't check pidfile on start.
test script
-------------------------------------
while true; do
killall pingd; sleep 3
rm -f /tmp/pingd.pid; sleep 1
/usr/lib64/heartbeat/pingd -D -p /tmp/pingd.pid -a ping_status -d
0 -m 100 -h 192.168.0.1
echo $?
ls /tmp/pingd.pid; sleep .1
ls /tmp/pingd.pid
done
-------------------------------------
result
-------------------------------------
0
/tmp/pingd.pid
/tmp/pingd.pid
0
ls: cannot access /tmp/pingd.pid: No such file or directory <- NG
/tmp/pingd.pid
0
/tmp/pingd.pid
/tmp/pingd.pid
0
/tmp/pingd.pid
/tmp/pingd.pid
0
/tmp/pingd.pid
/tmp/pingd.pid
0
ls: cannot access /tmp/pingd.pid: No such file or directory <- NG
/tmp/pingd.pid
--------------------------------------
Please consider the attached patch for pacemaker-1.0.
Regards,
Takatoshi MATSUO
pingd_check_pid.patch
Description: Binary data
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
