Re: [Pacemaker] Pacemaker restart bringing up resource in start mode even other node is running the resource
Andrew Beekhof andrew@... writes: So on pacemaker restart, is there any way I can stop my LSB resource coming up in START mode when such resource is already running on a master? Tell init/systemd not to start it when the node boots Thanks for the response Andrew. But even if I do not reboot the node and simply do pacemaker service stop and start too I run into this issue. 'it' referred to the LSB resource, not pacemaker/corosync Thanks for your help as always Andrew. Is there any sample that you can point me to how to configure it for the resource. Thanks Lax ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker restart bringing up resource in start mode even other node is running the resource
On 29 Oct 2014, at 7:42 am, Lax lk...@cisco.com wrote:
Andrew Beekhof andrew@... writes:
So on pacemaker restart, is there any way I can stop my LSB resource
coming
up in START mode when such resource is already running on a master?
Tell init/systemd not to start it when the node boots
Thanks for the response Andrew.
But even if I do not reboot the node and simply do pacemaker service stop
and start too I run into this issue.
'it' referred to the LSB resource, not pacemaker/corosync
Thanks for your help as always Andrew. Is there any sample that you can
point me to how to configure it for the resource.
I mean something like:
chkconfig {LSB-name} off
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker restart bringing up resource in start mode even other node is running the resource
Andrew Beekhof andrew@... writes:
Thanks for your help as always Andrew. Is there any sample that you can
point me to how to configure it for the resource.
I mean something like:
chkconfig {LSB-name} off
I tried setting it this way and still resource gets started on both the
nodes on pacemaker start. Here is the sequence I followed
1. Stop pacemaker service on both the peers Node1 and Node2
2. Issue 'chkconfig my-LSB-name off' on Node1 and Node2
3. Start pacemaker service first on Node1, wait till it fully comes up
- say 'crm_mon -1' to ensure Node1 is online and Node2 is Offline
4. Now Start pacemaker service on Node2
- while it is happening I run 'crm_mon' on Node1 to see the resource
state transition. Here I still see my-lsb-resource being started on Node1
and Node2 - Stopped - started back on Node1
Thanks
Lax
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker restart bringing up resource in start mode even other node is running the resource
On 29 Oct 2014, at 9:30 am, Lax lk...@cisco.com wrote:
Andrew Beekhof andrew@... writes:
Thanks for your help as always Andrew. Is there any sample that you can
point me to how to configure it for the resource.
I mean something like:
chkconfig {LSB-name} off
I tried setting it this way and still resource gets started on both the
nodes on pacemaker start. Here is the sequence I followed
1. Stop pacemaker service on both the peers Node1 and Node2
2. Issue 'chkconfig my-LSB-name off' on Node1 and Node2
3. Start pacemaker service first on Node1, wait till it fully comes up
- say 'crm_mon -1' to ensure Node1 is online and Node2 is Offline
4. Now Start pacemaker service on Node2
- while it is happening I run 'crm_mon' on Node1 to see the resource
state transition. Here I still see my-lsb-resource being started on Node1
and Node2 - Stopped - started back on Node1
crm_report please?
Thanks
Lax
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker restart bringing up resource in start mode even other node is running the resource
On 25 Oct 2014, at 9:08 am, Lax lk...@cisco.com wrote: Andrew Beekhof andrew@... writes: So on pacemaker restart, is there any way I can stop my LSB resource coming up in START mode when such resource is already running on a master? Tell init/systemd not to start it when the node boots Thanks for the response Andrew. But even if I do not reboot the node and simply do pacemaker service stop and start too I run into this issue. 'it' referred to the LSB resource, not pacemaker/corosync Thanks Lax ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker restart bringing up resource in start mode even other node is running the resource
Andrew Beekhof andrew@... writes: So on pacemaker restart, is there any way I can stop my LSB resource coming up in START mode when such resource is already running on a master? Tell init/systemd not to start it when the node boots Thanks for the response Andrew. But even if I do not reboot the node and simply do pacemaker service stop and start too I run into this issue. Thanks Lax ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker restart bringing up resource in start mode even other node is running the resource
On 18 Oct 2014, at 7:52 am, Lax lk...@cisco.com wrote: Hi, I have 2 node setup with 2 resources with one resource being OCF and one is an LSB resource. Every time I restart pacemaker on my standby(peer) server, my LSB resource default comes up in START mode though the resource is already running in master(other) server. Sequence it is happening is Peer server starts pacemaker Pacemaker directly brings up my LSB resource Start mode Then it sees my master is already running it Stops the resource on both master peer servers Goes back to starting the resource on original master server So on pacemaker restart, is there any way I can stop my LSB resource coming up in START mode when such resource is already running on a master? Tell init/systemd not to start it when the node boots ;-) Thanks Lax ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
