On Wed, Feb 6, 2013 at 9:24 PM, Michael Schwartzkopff
<[email protected]> wrote:
> Am Mittwoch, 6. Februar 2013, 11:06:23 schrieb Roman Haefeli:
>> Hi all
>>
>> We are running a pacemaker/corosync cluster with three nodes that
>> manages ~30 OpenVZ containers.
>>
>> We recently had the situation where one node fenced the to other two
>> nodes (sbd is configured as a stonith device). In the system logs I was
>> able to spot the line where the node gives the death pill to the others.
>> However, I have difficulties finding the original reason for the
>> decision to fence the other nodes.
>>
>> Before I spam the list with logs, I'd like to ask if there is something
>> particular I should look for. Are there any advices about how to proceed
>> in such a situation?
>>
>> Many thanks in advance.
>>
>> Roman
>
> The reasong should be in the logs above the fencing event. Something like
>
> corosync: lost connection.
Or if pacemaker is new enough, look for "pe_fence_node" which contains:
crm_warn("Node %s will be fenced %s", node->details->uname, reason);
That should give you a good place to start.
>
> If you want help from the list paste your logs (the relevant parts only!) to
> pastebin and mail the link.
>
> Greetings,
>
> --
> Dr. Michael Schwartzkopff
> Guardinistr. 63
> 81375 München
>
> Tel: (0163) 172 50 98
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
