[Pacemaker] LSB openswan script monitor problems

Michael Monette mmonette at 2keys.ca
Mon Jan 27 15:15:57 EST 2014

Not an expert..but I never used any timeout values for a monitor op. 

For stop and start ops I have the intervals at 0 and timeouts set to 240..

However for a monitor op the intervals are usually 30 and timeouts 0. 

It will monitor at intervals of 30. 

Remove the timeout part and I think you'll get different results


Dennis Jacobfeuerborn <dennisml at conversis.de> wrote:
>I'm trying to make an openswan setup redundant and this kind of works 
>but pacemaker reports errors like this on failover:
>p_ipsec_monitor_15000 on node02 'not running' (7): call=113, 
>status=complete, last-rc-change='Mon Jan 27 18:32:29 2014',
>The resource definition looks like this:
>primitive p_ipsec lsb:ipsec \
>	op monitor interval="15" timeout="15"
>The interesting bit is that the log shows no errors/warnings and the 
>service is running fine. After a bit of googling it appears that the 
>custom output of the status command is the culprit.
>Replacing it with a static string like "ipsec (pid 1111) is running..."
>seems to fix it but replacing "running" with "rnning" also seems to 
>work. Also outputting this line followed by the normal status output 
>fails as well.
>So my question is what exactly is pacemaker doing to determine if the 
>status call returned successfully if at all and what needs to be done
>I don't get the "not running" errors in pacemaker?
>   Dennis
>Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>Project Home: http://www.clusterlabs.org
>Getting started:
>Bugs: http://bugs.clusterlabs.org

Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140127/d9a19b42/attachment-0003.html>

More information about the Pacemaker mailing list