On 06.02.2014 00:39, Andrew Beekhof wrote:
On 5 Feb 2014, at 2:57 pm, Dennis Jacobfeuerborn <denni...@conversis.de> wrote:
On 05.02.2014 04:06, Andrew Beekhof wrote:
On 3 Feb 2014, at 11:34 pm, Frank Brendel <frank.bren...@eurolog.com> wrote:
As far as I know, Pacemaker does not parse STDOUT but it keeps STDERR
for logging.
Experts correct me if I am wrong.
You are correct
[snip]
Does nobody have an idea? I checked this link:
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/ap-lsb.html
This doesn't seem to have anything to do with what pacemaker is
actually checking the status result against though.
$? holds the return code from the command you just ran.
This is the value pacemaker is looking for
The return code of "service ipsec status"
That is not the command pacemaker is running though, so the result may differ
from: /etc/init.d/ipsec status
Also assuming you're not on a systemd system, since service redirects to the
systemd unit file instead of the init script.
I decided to rebuild the cluster because of the strange behaviour in
order to make sure everything is in a clean state and now I cannot
reproduce this anymore. Openswan not starts as before but I no longer
get the monitor failures. For now everything works as it should.
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
