- To: linux-cluster@xxxxxxxxxx
- Subject: Re: Fencing: Prevent rebooting halted node
- From: Nicolas Ecarnot <nicolas@xxxxxxxxxxx>
- Date: Wed, 21 Mar 2012 13:17:08 +0100
- In-reply-to: <CAE7pJ3Cr-AKMNSKuE5yM8SXw2RFP4fCkd-FjM=pwhZ1g2G-RwQ@mail.gmail.com>
- Organization: Si peu...
- References: <4F69B0CE.7020809@ecarnot.net> <CAE7pJ3Cr-AKMNSKuE5yM8SXw2RFP4fCkd-FjM=pwhZ1g2G-RwQ@mail.gmail.com>
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.28) Gecko/20120306 Lightning/1.0b2 Thunderbird/3.1.20
Le 21/03/2012 12:23, emmanuel segura a écrit :
Hello Nicolas
Hello Emmanuel,
The first i can recommend it's use a quorum disk
I do use a quorum disk. I did not mention it as I thought this had
nothing to do with my issue.
and for your problem i
know that it's called fencing-loop
Ok, I'll search on that subject.
you got two choices
1:don't put the daemons cluster at boot time
In fact, I do want the cluster daemons to be ran at boot time. This is a
good behaviour.
I just want dead nodes to remain dead, until manual intervention.
2:If you use a qdisk you can use clean_start="1" in the fence_daemon
tag, this can be used if you are not using gfs or gfs2 or
<cmantwo_node="1"expected_votes="1"/>
I am using gfs2...
To cope with my problem, I was looking whether it was possible to call
my own script in cluster.conf? I don't know if this is permitted and
what return code is expected?
--
Nicolas Ecarnot
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
[Corosync Cluster Engine]
[Linux RAID]
[Fedora Users]
[Fedora Legacy List]
[Fedora Desktop]
[Fedora SELinux]
[Big List of Linux Books]
[Yosemite News]
[Yosemite Photos]
[KDE Users]