[Pacemaker] resource file

Hi Written my own resource script file In the monitor command, what error code should I return to say the resource has failed, but to no make it permanent Currently I am using return $OCF_ERR_PERM but it means that ones the resource is unavailable it is permanently unavailable This is not m

Re: [Pacemaker] resource file

Hi, On Mon, Jun 03, 2013 at 08:39:23AM +, Alex Samad - Yieldbroker wrote: > Hi > > Written my own resource script file > > In the monitor command, what error code should I return to say the resource > has failed, but to no make it permanent OCF_ERR_GENERIC There's also the OCF resource a

[Pacemaker] resource running on both nodes

Hi All, Can someone please help me in my below setup?? I have 2 node setup with HB+pacemaker. I have my app running on both the nodes before the start of HB and pacemaker. Later I configured the crm as below: # crm configure primitive havip ocf:IPaddr2 params ip=192.168.101.205 cidr_netmask=32

Re: [Pacemaker] resource running on both nodes

On 2013-06-03T18:22:39, ESWAR RAO wrote: > Hi All, > > Can someone please help me in my below setup?? > > I have 2 node setup with HB+pacemaker. > I have my app running on both the nodes before the start of HB and > pacemaker. > > Later I configured the crm as below: > > # crm configure primi

[Pacemaker] What is the pcs equivalent of crm configure show?

Dear list, May I know what is the pcs equivalent of crm configure show? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/l

Re: [Pacemaker] What is the pcs equivalent of crm configure show?

On 06/03/13 10:18, Teo En Ming (Zhang Enming) wrote: Dear list, May I know what is the pcs equivalent of crm configure show? Thank you very much. This command will give you the full configuration and status of pacemaker in xml format: pcs cluster cib If you want a more user friendly forma

Re: [Pacemaker] resource running on both nodes

> -Original Message- > From: Lars Marowsky-Bree [mailto:l...@suse.com] > Sent: Monday, 3 June 2013 11:25 PM > To: The Pacemaker cluster resource manager > Subject: Re: [Pacemaker] resource running on both nodes > > On 2013-06-03T18:22:39, ESWAR RAO wrote: > > > Hi All, > > > > Can someon

Re: [Pacemaker] resource running on both nodes

Hi Lars, Thanks for the response. Should I configure the resource as below? # crm configure primitive oc_proxyapp lsb::proxyapp meta allow-migrate="true" migration-threshold="3" failure-timeout="30s" op monitor interval="5s" # crm oc_proxyapp_clone oc_proxyapp I couldn't find anywhere about on

Re: [Pacemaker] Pacemaker still may include memory leaks

On 03/06/2013, at 8:55 PM, Yuichi SEINO wrote: > Hi, > > I run the test after we updated pacemaker. > > I tested the same way as the previous test. However, I think that the > memory leak still may be caused. > > I attached the result(smaps and crm_mon and env). And, I also make the > chart o

Re: [Pacemaker] Pacemaker still may include memory leaks

On 6/3/2013 8:30 PM, Andrew Beekhof wrote: On 03/06/2013, at 8:55 PM, Yuichi SEINO wrote: Hi, I run the test after we updated pacemaker. I tested the same way as the previous test. However, I think that the memory leak still may be caused. I attached the result(smaps and crm_mon and env). A

[Pacemaker] more newbie questions

Hi One this page http://www.sebastien-han.fr/blog/2012/09/16/pacemaker-load-balancing-with-clone/ There is this === sudo crm configure primitive p_vip ocf:heartbeat:IPaddr2 \ params ip="172.17.1.100" cidr_netmask="24" nic="eth0" clusterip_hash="sourceip-sourceport" \

[Pacemaker] [Problem] The state of a node cut with the node that rebooted by a cluster is not recognized.

Hi All, We confirmed a state of the recognition of the cluster in the next procedure. We confirm it by the next combination.(RHEL6.4 guest) * corosync-2.3.0 * pacemaker-Pacemaker-1.1.10-rc3 - Step 1) Start all nodes and constitute a cluster. [root@rh64-coro1 ~]# crm_mo

Re: [Pacemaker] [Problem] The state of a node cut with the node that rebooted by a cluster is not recognized.

Hi All, I registered this problem with Bugzilla. * http://bugs.clusterlabs.org/show_bug.cgi?id=5160 Best Regards, Hideo Yamauchi. --- On Tue, 2013/6/4, renayama19661...@ybb.ne.jp wrote: > Hi All, > > We confirmed a state of the recognition of the cluster in the next procedure. > We confirm