Hello
I remove 2 nodes from cluster, with follow sequence:
crm_node --force -R
crm_node --force -R
cibadmin --delete --obj_type nodes --crm_xml ''
cibadmin --delete --obj_type status --crm_xml ''
cibadmin --delete --obj_type nodes --crm_xml ''
cibadmin --delete --obj_type status --crm_xml ''
Have you got any apache vhosts listening on 127.0.0.1? Try creating a
seperate vhost, listening only to the loopback interface on port 80.
On 11 April 2012 12:33, Hugo Deprez wrote:
> Hello,
>
> any idea ?
>
> Regards,
>
> On 10 April 2012 10:34, Hugo Deprez wrote:
>>
>> Dear community,
>>
>> I
On Saturday 14 April 2012 13:24:29 S, MOHAMED ** CTR ** wrote:
> The Pacemaker_Explained.pdf document says that
> " setting of migration-threshold=2 and failure-timeout=60s would cause the
> resource to move to a new node after 2 failures, and allow it to move back
> (depending on the stickiness an
Hi,
The Pacemaker_Explained.pdf document says that
" setting of migration-threshold=2 and failure-timeout=60s would cause the
resource to move to a new node after 2 failures, and allow it to move back
(depending on the stickiness and constraint scores) after one minute."
Can you please help me
Digimer,
Thanks for your advise.
Regards,
Raffi
> -Original Message-
> From: Digimer [mailto:li...@alteeve.ca]
> Sent: Friday, April 13, 2012 5:32 PM
> To: The Pacemaker cluster resource manager
> Cc: S, MOHAMED (MOHAMED)** CTR **
> Subject: Re: [Pacemaker] Corosync vs Heartbeat
>
> On
Michael,
Thanks for the info.
Regards,
Raffi
> -Original Message-
> From: Michael Schwartzkopff [mailto:mi...@clusterbau.com]
> Sent: Friday, April 13, 2012 5:21 PM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Corosync vs Heartbeat
>
> > Hi,
> >
> > Which comb
