[Group.of.nepali.translators] [Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
** Changed in: corosync (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: corosync (Ubuntu Bionic) Importance: Low => Wishlist -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script Status in corosync package in Ubuntu: Fix Released Status in corosync source package in Trusty: Won't Fix Status in corosync source package in Xenial: Won't Fix Status in corosync source package in Bionic: Won't Fix Status in corosync source package in Disco: Won't Fix Status in corosync source package in Eoan: Won't Fix Status in corosync source package in Focal: Fix Released Bug description: [SRU] [Impact] Users that use the sysv services provided by corosync-notifyd and corosync packages may find a corosync-notifyd service's misfunction because it uses the pid file created by corosync service. [Test Plan] In a new VM with bionic (specifically for this testing): #Disabling systemd (this will lead you to a non-usable system at the end for other things, but this is only for testing purposes of this bug -systemctl disable didn't work-): sudo apt remove --purge systemd #Install corosync and corosync-notifyd: sudo apt install corosync corosync-notifyd #check versions (optional): ubuntu@bionic-corosync-sysv:~/Builds$ dpkg -l | grep coro ii corosync 2.4.3-0ubuntu1.2 amd64cluster engine daemon and utilities ii corosync-notifyd 2.4.3-0ubuntu1.2 amd64cluster engine notification daemon ii libcorosync-common4:amd642.4.3-0ubuntu1.2 amd64cluster engine common library #Start notifyd service: ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd start * Starting corosync notifying daemon corosync-notifyd [ OK ] #Check that pid filename is not correct: ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro* /var/run/corosync.pid #stop de service, check pid file is gone and install new version: ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd stop * Stopping corosync notifying daemon corosync-notifyd [ OK ] ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro* ls: cannot access '/var/run/coro*': No such file or directory ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo dpkg -i /home/ubuntu/Builds/corosync-notifyd_2.4.3-0ubuntu1.3_amd64.deb (Reading database ... 59514 files and directories currently installed.) Preparing to unpack .../corosync-notifyd_2.4.3-0ubuntu1.3_amd64.deb ... Unpacking corosync-notifyd (2.4.3-0ubuntu1.3) over (2.4.3-0ubuntu1.2) ... /var/lib/dpkg/info/corosync-notifyd.postrm: 12: /var/lib/dpkg/info/corosync-notifyd.postrm: systemctl: not found Setting up corosync-notifyd (2.4.3-0ubuntu1.3) ... Installing new version of config file /etc/init.d/corosync-notifyd ... Can't exec "systemctl": No such file or directory at /usr/sbin/update-rc.d line 93. /usr/sbin/invoke-rc.d: 282: /usr/sbin/invoke-rc.d: systemctl: not found invoke-rc.d: could not determine current runlevel invoke-rc.d: WARNING: No init system and policy-rc.d missing! Defaulting to block. Processing triggers for dbus (1.12.2-1ubuntu1.2) ... Processing triggers for ureadahead (0.100.0-21) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... #Start notifyd service ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd start * Starting corosync notifying daemon corosync-notifyd [ OK ] #Check pid-filename is now the same as daemon's name (corosync-notifyd): ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro* /var/run/corosync-notifyd.pid [Where problems could occur] The fix is cherrypicked from the Focal's solution, only affects corosync-notifyd and corosync services. No other services depend on this pid files. No systemd services affected. [Other Info] This solution follows the example of the same bug fixed in Focal at https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622 , alongside bug https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 (in progress to be SRU processed also for Bionic). Although the number of users affected by this is a minority, I decided to fix this in concordance with that this issue is fixed in Focal and it's a copy/paste error easy to understand and without impact in any other application or system. -- [Original Description] A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE: > PIDFILE=/var/run/$NAME.pid >
[Group.of.nepali.translators] [Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
Xenial is now in Extended Security Maintenance (ESM) and this bug doesn't qualify for it, so this bug will not be fixed for that release. ** Changed in: corosync (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script Status in corosync package in Ubuntu: Fix Released Status in corosync source package in Trusty: Won't Fix Status in corosync source package in Xenial: Won't Fix Status in corosync source package in Bionic: In Progress Status in corosync source package in Disco: Won't Fix Status in corosync source package in Eoan: Won't Fix Status in corosync source package in Focal: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: corosync (Ubuntu Eoan) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script Status in corosync package in Ubuntu: Fix Released Status in corosync source package in Trusty: Won't Fix Status in corosync source package in Xenial: Triaged Status in corosync source package in Bionic: Triaged Status in corosync source package in Disco: Won't Fix Status in corosync source package in Eoan: Won't Fix Status in corosync source package in Focal: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
This bug was fixed in the package corosync - 3.0.3-2ubuntu2 --- corosync (3.0.3-2ubuntu2) focal; urgency=medium [Jorge Niedbalski] * d/control: corosync binary depends on libqb-dev (LP: #1677684) [Rafael David Tinoco] * debian/corosync-notifyd.init: fix for 2 PIDFILEs declared (LP: #1437359) * Post v3.0.3 release fixes backported to Ubuntu (LP: #1869622) debian/patches/ubuntu-v3.0.3-fixes/: - lp1869622-09f6d34a-logconfig-Remove-double-free-of-value.patch - lp1869622-0c118d8f-totemknet-Check-result-of-fcntl-O_NONBLOCK-call.patch - lp1869622-0c16442f-votequorum-Change-check-of-expected_votes.patch - lp1869622-1fb095b0-notifyd-Check-cmap_track_add-result.patch - lp1869622-29109683-totemknet-Assert-strcpy-length.patch - lp1869622-35c312f8-votequorum-Assert-copied-strings-length.patch - lp1869622-380b744e-totemknet-Don-t-mix-corosync-and-knet-error-codes.patch - lp1869622-56ee8503-quorumtool-Assert-copied-string-length.patch - lp1869622-5f543465-quorumtool-exit-on-invalid-expected-votes.patch - lp1869622-624b6a47-stats-Assert-value_len-when-value-is-needed.patch - lp1869622-74eed54a-sync-Assert-sync_callbacks.name-length.patch - lp1869622-89b0d62f-stats-Check-return-code-of-stats_map_get.patch - lp1869622-8ce65bf9-votequorum-Reflect-runtime-change-of-2Node-to-WFA.patch - lp1869622-8ff7760c-cmapctl-Free-bin_value-on-error.patch - lp1869622-a24cbad5-totemconfig-Initialize-warnings-variable.patch - lp1869622-c631951e-icmap-icmap_init_r-leaks-if-trie_create-fails.patch - lp1869622-ca320bea-votequorum-set-wfa-status-only-on-startup.patch - lp1869622-efe48120-totemconfig-Free-leaks-found-by-coverity.patch -- Rafael David Tinoco Sun, 29 Mar 2020 21:50:35 + ** Changed in: corosync (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script Status in corosync package in Ubuntu: Fix Released Status in corosync source package in Trusty: Won't Fix Status in corosync source package in Xenial: Triaged Status in corosync source package in Bionic: Triaged Status in corosync source package in Disco: Won't Fix Status in corosync source package in Eoan: Triaged Status in corosync source package in Focal: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
** Also affects: corosync (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Focal) Importance: Undecided Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Triaged ** Also affects: corosync (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: corosync (Ubuntu Focal) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: corosync (Ubuntu Disco) Status: New => Won't Fix ** Changed in: corosync (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: corosync (Ubuntu Eoan) Status: New => Triaged ** Changed in: corosync (Ubuntu Xenial) Status: New => Triaged ** Changed in: corosync (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script Status in corosync package in Ubuntu: In Progress Status in corosync source package in Trusty: Won't Fix Status in corosync source package in Xenial: Triaged Status in corosync source package in Bionic: Triaged Status in corosync source package in Disco: Won't Fix Status in corosync source package in Eoan: Triaged Status in corosync source package in Focal: In Progress Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
