[ClusterLabs] DRBD 2-node M/S doesn't want to promote new master, Centos 8
Brent Jensen
jeneral9 at gmail.com
Sun Jan 17 15:05:54 EST 2021
FYI: I was using ELREPO's packages:
kmod-drbd90.x86_64 9.0.25-2.el8_3.elrepo
drbd90-utils.x86_64 9.13.1-1.el8.elrepo
drbd90-utils-sysvinit.x86_64 9.13.1-1.el8.elrepo
I just tried EPEL's packages (still needed elrepos's kmod) and nothing
seemed to work there (the cluster couldn't seem to load DRBD) even
though it worked manually.
drbd.x86_64 9.13.1-1.el8
drbd-pacemaker.x86_64 9.13.1-1.el8
drbd-udev.x86_64 9.13.1-1.el8
drbd-utils.x86_64 9.13.1-1.el8
kmod-drbd90.x86_64 9.0.25-2.el8_3.elrepo
e.g. output:
pacemaker-execd[1702]: notice: drbd0_stop_0[2992] error output [
/usr/lib/ocf/resource.d/linbit/drbd: line 318: USAGE:: command not found ]
pacemaker-execd[1702]: notice: drbd0_stop_0[2992] error output [
/usr/lib/ocf/resource.d/linbit/drbd: line 320: Commands:: command not
found ]
pacemaker-execd[1702]: notice: drbd0_stop_0[2992] error output [
/usr/lib/ocf/resource.d/linbit/drbd: line 321: primary: command not found ]
pacemaker-execd[1702]: notice: drbd0_stop_0[2992] error output [
/usr/lib/ocf/resource.d/linbit/drbd: line 322: secondary: command not
found ]
pacemaker-execd[1702]: notice: drbd0_stop_0[2992] error output [
/usr/lib/ocf/resource.d/linbit/drbd: line 323: attach: command not found ]
pacemaker-execd[1702]: notice: drbd0_stop_0[2992] error output [
/usr/lib/ocf/resource.d/linbit/drbd: line 324: disk-options: command not
found ]
pacemaker-execd[1702]: notice: drbd0_stop_0[2992] error output [
/usr/lib/ocf/resource.d/linbit/drbd: line 325: detach: command not found ]
pacemaker-execd[1702]: notice: drbd0_stop_0[2992] error output [
/usr/lib/ocf/resource.d/linbit/drbd: eval: line 326: syntax error near
unexpected token `(' ]
Brent
On 1/16/2021 11:07 AM, Strahil Nikolov wrote:
> В 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 one...
>> 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
>> <http://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
> (https://www.linbit.com/drbd-user-guide/drbd-guide-9_0-en/#s-pacemaker-crm-drbd-backed-service
> <https://www.linbit.com/drbd-user-guide/drbd-guide-9_0-en/#s-pacemaker-crm-drbd-backed-service>):
> 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
>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20210117/f48538ca/attachment.htm>
More information about the Users
mailing list