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" is always 0 yet crm status
shows the failure:
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
When I change the init script to modify what the status command prints
out to something that looks like what the other scripts print then the
error goes away. This suggests that what the status command outputs to
stdout does indeed matter.
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
