Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
Am 05.06.2013 um 04:04 schrieb Andrew Beekhof : But no resources are started, so I suspect there really is quorum. >>> >>> Can you send me the output of cibadmin -Ql please? >>> Perhaps those two resources are blocked for other reasons. > > It looks like you may have hit a bug in an older

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Andrew Beekhof
On 05/06/2013, at 12:15 PM, Denis Witt wrote: > > Am 05.06.2013 um 04:04 schrieb Andrew Beekhof : > > But no resources are started, so I suspect there really is quorum. Can you send me the output of cibadmin -Ql please? Perhaps those two resources are blocked for other rea

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Andrew Beekhof
On 05/06/2013, at 11:55 AM, Denis Witt wrote: > > Am 05.06.2013 um 03:34 schrieb Andrew Beekhof : > >>> But no resources are started, so I suspect there really is quorum. >> >> Can you send me the output of cibadmin -Ql please? >> Perhaps those two resources are blocked for other reasons. I

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
Am 05.06.2013 um 03:34 schrieb Andrew Beekhof : >> But no resources are started, so I suspect there really is quorum. > > Can you send me the output of cibadmin -Ql please? > Perhaps those two resources are blocked for other reasons. Hi Andrew, here we go:

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Andrew Beekhof
On 05/06/2013, at 10:43 AM, Denis Witt wrote: > > Am 05.06.2013 um 02:15 schrieb Andrew Beekhof : > >>> Jun 5 01:11:06 test4 pengine: [18625]: WARN: cluster_status: We do not >>> have quorum - fencing and resource management disabled >>> Jun 5 01:11:06 test4 pengine: [18625]: notice: LogAc

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
Am 05.06.2013 um 02:15 schrieb Andrew Beekhof : >> Jun 5 01:11:06 test4 pengine: [18625]: WARN: cluster_status: We do not have >> quorum - fencing and resource management disabled >> Jun 5 01:11:06 test4 pengine: [18625]: notice: LogActions: Start >> pingtest:0#011(test4 - blocked) >> Jun

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Andrew Beekhof
On 05/06/2013, at 9:22 AM, Denis Witt wrote: > > Am 05.06.2013 um 00:52 schrieb Andrew Beekhof : > >>> been restored the resources aren't restarted. Running crm_resource -P >>> brings anything up, but of course it would be nice if this happens >>> automatically. Is there any way to archive th

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
Am 05.06.2013 um 00:52 schrieb Andrew Beekhof : >> been restored the resources aren't restarted. Running crm_resource -P >> brings anything up, but of course it would be nice if this happens >> automatically. Is there any way to archive this? > > It should happen automatically. > Logs? Hi Andre

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Andrew Beekhof
On 05/06/2013, at 2:13 AM, Denis Witt wrote: > Hi List, > > I have a cluster with two nodes running services, to make the Cluster > more reliable I added a third node with no services (I didn't start > pacemaker there, only corosync). I can't use STONITH in my setup so I > choose no-quorum-pol

[Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
Hi List, I have a cluster with two nodes running services, to make the Cluster more reliable I added a third node with no services (I didn't start pacemaker there, only corosync). I can't use STONITH in my setup so I choose no-quorum-policy=stop to avoid data corruption on my DRBD-Resources. The s