[ClusterLabs] Q: Is there any plan for pcs to support corosync-notifyd?

[井上和徳]

On Tue, Mar 16, 2021 at 10:23 PM Jehan-Guillaume de Rorthais
<jgdr at dalibo.com> wrote:
>
> > On Tue, 16 Mar 2021, 09:58 井上和徳, <kazunori_inoue at newson.co.jp> wrote:
> >
> > > Hi!
> > >
> > > Cluster (corosync and pacemaker) can be started with pcs,
> > > but corosync-notifyd needs to be started separately with systemctl,
> > > which is not easy to use.
>
> Maybe you can add to the [Install] section of corosync-notifyd a dependency
> with corosync? Eg.:
>
>   WantedBy=corosync.service
>
> (use systemctl edit corosync-notifyd)
>
> Then re-enable the service (without starting it by hands).

I appreciate your proposal. How to use WantedBy was helpful!
However, since I want to start the cluster (corosync, pacemaker) only manually,
it is unacceptable to start corosync along with corosync-notifyd at OS
boot time.

Disabling the dependency (Requires=corosync.service) on corosync-notifyd.service
will prevent corosync from starting at OS boot, but will cause corosync-notifyd
to fail, which may confuse users.
# sytemctl reboot
 :
# grep "notifyd.*error" /var/log/messages
Mar 18 12:09:54 rhel83-1 <daemon.err> notifyd[949]:[error] Failed to
initialize the cmap API. Error 2
Mar 18 12:09:54 rhel83-1 <daemon.err> notifyd[978]:[error] Failed to
initialize the cmap API. Error 2
Mar 18 12:09:55 rhel83-1 <daemon.err> notifyd[1014]:[error] Failed to
initialize the cmap API. Error 2
Mar 18 12:09:55 rhel83-1 <daemon.err> notifyd[1021]:[error] Failed to
initialize the cmap API. Error 2
Mar 18 12:09:55 rhel83-1 <daemon.err> notifyd[1025]:[error] Failed to
initialize the cmap API. Error 2

Regards,
Kazunori INOUE