Re: [ClusterLabs] difference between OCF return codes for monitor action
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 that 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 node. Regards. Mark K Vallevand mark.vallev...@unisys.com<mailto:mark.vallev...@unisys.com> Never try and teach a pig to sing: it's a waste of time, and it annoys the pig. 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.ponomare...@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 action Hi, 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 http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-ocf-return-codes.html , but I still don't see the difference clearly. Thank you, Kostya ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] difference between OCF return codes for monitor action
On 10/21/2015 07:44 AM, Kostiantyn Ponomarenko wrote: > Hi, > > 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 > http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-ocf-return-codes.html > , but I still don't see the difference clearly. > > Thank you, > Kostya OCF_ERR_GENERIC is a "soft" error, so if any operation returns that, Pacemaker will try to recover the resource by restarting it or moving it to a new location. OCF_NOT_RUNNING is a state (not necessarily an error). When first placing a resource, Pacemaker will (by default) run monitors for it on all hosts, to make sure it's not already running somewhere. So in that case (which is usually where you see this), it's not an error, but a confirmation of the expected state. On the other hand, if Pacemaker gets this when a resource is expected to be up, it will consider it an error and try to recover. The only difference in that case is that Pacemaker will not try to stop the resource because it's already stopped. ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] difference between OCF return codes for monitor action
Hi, 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 http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-ocf-return-codes.html , but I still don't see the difference clearly. Thank you, Kostya ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] difference between OCF return codes for monitor action
Am Mittwoch, 21. Oktober 2015, 15:44:17 schrieb Kostiantyn Ponomarenko: > Hi, > > 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 > http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-oc > f-return-codes.html , but I still don't see the difference clearly. > > Thank you, > Kostya No differences from pacemaker point of view. Both are errors and pacemaker acts as configured. The return codes are for the admin to make it easier to find the cause. Mit freundlichen Grüßen, Michael Schwartzkopff -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein signature.asc Description: This is a digitally signed message part. ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org