Re: [Pacemaker] Stopping resource using pcs

2014-03-05 Thread Frank Brendel
_is_ that the resource name though? From one of your earlier examples: It's an example from me not from Kiran. # pcs resource clone groupPing clone-max=3 clone-node-max=1 # pcs resource Clone Set: groupPing-clone [groupPing] The name you should be passing to pcs is groupPing-clone, _not_ g

Re: [Pacemaker] Stopping resource using pcs

2014-03-04 Thread Andrew Beekhof
ver succeeds > if (res.getAttribute("role") == "Started" and not stopped) or > (res.getAttribute("role") == "Stopped" and stopped): > return True > break > if (expire_time < int(time.time())

Re: [Pacemaker] Stopping resource using pcs

2014-03-03 Thread K Mehta
break > if (expire_time < int(time.time())): > break > time.sleep(1) > return False<<< False is returned > > > > > > On Fri, Feb 28, 2014 at 10:49 PM, David Vossel wrote: > >> >> >> >> >> -

Re: [Pacemaker] Stopping resource using pcs

2014-02-28 Thread K Mehta
k if (expire_time < int(time.time())): break time.sleep(1) return False<<< False is returned On Fri, Feb 28, 2014 at 10:49 PM, David Vossel wrote: > > > > > - Original Message - > > From: "K Mehta" >

Re: [Pacemaker] Stopping resource using pcs

2014-02-28 Thread David Vossel
- Original Message - > From: "K Mehta" > To: "The Pacemaker cluster resource manager" > Sent: Friday, February 28, 2014 7:05:47 AM > Subject: Re: [Pacemaker] Stopping resource using pcs > > Can anyone tell me why --wait parameter always c

Re: [Pacemaker] Stopping resource using pcs

2014-02-28 Thread K Mehta
712-c82bb43f19d8:1 ] > > > > > > On Wed, Feb 26, 2014 at 8:55 PM, David Vossel wrote: > >> ----- Original Message - >> > From: "Frank Brendel" >> > To: pacemaker@oss.clusterlabs.org >> > Sent: Wednesday, February 26, 2014 8:53:19

Re: [Pacemaker] Stopping resource using pcs

2014-02-26 Thread K Mehta
sage - > > 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. > > > >

Re: [Pacemaker] Stopping resource using pcs

2014-02-26 Thread David Vossel
- 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

Re: [Pacemaker] Stopping resource using pcs

2014-02-26 Thread Frank Brendel
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] Stopping resource using pcs

2014-02-26 Thread K Mehta
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] Stopping resource using pcs

2014-02-26 Thread K Mehta
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] Stopping resource using pcs

2014-02-26 Thread Frank Brendel
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

2014-02-26 Thread K Mehta
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] Stopping resource using pcs

2014-02-25 Thread Frank Brendel
No erros in syslog? Am 25.02.2014 15:45, schrieb K Mehta: Frank, Creation/Disabling/Deletion of non multi state resource worked fine. When I try to delete a multi state resource, the resource goes into stopped state and the following error is thrown Error: unable to stop: . Regards,

Re: [Pacemaker] Stopping resource using pcs

2014-02-25 Thread K Mehta
Frank, Creation/Disabling/Deletion of non multi state resource worked fine. When I try to delete a multi state resource, the resource goes into stopped state and the following error is thrown Error: unable to stop: . Regards, kiran On Mon, Feb 24, 2014 at 6:03 PM, Frank Brendel wrote: >

Re: [Pacemaker] Stopping resource using pcs

2014-02-24 Thread Frank Brendel
Hi Kiran, the man page says (or use 'pcs resource help') disable [--wait[=n]] Attempt to stop the resource if it is running and forbid the cluster from starting it again. Depending on the rest of the configuration (constraints, options, failures, etc), the resource ma

[Pacemaker] Stopping resource using pcs

2014-02-24 Thread K Mehta
Hi, I am trying to use pcs commands instead of crmsh commands to manage resources. How do I stop a resource using pcs ? I didnt find any pcs resource stop command. Regards, kiran ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clus