[Bug 1445616] Re: crmsh in vivid/wily/xenial is not compatible with pacemaker
AFAICT, for the current xenial, the pacemaker is 1.1.14 and crmsh v2.1.4 is "old" again. Works for me with https://launchpad.net/ubuntu/+source/crmsh/2.2.0-1/+build/8964914/+files/crmsh_2.2.0-1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1445616 Title: crmsh in vivid/wily/xenial is not compatible with pacemaker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1445616/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1437359] [NEW] A PIDFILE is double-defined for the corosync-notifyd init script
Public bug reported: A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE: PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME PIDFILE=/var/run/corosync.pid The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead The corosync package version is 2.3.3-1ubuntu1 ** Affects: corosync (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ** Description changed: A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE: PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME PIDFILE=/var/run/corosync.pid The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead + + The corosync package version is 2.3.3-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1437368] [NEW] A DAEMON_ARGS=-d is missing for the corosync-notifyd init script
Public bug reported: Without a -d option, corosync-notifyd refuses to start with the command start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd -- But it starts OK with start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd -- -d According to the man pages, the -d option should be used in order to make the corosync-notifyd to send DBUS signals on all events, so it looks like is *should* present as well The corosync package version is 2.3.3-1ubuntu1 ** Affects: corosync (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ** Tags added: trusty ** Description changed: Without a -d option, corosync-notifyd refuses to start with the command start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd -- But it starts OK with start-stop-daemon --verbose --start --exec /usr/sbin/corosync-notifyd -- -d According to the man pages, the -d option should be used in order to make the corosync-notifyd to send DBUS signals on all events, so it looks like is *should* present as well + + The corosync package version is 2.3.3-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1437368 Title: A DAEMON_ARGS=-d is missing for the corosync-notifyd init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437368/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
