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
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
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
LSB resource coming
up in START mode when such resource is already running on a master?
Thanks
Lax
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Andrew Beekhof andrew@... writes:
One does not imply the other. Stonith is arguably even more important for
2-node clusters.
Ok, will try it out.
One more thing, on another setup with same configuration while running
pacemaker I keep getting 'gfs_controld[10744]: daemon cpg_join
Andrew Beekhof andrew@... writes:
On 10 Oct 2014, at 12:12 pm, Lax lkota@... wrote:
Hi All,
I ran into a time out issue while failing over from master to the peer
server and I have a 2 node setup with 2 resources. Though it was working all
along, this was the first time
/pacemaker/pengine/pe-input-1710.bz2): Stopped
Oct 9 14:57:58 server1 attrd[371]: notice: attrd_perform_update: Sent
update 11: fail-count-resourceB=INFINITY
Thanks
Lax
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org
