On 2011-10-27T13:39:10, Ulrich Windl <[email protected]> wrote:
> According to the docs, the status/monitor operation may not return
> OCF_ERR_INSTALLED, but only OCF-ERR_GENERIC if something is wrong (eg.
> required software not installed).
That is not correct, where did you read that?
Basically, the logic is a bit different - OCF_NOT_RUNNING should be
returned if the service is down cleanly, regardless of whether binaries
are present or not.
OCF_ERR_GENERIC should only be returned if it is up in some form and not
cleanly stopped nor running.
> Only start and stop methods are allowed to return OCF_ERR_INSTALLED,
> possibly preventing a resource start if something is not
> configured/installed.
Yes, they can also return this.
> Now I'm afraid if the status/monitor returns OCF_ERR_GENERIC on a probe the
> node is fenced: LRM will try to stop that resource, but the stop will return
> OCF_ERR_INSTALLED, causing a fence. Right?
Depends. "stop" should return success if the service is cleanly stopped,
regardless of whether binaries etc are present or not.
Returning OCF_ERR_GENERIC for the startup probe is a bad idea, because
it'll trigger the multi-node recovery logic. (Unless, of course, it is
indeed up.)
> I think the status/monitor should be allowed to return OCF_ERR_INSTALLED.
They can, it'll just cause the service to be started on that node. If
the installation error is unlikely to be remedied by further
dependencies having started, that may be just the right answer.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
