[ClusterLabs] Antw: Re: Antw: [EXT] why is node fenced ?

Lentes, Bernd bernd.lentes at helmholtz-muenchen.de
Fri Jul 31 10:55:58 EDT 2020

----- On Jul 31, 2020, at 8:03 AM, Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de wrote:

>>> My guess is that ha-idg-1 was fenced because a failed migration from
>> ha-idg-2
>>> is treated like a stop failure on ha-idg-2. Stop failures cause fencing.
> You
>>> should have tested your resource before going productive.
>> Migration failed at 16:59:34.
>> Node is fenced at 17:05:35. 6 minutes later.
>> The cluster needs 6 minutes to decide to fence the node ?
>> I don't believe that the failed migration is the cause for the fencing.
> What are the values for migration timeout and for stop timeout?

primitive vm_nextcloud VirtualDomain \
        params config="/mnt/share/vm_nextcloud.xml" \
        params hypervisor="qemu:///system" \
        params migration_transport=ssh \
        params migrate_options="--p2p --tunnelled" \
        op start interval=0 timeout=120 \
        op stop interval=0 timeout=180 \  <==================
        op monitor interval=30 timeout=25 \
        op migrate_from interval=0 timeout=300 \ <=================
        op migrate_to interval=0 timeout=300 \ <================
        meta allow-migrate=true target-role=Started is-managed=true maintenance=false \
        utilization cpu=1 hv_memory=4096

3 or 5 minutes, not 6 minutes.

Helmholtz Zentrum München

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, Kerstin Guenther
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671

More information about the Users mailing list