On 27.01.2014 21:18, Michael Monette wrote:
Also 1 more thing about your init script
You can make it simple just to test..change the status part to something
like this:
If ps aux | grep openswan
then
true
else
exit 3
done
I think this could help
The status command already returns a status code of 0 (success). That's
why I started messing with the output and found then when I change that
it actually plays a role. The question is what *exactly* does pacemaker
do test the result? I was unsuccessful in finding the place in the
pacemaker source where this call is made and the output analyzed.
Regards,
Dennis
Dennis Jacobfeuerborn <denni...@conversis.de> wrote:
Hi,
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', queued=37ms,
exec=0ms
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 so
I don't get the "not running" errors in pacemaker?
Regards,
Dennis
------------------------------------------------------------------------
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home:http://www.clusterlabs.org
Getting started:http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs:http://bugs.clusterlabs.org
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
