[Pacemaker] How to delay first monitor op upon resource start?

Gianluca Cecchi gianluca.cecchi at gmail.com
Thu Mar 13 13:00:16 EDT 2014

I have some init based scripts that I configure as lsb resources.
They are java based (in this case ovirt-engine and
ovirt-websocket-proxy from oVirt project) and they are started through
the rhel "daemon" function.
Basically it needs a few seconds before the scripts exit and the
status option returns ok.
So most of times when used as resources in pacemaker, their start is
registered as FAILED because the "status" call happens too quickly.
In the mean time I solved the problem putting a "sleep 5" before the
exit, but I would like to know if I can set a resource or cluster
parameter so that the first status monitor after start is delayed.
So I don't need to ask maintainer to make the change to the script and
I don't need after every update to remember to re-modify the script.

Another option would be to try the status after start more than once
so that eventually the first time is not ok, but it is so the second

Thanks in advance,

More information about the Pacemaker mailing list