Réf. : Re: Problem with fenced on cluster with 2 BladeCenter machines: 1st machine is remove physically. The remaining one does not became Active (waiting for fenced)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




From Catalin LUPESCU

Explications for the 1 value of this parameter (clean_start="1")

I have continued the initial test (with the clean_start="0"): the node 2 still not working. I have reboot the node2 (with node 1 still unplug).
After the boot, the node 2 still not became Active.
(fenced is started in loop after the boot)

With the value "1", the fenced is not started at boot because the node 2 is the first (and the only) machine in the cluster. The machine became Active. The fenced is used only after the complete boot of the node 1.
I have done the test with the value "1" and is OK for this part. But the original Pb is still there…

Cordialement,
Catalin LUPESCU
VoIP & Signalling Support

Bull, Architect of an Open World TM
Tél : 01.30.80.75.43
http://www.bull.com
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux