Re: [Pacemaker] Quorum in pacemaker

On 2 Jul 2014, at 1:46 pm, Vijay B wrote: > Hi Emmanuel, > > Thanks for the response! I thought cman is a newer version of corosync itself, older actually. even though you're technically using cman, corosync is doing all the heavy lifting underneath. > w.r.t the plugin that is used between c

[Pacemaker] Resources not failing over, ERROR: RecurringOp: Invalid recurring action ... wth name: 'start'

Hi, I'm puppetizing resource deployment for pacemaker and corosync, and as part of it, am creating a resource on one of three nodes of a cluster. The problem is that I'm seeing RecurringOp errors during resource creation, which are probably not allowing failover a resource. The resource creation s

Re: [Pacemaker] Quorum in pacemaker

Hi Emmanuel, Thanks for the response! I thought cman is a newer version of corosync itself, w.r.t the plugin that is used between corosync (cluster membership) and pacemaker (resource group management) - is that not the case? I installed the pacemaker and cman packages on ubuntu 12.04, and no pack

Re: [Pacemaker] Quorum in pacemaker

Hi Andrew, Thanks for the responses! I set the cman quorum timeout to 0, and the first node came up. However, I'm seeing newer issues now that I hadn't seen before, when creating a resource of an LSB compliant service. I will send another mail to the ML to keep that discussion separate. Regards,

Re: [Pacemaker] crm_verify reports bogus "requires fencing but fencing is disabled" notices

Can you send us the 'cibadmin -Ql' output? On 2 Jul 2014, at 3:30 am, Ron Kerry wrote: > I have seen the following reporting coming out of crm_verify that is clearly > misleading to a sysadmin. Every resource defined with this sort of start/stop > operations is called out twice (presumably bec

Re: [Pacemaker] rc=5 with DRBD

Bart, I've no experience with the DRBD RA but I guess I can give you a few hints. >From my experience on other RA, NOT_INSTALLED error doesn't necessary mean that some tools are not installed. It might mean that a requirement of DRBD is not properly setup (can be an external tool, but could be a c

[Pacemaker] rc=5 with DRBD

Hi, I get this error message for every DRBD resource I have: notice: unpack_rsc_op: Preventing ms_drbd_lx06 from re-starting on storage3: operation stop failed 'not installed' (rc=5) The OCF return codes table points to required tools missing, but I cannot find which tools are missing.

Re: [Pacemaker] crm_verify reports bogus "requires fencing but fencing is disabled" notices

Note: The bogus reporting only seems to be an issue with a live check (-L). If you check a stored pe-input file (even from the same time frame), it does not report these issues. On 7/1/14, 1:30 PM, Ron Kerry wrote: I have seen the following reporting coming out of crm_verify that is clearly

[Pacemaker] crm_verify reports bogus "requires fencing but fencing is disabled" notices

I have seen the following reporting coming out of crm_verify that is clearly misleading to a sysadmin. Every resource defined with this sort of start/stop operations is called out twice (presumably because this is a 2-node cluster) op start interval="0" timeout="xx" on-fail="restart" requires

[Pacemaker] testquorum module

Hi Chrissie, You mentioned "testquorum" in your doc ("Whatever happened to cman") as it's a good place if you are thinking about writing your own quorum module. The only file I found in corosync code is in /test folder and I think it's not the module. Could you please point me where I can find thi