If anyone faces this issue, just remove the second PIDFILE as it appears to be a leftover. I'll fix this and point this out to Debian as it also faces the same issue. NEVERTHELESS, remember that this issue would only exist if you are using the "sysv" scripts OR the sysv-generator (making systemd to control the service through sysv scripts).
All others are probably relying in systemd to start/stop/monitor corosync daemon (/lib/systemd/system/corosync.service).
(c)rafaeldtinoc o@clusterdev: ~/.../sources/ ubuntu/ corosync$ git diff HEAD corosync- notifyd. init b/debian/ corosync- notifyd. init corosync- notifyd. init corosync- notifyd. init notifyd /usr/sbin/ $NAME /var/run/ $NAME.pid /etc/init. d/$NAME /var/run/ corosync. pid /var/run/ resource- agents
diff --git a/debian/
index c908618..837e48a 100644
--- a/debian/
+++ b/debian/
@@ -21,7 +21,6 @@ NAME=corosync-
DAEMON=
PIDFILE=
SCRIPTNAME=
-PIDFILE=
RARUNDIR=
# Exit if the package is not installed
If anyone faces this issue, just remove the second PIDFILE as it appears to be a leftover. I'll fix this and point this out to Debian as it also faces the same issue. NEVERTHELESS, remember that this issue would only exist if you are using the "sysv" scripts OR the sysv-generator (making systemd to control the service through sysv scripts).
All others are probably relying in systemd to start/stop/monitor corosync daemon (/lib/systemd/ system/ corosync. service) .