[ClusterLabs] DRBD 2-node M/S doesn't want to promote new master, Centos 8

Strahil Nikolov hunter86_bg at yahoo.com
Sat Jan 16 13:07:00 EST 2021

В 14:10 -0700 на 15.01.2021 (пт), Brent Jensen написа:
>       Problem: When performing "pcs node standby" on the
>         current master, this node demotes fine but the slave doesn't
>         promote to master. It keeps  looping the same error including
>         "Refusing to be Primary while peer is  not outdated" and
> "Could
>         not connect to the CIB." At this point the old  master has
>         already unloaded drbd. The only way to fix it is to start
>  drbd
>         on the standby node (e.g. drbdadm r0 up). Logs contained
> herein
>         are  from the node trying to be master.
In order to debug, stop the cluster and verify that drbd is running
properly. Promote one of the nodes, then demote and promote another
>         I have done this on DRBD9/Centos7/Pacemaker1 w/o any
> problems.
>         So I don't know were the issue is (crm-fence-peer.9.sh
>       Another odd data point: On the slave if I do a "pcs
>         node standby" & then unstandby, DRBD is loaded again;
>         HOWEVER, when I do this on the master (which should then be
>         slave), DRBD doesn't get loaded.
>         Stonith/Fencing doesn't seem to make a difference. Not sure
> if
>         auto-promote is required.
Quote from official documentation (
If you are employing the DRBD OCF resource agent, it is recommended
that you defer DRBD startup, shutdown, promotion, and
demotion exclusively to the OCF resource agent. That means that you
should disable the DRBD init script:

So remove the autopromote and disable the drbd service at all.

Best Regards,
Strahil Nikolov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20210116/15694a13/attachment.htm>

More information about the Users mailing list