[ClusterLabs] shutdown and restart of complete cluster due to power outage with UPS
bernd.lentes at helmholtz-muenchen.de
Wed Jan 23 07:53:21 EST 2019
----- On Jan 22, 2019, at 6:00 PM, kgaillot kgaillot at redhat.com wrote:
> On Tue, 2019-01-22 at 16:52 +0100, Lentes, Bernd wrote:
>> Now the restart, which makes me trouble.
>> Currently i want to restart the cluster manually, because i'm not
>> completly familiar with pacemaker and a bit afraid of getting
>> due to automotization i didn't think of before.
>> I can do that from anywhere because both nodes have ILO-cards.
>> I start e.g. node1 with power button.
>> systemctl start corosync
>> systemctl start pacemaker
>> corosync and pacemaker don't start automatically, i read that
>> several times as a recommendation.
>> Now my first problem. Let's assume the other node is broken. But i
>> still want to get
>> resources running. My no-quorum-policy is ignore. That should be
>> fine. But i have this setup now and don't get the resources running
> I'm guessing you have corosync 2's wait_for_all set (probably
> implicitly by two_node). This is a safeguard for the situation where
> both nodes are booted up but can't see each other.
> If you're sure the other node is down, you can disable wait_for_all
> before starting the node. (I'm not sure if this can be changed while
> corosync is already running.)
I have corosync-2.3.6-9.13.1.x86_64.
Where can i configure this value ?
Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
Aufsichtsratsvorsitzende: MinDirig'in Petra Steiner-Hoffmann
Stellv.Aufsichtsratsvorsitzender: MinDirig. Dr. Manfred Wolter
Geschaeftsfuehrer: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Heinrich Bassler
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671
More information about the Users