Correct me if I'm wrong but I strongly think the following would work:
Since you want to _start_ pacemaker in unmanaged mode, I expect all your
nodes to be offline. Then delete cib.xml on all nodes but one.
On the one remaining, edit cib.xml and put your configuration
is_managed=false there.
Hi Dominik,
I just have tried again :
service corosync stop on both nodes node1 node2
remove the cib.xml on node2
vi cib.xml on node1
set the property maintenance-mode=true
(nvpair id=cib-bootstrap-options-maintenance-mode
name=maintenance-mode value=true/)
wq!
start Pacemaker on node1
On 05/11/2011 10:24 AM, Alain.Moulle wrote:
Hi Dominik,
I just have tried again :
service corosync stop on both nodes node1 node2
remove the cib.xml on node2
vi cib.xml on node1
set the property maintenance-mode=true
(nvpair id=cib-bootstrap-options-maintenance-mode
On 5/11/2011 at 06:49 PM, Dominik Klein d...@in-telegence.net wrote:
On 05/11/2011 10:24 AM, Alain.Moulle wrote:
Hi Dominik,
I just have tried again :
service corosync stop on both nodes node1 node2
remove the cib.xml on node2
vi cib.xml on node1
set the property
Hi
I wonder if there is a way to start Pacemaker but directly in the mode
is_managed=true,
so that at the start , none action on any resource configured in
Pacemaker will be executed (start, stop, monitoring etc.)
This would useful in the case we have a big problem which makes all
resources
Sorry I meant directly with is_managed=false of course !
Alain
Hi
I wonder if there is a way to start Pacemaker but directly in the mode
is_managed=true,
so that at the start , none action on any resource configured in
Pacemaker will be executed (start, stop, monitoring etc.)
This would
Just write it to the xml on all nodes?
On 05/10/2011 01:23 PM, Alain.Moulle wrote:
Sorry I meant directly with is_managed=false of course !
Alain
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
I don't think it is authorized at all, we must never write directly
in cib.xml , I tried for other needs and it systematically disturbs
Pacemaker a lot !
We always have to go through some crm commands or similar
(crm_attributes, etc.)
but they are not taken in account before the 60s are ended.
