On 20/09/2013, at 10:46 AM, Lists wrote:
> On 09/19/2013 04:50 PM, Andrew Beekhof wrote:
>> From this we can infer that corosync has gotten horribly confused and, as a
>> consequence, pacemaker can't talk to its peers anymore.
>>
>>> >this is a test cluster and not being monitored by a netmon.
On 09/19/2013 04:50 PM, Andrew Beekhof wrote:
From this we can infer that corosync has gotten horribly confused and, as a
consequence, pacemaker can't talk to its peers anymore.
>this is a test cluster and not being monitored by a netmon. Any other details
I could provide that would be usefu
On 09/18/2013 06:49 PM, Andrew Beekhof wrote:
On 19/09/2013, at 8:25 AM, David Lang wrote:
What's the best way to see what it's getting stuck doing?
Log files.
Is there a good way to tell if this is a pacemaker or corosync problem (so I
can drop one of the lists from the thread)?
Not with
On 20/09/2013, at 8:19 AM, Lists wrote:
> On 09/18/2013 06:49 PM, Andrew Beekhof wrote:
>> On 19/09/2013, at 8:25 AM, David Lang wrote:
>>
>>> What's the best way to see what it's getting stuck doing?
>> Log files.
>>
>>> Is there a good way to tell if this is a pacemaker or corosync problem
On 19/09/2013, at 8:25 AM, David Lang wrote:
> I have been using heartbeat for many years, but am now setting up some new
> clusters with pacemaker/corosync. I'm not sure which component is having
> problems so I'm sending to both lists.
>
> These are two machine clusters, configured per the
