On 06.02.2014 00:39, Andrew Beekhof wrote:
On 5 Feb 2014, at 2:57 pm, Dennis Jacobfeuerborn wrote:
On 05.02.2014 04:06, Andrew Beekhof wrote:
On 3 Feb 2014, at 11:34 pm, Frank Brendel wrote:
As far as I know, Pacemaker does not parse STDOUT but it keeps STDERR
for logging.
Experts correc
On 5 Feb 2014, at 2:57 pm, Dennis Jacobfeuerborn wrote:
> On 05.02.2014 04:06, Andrew Beekhof wrote:
>>
>> On 3 Feb 2014, at 11:34 pm, Frank Brendel wrote:
>>
>>> As far as I know, Pacemaker does not parse STDOUT but it keeps STDERR
>>> for logging.
>>> Experts correct me if I am wrong.
>>
>
Please could you post the init script, the resource configuration and
the pacemaker version?
Frank
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 2
On 05.02.2014 04:06, Andrew Beekhof wrote:
On 3 Feb 2014, at 11:34 pm, Frank Brendel 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://c
On 3 Feb 2014, at 11:34 pm, Frank Brendel 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/Pacemak
As far as I know, Pacemaker does not parse STDOUT but it keeps STDERR
for logging.
Experts correct me if I am wrong.
The important thing is the return value of the ipsec script.
You could debug the ipsec script. If it is a Bash script you can put a
logger command after each 'RETVAL=$?'.
Example
On 27.01.2014 19:41, Dennis Jacobfeuerborn 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',
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 co
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
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
Dennis Jacobfeuerborn wrote:
>Hi,
>I'm trying to make an openswan setup redundant and thi
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 definitio
11 matches
Mail list logo
