Thanks Andrew.
I upgraded corosync and pacemaker and the cluster works fine now.
On Thu, Jan 8, 2015 at 8:26 AM, Andrew Beekhof wrote:
>
> > On 15 Dec 2014, at 4:29 pm, Bharathiraja P wrote:
> >
> > Hi Andrew,
> >
> > Frequently one node gets disconnected from CIB and stops the cluster
> resou
> On 15 Dec 2014, at 4:29 pm, Bharathiraja P wrote:
>
> Hi Andrew,
>
> Frequently one node gets disconnected from CIB and stops the cluster
> resources. I'm not able to start or cleanup failed actions for any of the
> resources. For ex, if nodeA gets disconnected from CIB, I won't be able to
Hi Andrew,
Frequently one node gets disconnected from CIB and stops the cluster
resources. I'm not able to start or cleanup failed actions for any of the
resources. For ex, if nodeA gets disconnected from CIB, I won't be able to
run actions on a resource like cleanup/stop/restart,... as that hangs
> On 12 Dec 2014, at 9:57 pm, Bharathiraja P wrote:
>
> Hi,
>
> We run pacemaker+corosync cluster on OpenSuSE 13.1 QEMU guests.
>
> Frequently, one node gets disconnected from cib. This is the message seen in
> corosync logs,
>
> Nov 25 08:36:07 [3760] sysmon-secondarycib:debug:
Hi,
We run pacemaker+corosync cluster on OpenSuSE 13.1 QEMU guests.
Frequently, one node gets disconnected from cib. This is the message seen
in corosync logs,
Nov 25 08:36:07 [3760] sysmon-secondarycib:debug:
qb_ipcs_dispatch_connection_request: HUP conn (3760-5529-13)
Nov 25 0
