Re: [Pacemaker] Stopping resource using pcs

Deleting master resource id does not work. I see the same issue. However, uncloning helps. Delete works after disabling and uncloning. I see anissue in using --wait option with disable. Resources moves into stopped state but still error an error message is printed. When --wait option is not prov

Re: [Pacemaker] getting started with development

- Original Message - > From: "Tasim Noor" > To: pacemaker@oss.clusterlabs.org > Sent: Tuesday, February 25, 2014 5:10:33 PM > Subject: [Pacemaker] getting started with development > > Hi All, > I would be interested in contributing to the pacemaker/linux HA codebase. I > did look through

Re: [Pacemaker] Stopping resource using pcs

- Original Message - > From: "Frank Brendel" > To: pacemaker@oss.clusterlabs.org > Sent: Wednesday, February 26, 2014 8:53:19 AM > Subject: Re: [Pacemaker] Stopping resource using pcs > > I guess we need some real experts here. > > I think it's because you're attempting to delete the res

Re: [Pacemaker] [corosync] corosync Segmentation fault.

Andrey Groshev napsal(a): > > > 26.02.2014, 16:11, "Jan Friesse" : >> Andrey, >> can you please give a try to patch "[PATCH] votequorum: Properly >> initialize atb and atb_string" which I've sent to ML (it should be there >> soon)? > > Yes. Service is running. Thanks. > > # corosync-quorumtool

Re: [Pacemaker] Stopping resource using pcs

I guess we need some real experts here. I think it's because you're attempting to delete the resource and not the Master. Try deleting the Master instead of the resource. I had a similar problem with a cloned group and solved it by un-cloning before deleting the group. Maybe un-cloning the m

Re: [Pacemaker] [corosync] corosync Segmentation fault.

26.02.2014, 16:11, "Jan Friesse" : > Andrey, > can you please give a try to patch "[PATCH] votequorum: Properly > initialize atb and atb_string" which I've sent to ML (it should be there > soon)? Yes. Service is running. Thanks. # corosync-quorumtool -l Membership information -

Re: [Pacemaker] Stopping resource using pcs

Here is the config and output of few commands [root@sys11 ~]# pcs config Cluster Name: kpacemaker1.1 Corosync Nodes: Pacemaker Nodes: sys11 sys12 Resources: Master: ms-de5566b1-c2a3-4dc6-9712-c82bb43f19d8 Meta Attrs: clone-max=2 globally-unique=false target-role=Started Resource: vha-de556

Re: [Pacemaker] Get group behaviour with Master slave or clones envolved

2014-02-18 0:47 GMT+01:00 Andrew Beekhof : > > On 17 Feb 2014, at 10:34 pm, Néstor C. wrote: > > > > > > > > > 2014-02-17 1:22 GMT+01:00 Andrew Beekhof : > > > > On 21 Jan 2014, at 10:50 pm, Néstor C. wrote: > > > > >> Hello. > > >> > > >> When you need that some primitives switch in block you c

Re: [Pacemaker] Stopping resource using pcs

With force option, resource gets deleted. But the question is, why should the stop fail. Setup has two systems and there is only one resource (multi state type). Things work fine with crm commands. With pcs command, delete command tries to stop but fails. Looked at pcs resource.py script and afte

Re: [Pacemaker] [corosync] corosync Segmentation fault.

Andrey, can you please give a try to patch "[PATCH] votequorum: Properly initialize atb and atb_string" which I've sent to ML (it should be there soon)? Thanks, Honza Andrey Groshev napsal(a): > > > 26.02.2014, 12:11, "Jan Friesse" : >> Andrey, >> what version of corosync and libqb are you us

Re: [Pacemaker] Stopping resource using pcs

An overview of your setup/configuration would be nice. What was the cluster status before you tried to delete the resource? And did you try the --force option? Am 26.02.2014 11:46, schrieb K Mehta: Here is the log [root@sys11 ~]# pcs resource delete vha-de5566b1-c2a3-4dc6-9712-c82bb43f19d8 Fe

Re: [Pacemaker] Stopping resource using pcs

Here is the log [root@sys11 ~]# pcs resource delete vha-de5566b1-c2a3-4dc6-9712-c82bb43f19d8 Feb 26 02:28:16 sys11 cibadmin[5072]: notice: crm_log_args: Invoked: /usr/sbin/cibadmin -Q --xpath //master[@id="vha-de5566b1-c2a3-4dc6-9712-c82bb43f19d8"] Feb 26 02:28:16 sys11 cibadmin[5073]: notice:

Re: [Pacemaker] [corosync] corosync Segmentation fault.

26.02.2014, 12:11, "Jan Friesse" : > Andrey, > what version of corosync and libqb are you using? > > Can you please attach output from valgrind (and gdb backtrace)? ,,, 1314qb_loop_run (corosync_poll_handle); (gdb) n Program received signal SIGSEGV, Segmentation fault. 0x

Re: [Pacemaker] [corosync] corosync Segmentation fault.

Andrey, what version of corosync and libqb are you using? Can you please attach output from valgrind (and gdb backtrace)? Thanks, Honza Andrey Groshev napsal(a): > Hi, ALL. > Something I already confused, or after updating any package or myself > something broke, > but call corosycn killed b