[ClusterLabs] corosync.service (and sbd.service) are not stopper on pacemaker shutdown when corosync-qdevice is used

Roger Zhou ZZhou at suse.com
Fri Aug 9 02:27:05 EDT 2019

On 7/29/19 12:24 AM, Andrei Borzenkov wrote:
> corosync.service sets StopWhenUnneded=yes which normally stops it when
> pacemaker is shut down.

`systemctl stop corosync.service` is the right command to stop those 
cluster stack.

It stops pacemaker and corosync-qdevice first, and stop SBD too.

pacemaker.service: After=corosync.service
corosync-qdevice.service: After=corosync.service
sbd.service: PartOf=corosync.service

On the reverse side, to start the cluster stack, use

systemctl start pacemaker.service corosync-qdevice

It is slightly confusing from the impression. So, openSUSE uses the 
consistent commands as below:

crm cluster start
crm cluster stop


> Unfortunately, corosync-qdevice.service declares
> Requires=corosync.service and corosync-qdevice.service itself is *not*
> stopped when pacemaker.service is stopped. Which means corosync.service
> remains "needed" and is never stopped.
> Also sbd.service (which is PartOf=corosync.service) remains running as well.
> The latter is really bad, as it means sbd watchdog can kick in at any
> time when user believes cluster stack is safely stopped. In particular
> if qnetd is not accessible (think network reconfiguration).
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
> ClusterLabs home: https://www.clusterlabs.org/

More information about the Users mailing list