[ClusterLabs] Antw: Re: Antw: why is node fenced ?
Ulrich.Windl at rz.uni-regensburg.de
Tue Aug 13 05:20:10 EDT 2019
>>> "Lentes, Bernd" <bernd.lentes at helmholtz-muenchen.de> schrieb am 13.08.2019
10:54 in Nachricht
<848962511.1856599.1565686469666.JavaMail.zimbra at helmholtz-muenchen.de>:
> ‑‑‑‑‑ On Aug 13, 2019, at 9:00 AM, Ulrich Windl
Ulrich.Windl at rz.uni‑regensburg.de
>> Personally I feel more save with updates when the whole cluster node is
>> offline, not standby. When you are going to boot anyway, it won't make much
>> a difference. Also you don't have to remember to put the node back online
>> the configuration.
>> For your case: After Rebooting the first node, the second one was DC. If
>> reboot that, the first node becomes DC, but when booting node 2 it still
>> the old config saying it it the DC. So both nodes have to agree on that.
>> that's why the cluster is "unclean" for a while. Did it "go away" after
> For debugging, e.g. after fencing: is there something in the logs form
> i recognize which one was DC and which not ? E.g. some differences in the
> pacemaker.log ?
In SLES12 it's in /var/log/pacemaker.log: Look for strings like "Set DC to "
and "Unset DC. Was ", or "I_ELECTION_DC" and "I_NOT_DC".
> What is about changes of the CIB and the following actions ? If after a diff
> in the CIB pengine is doing s.th.,
> this must be the DC i guess.
> Helmholtz Zentrum Muenchen
> Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
> Ingolstaedter Landstr. 1
> 85764 Neuherberg
> Aufsichtsratsvorsitzende: MinDir'in Prof. Dr. Veronika von Messling
> Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Heinrich
> Bassler, Kerstin Guenther
> Registergericht: Amtsgericht Muenchen HRB 6466
> USt‑IdNr: DE 129521671
> Manage your subscription:
> ClusterLabs home: https://www.clusterlabs.org/
More information about the Users