[Pacemaker] Bug in "ping" pacemaker resource agent

Maros Timko timkom at gmail.com
Thu Jan 28 13:38:05 EST 2010


Hi all,

this one worked for me. I also added debug parameter defaulted to
false to prevent logging on every attr update.

Tino

2010/1/28 Maros Timko <timkom at gmail.com>:
> Unfortunately, this is not the only bug of this RA.
> 1. There is absolute mess regarding the status file - some part of
> code uses OCF_RESKEY_pidfile, some uses $OCF_RESKEY_state. It means
> that the status handling does not work and you will end up with
> following failure:
> Jan 28 16:45:08 vsp7 lrmd: [17862]: info: RA output:
> (ping:0:stop:stderr) rm: missing operand Try `rm --help' for more
> information.
>
> 2. In validate-all there is also check $OCF_RESKEY_interval that has
> no source, I am not sure if this should be dampen parameter or
> $OCF_RESKEY_CRM_meta_interval.
>
> I will try to fix that because it seems to be very interesting RA for
> production.
>
> Tino
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ping.patch
Type: application/octet-stream
Size: 4821 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100128/3a0df2ce/attachment-0001.obj>


More information about the Pacemaker mailing list