[ClusterLabs] Antw: Re: difference between OCF return codes for monitor action
Ulrich.Windl at rz.uni-regensburg.de
Thu Oct 22 03:21:30 EDT 2015
I think the RAs' exit codes should be defined on the resource (agent)'s state
only, not on the reaction pacemaker will perform. Otherwise the idea of
universal resource agents will never work.
>>> "Vallevand, Mark K" <Mark.Vallevand at UNISYS.com> schrieb am 21.10.2015 um
<6555c5b6072f4eb097ef25488b3a574d at US-EXCH13-5.na.uis.unisys.com>:
> In my resource agent, I use OCF_NOT_RUNNING to indicate that the managed
> resource is literally ‘not running’. I use OCF_ERR_GENERIC to indicate
> the managed resource is running, but has entered an error state. It is
> potentially recoverable if it is restarted. I use OCF_ERR_PERM to indicate
> the managed resource has entered an error state which would not be
> recoverable if it is restarted. The resource usually restarts on another
> Mark K Vallevand
Mark.Vallevand at Unisys.com<mailto:Mark.Vallevand at Unisys.com>
> Never try and teach a pig to sing: it's a waste of time, and it annoys the
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
> From: Kostiantyn Ponomarenko [mailto:konstantin.ponomarenko at gmail.com]
> Sent: Wednesday, October 21, 2015 07:44 AM
> To: Cluster Labs - All topics related to open-source clustering welcomed
> Subject: [ClusterLabs] difference between OCF return codes for monitor
> What is the difference between "OCF_ERR_GENERIC" and "OCF_NOT_RUNNING"
> return codes in "monitor" action from the Pacemaker's point of view?
> I was looking here
> -return-codes.html , but I still don't see the difference clearly.
> Thank you,
More information about the Users