[ClusterLabs] Antw: why is node fenced ?

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Tue Aug 13 03:00:17 EDT 2019


>>> "Lentes, Bernd" <bernd.lentes at helmholtz-muenchen.de> schrieb am 12.08.2019
um
18:09 in Nachricht
<546330844.1686419.1565626164456.JavaMail.zimbra at helmholtz-muenchen.de>:
> Hi,
> 
> last Friday (9th of August) i had to install patches on my two-node
cluster.
> I put one of the nodes (ha-idg-2) into standby (crm node standby ha-idg-2),

> patched it, rebooted, 
> started the cluster (systemctl start pacemaker) again, put the node again 
> online, everything fine.

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 of
a difference. Also you don't have to remember to put the node back online in
the configuration.

For your case: After Rebooting the first node, the second one was DC. If you
reboot that, the first node becomes DC, but when booting node 2 it still have
the old config saying it it the DC. So both nodes have to agree on that. Maybe
that's why the cluster is "unclean" for a while. Did it "go away" after some
time?

Regards,
Ulrich

> 
> Then i wanted to do the same procedure with the other node (ha-idg-1).
> I put it in standby, patched it, rebooted, started pacemaker again.
> But then ha-idg-1 fenced ha-idg-2, it said the node is unclean.
> I know that nodes which are unclean need to be shutdown, that's logical.
> 
> But i don't know from where the conclusion comes that the node is unclean 
> respectively why it is unclean,
> i searched in the logs and didn't find any hint.
> 
> I put the syslog and the pacemaker log on a seafile share, i'd be very 
> thankful if you'll have a look.
> https://hmgubox.helmholtz-muenchen.de/d/53a10960932445fb9cfe/ 
> 
> Here the cli history of the commands:
> 
> 17:03:04  crm node standby ha-idg-2
> 17:07:15  zypper up (install Updates on ha-idg-2)
> 17:17:30  systemctl reboot
> 17:25:21  systemctl start pacemaker.service
> 17:25:47  crm node online ha-idg-2
> 17:26:35  crm node standby ha-idg1-
> 17:30:21  zypper up (install Updates on ha-idg-1)
> 17:37:32  systemctl reboot
> 17:43:04  systemctl start pacemaker.service
> 17:44:00  ha-idg-1 is fenced
> 
> Thanks.
> 
> Bernd
> 
> OS is SLES 12 SP4, pacemaker 1.1.19, corosync 2.3.6-9.13.1
> 
> 
> -- 
> 
> Bernd Lentes 
> Systemadministration 
> Institut für Entwicklungsgenetik 
> Gebäude 35.34 - Raum 208 
> HelmholtzZentrum münchen 
> bernd.lentes at helmholtz-muenchen.de 
> phone: +49 89 3187 1241 
> phone: +49 89 3187 3827 
> fax: +49 89 3187 2294 
> http://www.helmholtz-muenchen.de/idg 
> 
> Perfekt ist wer keine Fehler macht 
> Also sind Tote perfekt
>  
> 
> Helmholtz Zentrum Muenchen
> Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
> Ingolstaedter Landstr. 1
> 85764 Neuherberg
> www.helmholtz-muenchen.de 
> 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:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/ 





More information about the Users mailing list