[Ubuntu-ha] [Bug 1869622] [NEW] [focal] corosync v3.0.3 last upstream fixes
Public bug reported: Apart from fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = coverity fix -> ca320bea votequorum: set wfa status only on startup = fix for corner case -> 5f543465 quorumtool: exit on invalid expected votes = fix -> 0c16442f votequorum: Change check of expected_votes = fix -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix -> 89b0d62f stats: Check return code of stats_map_get = fix -> 56ee8503 quorumtool: Assert copied string length = assert (better support) -> 1fb095b0 notifyd: Check cmap_track_add result = assert (better support) -> 8ff7760c cmapctl: Free bin_value on error (fix) -> 35c312f8 votequorum: Assert copied strings length = assert (better support) -> 29109683 totemknet: Assert strcpy length assert (better support) -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call -> a24cbad5 totemconfig: Initialize warnings variable = build fix -> 74eed54a sync: Assert sync_callbacks.name length = assert (better support) -> 380b744e totemknet: Don't mix corosync and knet error codes = fix -> 624b6a47 stats: Assert value_len when value is needed = assert (bet support) -> 09f6d34a logconfig: Remove double free of value = fix -> efe48120 totemconfig: Free leaks found by coverity = fix ** Affects: corosync (Ubuntu) Importance: High Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Changed in: corosync (Ubuntu) Status: New => Confirmed ** Changed in: corosync (Ubuntu) Importance: Undecided => High ** Changed in: corosync (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes Status in corosync package in Ubuntu: Confirmed Bug description: Apart from fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = coverity fix -> ca320bea votequorum: set wfa status only on startup = fix for corner case -> 5f543465 quorumtool: exit on invalid expected votes = fix -> 0c16442f votequorum: Change check of expected_votes = fix -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix -> 89b0d62f stats: Check return code of stats_map_get = fix -> 56ee8503 quorumtool: Assert copied string length = assert (better support) -> 1fb095b0 notifyd: Check cmap_track_add result = assert (better support) -> 8ff7760c cmapctl: Free bin_value on error (fix) -> 35c312f8 votequorum: Assert copied strings length = assert (better support) -> 29109683 totemknet: Assert strcpy length assert (better support) -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call -> a24cbad5 totemconfig: Initialize warnings variable = build fix -> 74eed54a sync: Assert sync_callbacks.name length = assert (better support) -> 380b744e totemknet: Don't mix corosync and knet error codes = fix -> 624b6a47 stats: Assert value_len when value is needed = assert (bet support) -> 09f6d34a logconfig: Remove double free of value = fix -> efe48120 totemconfig: Free leaks found by coverity = fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1869622] Re: [focal] corosync v3.0.3 last upstream fixes
** Description changed: Together with fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: - -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = coverity fix - -> ca320bea votequorum: set wfa status only on startup = fix for corner case - -> 5f543465 quorumtool: exit on invalid expected votes = fix - -> 0c16442f votequorum: Change check of expected_votes = fix - -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix - -> 89b0d62f stats: Check return code of stats_map_get = fix - -> 56ee8503 quorumtool: Assert copied string length = assert (better support) - -> 1fb095b0 notifyd: Check cmap_track_add result = assert (better support) - -> 8ff7760c cmapctl: Free bin_value on error (fix) - -> 35c312f8 votequorum: Assert copied strings length = assert (better support) - -> 29109683 totemknet: Assert strcpy length assert (better support) - -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call - -> a24cbad5 totemconfig: Initialize warnings variable = build fix - -> 74eed54a sync: Assert sync_callbacks.name length = assert (better support) - -> 380b744e totemknet: Don't mix corosync and knet error codes = fix - -> 624b6a47 stats: Assert value_len when value is needed = assert (bet support) - -> 09f6d34a logconfig: Remove double free of value = fix - -> efe48120 totemconfig: Free leaks found by coverity = fix + -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = fix + -> ca320bea votequorum: set wfa status only on startup = fix + -> 5f543465 quorumtool: exit on invalid expected votes = fix + -> 0c16442f votequorum: Change check of expected_votes = fix + -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix + -> 89b0d62f stats: Check return code of stats_map_get = fix + -> 56ee8503 quorumtool: Assert copied string length= assert + -> 1fb095b0 notifyd: Check cmap_track_add result = assert + -> 8ff7760c cmapctl: Free bin_value on error = fix + -> 35c312f8 votequorum: Assert copied strings length = assert + -> 29109683 totemknet: Assert strcpy length assert = assert + -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call = assert + -> a24cbad5 totemconfig: Initialize warnings variable = build fix + -> 74eed54a sync: Assert sync_callbacks.name length= assert + -> 380b744e totemknet: Don't mix corosync and knet error codes = fix + -> 624b6a47 stats: Assert value_len when value is needed = assert + -> 09f6d34a logconfig: Remove double free of value = fix + -> efe48120 totemconfig: Free leaks found by coverity = fix -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes Status in corosync package in Ubuntu: Confirmed Bug description: Together with fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = fix -> ca320bea votequorum: set wfa status only on startup = fix -> 5f543465 quorumtool: exit on invalid expected votes = fix -> 0c16442f votequorum: Change check of expected_votes = fix -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix -> 89b0d62f stats: Check return code of stats_map_get = fix -> 56ee8503 quorumtool: Assert copied string length= assert -> 1fb095b0 notifyd: Check cmap_track_add result = assert -> 8ff7760c cmapctl: Free bin_value on error = fix -> 35c312f8 votequorum: Assert copied strings length = assert -> 29109683 totemknet: Assert strcpy length assert = assert -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call = assert -> a24cbad5 totemconfig: Initialize warnings variable = build fix -> 74eed54a sync: Assert sync_callbacks.name length= assert -> 380b744e totemknet: Don't mix corosync and knet error codes = fix -> 624b6a47 stats: Assert value_len when value is needed = assert -> 09f6d34a logconfig: Remove double free of value = fix -> efe48120 totemconfig: Free leaks found by coverity = fix To manage notifications about this bug go to:
[Ubuntu-ha] [Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/corosync/+git/corosync/+merge/381355 -- You received this bug notification because you are a member of Ubuntu High Availability 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 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/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1425431] Re: Pacemaker [SIGSEGV - Segmentation violation] using with Heartbeat 3.x
Thank you for taking the time to report this bug. In an effort to keep an up-to-date and valid list of bugs to work on, I have reviewed this report to verify it still requires effort and occurs on an Ubuntu release in standard support, and it does not. Judging by the existing comments, other related bugs and the pointed upstream discussion thread, it appears that the wrong lrmd was being set after upgrade and that led existing cluster to confusion when connecting to the local resource manager daemon. It is unfortunate that we were unable to resolve this defect, however there appears to be no further action possible at this time. I am therefore moving the bug to 'Incomplete'. If you disagree or have new information, we would be grateful if you could please add a comment stating why and then change the status of the bug to 'New'. ** Also affects: pacemaker (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Trusty) Status: New => Triaged ** Changed in: pacemaker (Ubuntu) Status: Confirmed => Fix Released ** Changed in: pacemaker (Ubuntu Trusty) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1425431 Title: Pacemaker [SIGSEGV - Segmentation violation] using with Heartbeat 3.x Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Trusty: Incomplete Bug description: According to: http://oss.clusterlabs.org/pipermail/pacemaker/2013-November/020152.html and my test case using: Pacemaker - Version: 1.1.10+git20130802-1ubuntu2.3 - Architecture: armhf Hearbeat - Version: 1:3.0.5-3.2 - Architecture: armhf Cluster-Glue- Version: 1.0.11+hg2754-1.1build1 - Architecture: armhf I got (into syslog): ccm: [4356]: info: Hostname: ccm: [4356]: info: Break tie for 2 nodes cluster ccm: [4356]: WARN: ccm_state_joined: received message with unknown cookie, just dropping ccm: [4356]: info: client (pid=4361) removed from ccm heartbeat: [4269]: WARN: Managed /usr/lib/heartbeat/crmd process 4361 killed by signal 11 [SIGSEGV - Segmentation violation]. heartbeat: [4269]: ERROR: Client /usr/lib/heartbeat/crmd (pid=4361) killed by signal 11. heartbeat: [4269]: ERROR: Respawning client "/usr/lib/heartbeat/crmd": heartbeat: [4269]: info: Starting child client "/usr/lib/heartbeat/crmd" (109,114) heartbeat: [4427]: info: Starting "/usr/lib/heartbeat/crmd" as uid 109 gid 114 (pid 4427) heartbeat: [4269]: info: the send queue length from heartbeat to client crmd is set to 1024 heartbeat: [4269]: info: killing /usr/lib/heartbeat/crmd process group 4427 with signal 15 heartbeat: [4269]: info: Core process 4273 exited. 7 remaining heartbeat: [4269]: info: Core process 4274 exited. 6 remaining heartbeat: [4269]: info: Core process 4275 exited. 5 remaining heartbeat: [4269]: info: Core process 4276 exited. 4 remaining heartbeat: [4269]: info: Core process 4277 exited. 3 remaining heartbeat: [4269]: info: Core process 4278 exited. 2 remaining then node always reboot by crmd after some time. Using Heartbeat without Pacemaker (crm no into ha.cf) no problem occur. Note that /usr/lib/heartbeat/crmd are soft links to: lrwxrwxrwx 1 root root 18 Feb 5 19:51 /usr/lib/heartbeat/attrd -> ../pacemaker/attrd lrwxrwxrwx 1 root root 16 Feb 5 19:51 /usr/lib/heartbeat/cib -> ../pacemaker/cib lrwxrwxrwx 1 root root 17 Feb 5 19:51 /usr/lib/heartbeat/crmd -> ../pacemaker/crmd lrwxrwxrwx 1 root root 20 Feb 5 19:51 /usr/lib/heartbeat/pengine -> ../pacemaker/pengine lrwxrwxrwx 1 root root 21 Feb 5 19:51 /usr/lib/heartbeat/stonithd -> ../pacemaker/stonithd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1425431/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1049037] Re: Pacemaker 1.1.6 VirtualDomain OCF wrong timeout handle on shutdown
Fix was already included in current pacemaker version by patch: commit fcfe6fe522138343e4138248829926700fac213e Author: Yan Gao Date: Mon Oct 17 11:19:01 2011 +0800 Medium: crmd: Send out all of the meta parameters to lrmd for stop actions So I'm flagging this as "Fix Released" as it does not affect current supported versions of pacemaker. ** Changed in: pacemaker (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1049037 Title: Pacemaker 1.1.6 VirtualDomain OCF wrong timeout handle on shutdown Status in pacemaker package in Ubuntu: Fix Released Bug description: Pacemaker 1.1.6 included in current LTS has a bug which causes VirtualDomain to fail upon VM shutdown. Full thread with explaination here: http://www.gossamer-threads.com/lists/linuxha/pacemaker/78969 it would be great if either the patch is backported or Pacemaker upgraded into LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1049037/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1322899] Re: pacemaker init script links aren't created on upgrade
*** This bug is a duplicate of bug 1052449 *** https://bugs.launchpad.net/bugs/1052449 ** This bug has been marked a duplicate of bug 1052449 corosync hangs due to missing pacemaker shutdown scripts -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1322899 Title: pacemaker init script links aren't created on upgrade Status in pacemaker package in Ubuntu: Triaged Bug description: When upgrading my pacemaker/corosync machines from ubuntu 12.04 to 14.04, update-rc.d for pacemaker is not run, so the new pacemaker init.d script is never executed on system startup, causing corosync/pacemaker HA system to not start. When adding the new pacemaker init.d script, update-rc.d should be run, so pacemaker init.d is run to start pacemaker as needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1322899/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1869622] Re: [focal] corosync v3.0.3 last upstream fixes
** Changed in: corosync (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes Status in corosync package in Ubuntu: In Progress Bug description: Together with fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = fix -> ca320bea votequorum: set wfa status only on startup = fix -> 5f543465 quorumtool: exit on invalid expected votes = fix -> 0c16442f votequorum: Change check of expected_votes = fix -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix -> 89b0d62f stats: Check return code of stats_map_get = fix -> 56ee8503 quorumtool: Assert copied string length= assert -> 1fb095b0 notifyd: Check cmap_track_add result = assert -> 8ff7760c cmapctl: Free bin_value on error = fix -> 35c312f8 votequorum: Assert copied strings length = assert -> 29109683 totemknet: Assert strcpy length assert = assert -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call = assert -> a24cbad5 totemconfig: Initialize warnings variable = build fix -> 74eed54a sync: Assert sync_callbacks.name length= assert -> 380b744e totemknet: Don't mix corosync and knet error codes = fix -> 624b6a47 stats: Assert value_len when value is needed = assert -> 09f6d34a logconfig: Remove double free of value = fix -> efe48120 totemconfig: Free leaks found by coverity = fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found
BUG: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622 PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging ** Changed in: corosync (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1677684 Title: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb- blackbox: not found 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: Confirmed Status in corosync source package in Zesty: Won't Fix Status in corosync source package in Bionic: Confirmed Status in corosync source package in Disco: Won't Fix Status in corosync source package in Eoan: Confirmed Status in corosync source package in Focal: In Progress Bug description: [Environment] Ubuntu Xenial 16.04 Amd64 [Test Case] 1) sudo apt-get install corosync 2) sudo corosync-blackbox. root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep black /usr/bin/corosync-blackbox Expected results: corosync-blackbox runs OK. Current results: $ sudo corosync-blackbox /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found [Impact] * Cannot run corosync-blackbox [Regression Potential] * None identified. [Fix] Make the package dependant of libqb-dev root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep qb-bl /usr/sbin/qb-blackbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 955164] Re: PostgreSQL resource agent has wrong default paths
Thank you for taking the time to report this bug. In an effort to keep an up-to-date and valid list of bugs to work on, I have reviewed this report to verify it still requires effort and occurs on an Ubuntu release in standard support, and it does not. It is unfortunate that we were unable to resolve this defect, however there appears to be no further action possible at this time. I am therefore moving the bug to 'Incomplete'. If you disagree or have new information, we would be grateful if you could please add a comment stating why and then change the status of the bug to 'New'. Observation: The correct affected package for this bug is resource-agents: (k)rafaeldtinoco@clufocal01:~$ dpkg -L resource-agents | grep -i pgsql /usr/lib/ocf/resource.d/heartbeat/pgsql and I'm opening a generic bug to check ALL resource agents paths existence. ** Also affects: resource-agents (Ubuntu) Importance: Undecided Status: New ** No longer affects: pacemaker (Ubuntu) ** Also affects: resource-agents (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: resource-agents (Ubuntu Precise) Status: New => Incomplete ** Changed in: resource-agents (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/955164 Title: PostgreSQL resource agent has wrong default paths Status in resource-agents package in Ubuntu: Invalid Status in resource-agents source package in Precise: Incomplete Bug description: The pgsql resource agent has default paths which don't match those used by the Ubuntu postgresql package In the resource agent: * The default configuration file is /etc/postgresql/9.1/main/postgresql.conf * The default loction of pg_ctl is /usr/lib/postgresql/9.1/bin/pg_ctl * The default data directory is given as /var/lib/pgsql/data This causes Pacemaker to be unable to start the postgresql server, and the following errors in /var/log/syslog: Mar 14 14:51:38 OB1 pgsql[3533]: ERROR: Configuration file /var/lib/pgsql/data/postgresql.conf doesn't exist Mar 14 14:51:38 OB1 pgsql[3533]: ERROR: Setup problem: couldn't find command: /usr/bin/pg_ctl The problem is in the file /usr/lib/ocf/resource.d/heartbeat/pgsql The following patch fixes these problems: = --- pgsql.old 2012-03-14 15:17:09.123507205 + +++ pgsql 2012-03-14 15:19:37.521641615 + @@ -45,13 +45,13 @@ } # Defaults -OCF_RESKEY_pgctl_default=/usr/bin/pg_ctl +OCF_RESKEY_pgctl_default=/usr/lib/postgresql/9.1/bin/pg_ctl OCF_RESKEY_psql_default=/usr/bin/psql -OCF_RESKEY_pgdata_default=/var/lib/pgsql/data +OCF_RESKEY_pgdata_default=/var/lib/postgresql/9.1/main OCF_RESKEY_pgdba_default=postgres OCF_RESKEY_pghost_default="" OCF_RESKEY_pgport_default=5432 -OCF_RESKEY_config_default="" +OCF_RESKEY_config_default=/etc/postgresql/9.1/main/postgresql.conf OCF_RESKEY_start_opt_default="" OCF_RESKEY_pgdb_default=template1 OCF_RESKEY_logfile_default=/dev/null = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/955164/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1227580] Re: Monitoring in Master state doesn't always work
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.
** Changed in: pacemaker (Ubuntu Precise)
Status: New => Incomplete
** Changed in: pacemaker (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1227580
Title:
Monitoring in Master state doesn't always work
Status in pacemaker package in Ubuntu:
Fix Released
Status in pacemaker source package in Precise:
Incomplete
Bug description:
Hi
There is a bug that master/slave resources are not always monitored. It is
already fixed in pacemaker trunk, but not in libpengine3 1.1.6-2ubuntu3. I
patched lib/pengine/unpack.c
1391c1391,1395
< } else if(safe_str_eq(task, CRMD_ACTION_START)) {
---
> } else if(safe_str_eq(task, CRMD_ACTION_START) ||
> safe_str_eq(task, CRMD_ACTION_MIGRATED) ||
> safe_str_eq(task, CRMD_ACTION_PROMOTE) ||
> safe_str_eq(task, CRMD_ACTION_DEMOTE)) {
>
With this monitoring also works if resource has been promoted. This
bug can cause much trouble as a failed service wont be recognized.
Best regards
Achim
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1227580/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1227580] Re: Monitoring in Master state doesn't always work
The mentioned patch is the following one:
commit fc03be02bf3a045babfe8233cbc99227da71d024
Author: David Vossel
Date: Fri Jun 29 11:24:52 2012 -0500
High: pengine: cl#5072 - Fixes monitor op stopping after rsc
promotion.
and was supposed to be applied to Precise.
** Also affects: pacemaker (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1227580
Title:
Monitoring in Master state doesn't always work
Status in pacemaker package in Ubuntu:
Fix Released
Status in pacemaker source package in Precise:
Incomplete
Bug description:
Hi
There is a bug that master/slave resources are not always monitored. It is
already fixed in pacemaker trunk, but not in libpengine3 1.1.6-2ubuntu3. I
patched lib/pengine/unpack.c
1391c1391,1395
< } else if(safe_str_eq(task, CRMD_ACTION_START)) {
---
> } else if(safe_str_eq(task, CRMD_ACTION_START) ||
> safe_str_eq(task, CRMD_ACTION_MIGRATED) ||
> safe_str_eq(task, CRMD_ACTION_PROMOTE) ||
> safe_str_eq(task, CRMD_ACTION_DEMOTE)) {
>
With this monitoring also works if resource has been promoted. This
bug can cause much trouble as a failed service wont be recognized.
Best regards
Achim
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1227580/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1869622] Re: [focal] corosync v3.0.3 last upstream fixes
For the 2 fixes: LP: #1437359 LP: #1677684 I have submitted to upstream the following merge request: https://salsa.debian.org/ha-team/corosync/-/merge_requests/2 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes Status in corosync package in Ubuntu: Confirmed Bug description: Together with fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = fix -> ca320bea votequorum: set wfa status only on startup = fix -> 5f543465 quorumtool: exit on invalid expected votes = fix -> 0c16442f votequorum: Change check of expected_votes = fix -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix -> 89b0d62f stats: Check return code of stats_map_get = fix -> 56ee8503 quorumtool: Assert copied string length= assert -> 1fb095b0 notifyd: Check cmap_track_add result = assert -> 8ff7760c cmapctl: Free bin_value on error = fix -> 35c312f8 votequorum: Assert copied strings length = assert -> 29109683 totemknet: Assert strcpy length assert = assert -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call = assert -> a24cbad5 totemconfig: Initialize warnings variable = build fix -> 74eed54a sync: Assert sync_callbacks.name length= assert -> 380b744e totemknet: Don't mix corosync and knet error codes = fix -> 624b6a47 stats: Assert value_len when value is needed = assert -> 09f6d34a logconfig: Remove double free of value = fix -> efe48120 totemconfig: Free leaks found by coverity = fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1869622] Re: [focal] corosync v3.0.3 last upstream fixes
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/corosync/+git/corosync/+merge/381355 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1869622 Title: [focal] corosync v3.0.3 last upstream fixes Status in corosync package in Ubuntu: In Progress Bug description: Together with fixes for: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359 https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 This bug will also backport/cherrypick the following post release fixes: -> c631951e icmap: icmap_init_r() leaks if trie_create() fails = fix -> ca320bea votequorum: set wfa status only on startup = fix -> 5f543465 quorumtool: exit on invalid expected votes = fix -> 0c16442f votequorum: Change check of expected_votes = fix -> 8ce65bf9 votequorum: Reflect runtime change of 2Node to WFA = fix -> 89b0d62f stats: Check return code of stats_map_get = fix -> 56ee8503 quorumtool: Assert copied string length= assert -> 1fb095b0 notifyd: Check cmap_track_add result = assert -> 8ff7760c cmapctl: Free bin_value on error = fix -> 35c312f8 votequorum: Assert copied strings length = assert -> 29109683 totemknet: Assert strcpy length assert = assert -> 0c118d8f totemknet: Check result of fcntl O_NONBLOCK call = assert -> a24cbad5 totemconfig: Initialize warnings variable = build fix -> 74eed54a sync: Assert sync_callbacks.name length= assert -> 380b744e totemknet: Don't mix corosync and knet error codes = fix -> 624b6a47 stats: Assert value_len when value is needed = assert -> 09f6d34a logconfig: Remove double free of value = fix -> efe48120 totemconfig: Free leaks found by coverity = fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/corosync/+git/corosync/+merge/381355 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1677684 Title: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb- blackbox: not found 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: Confirmed Status in corosync source package in Zesty: Won't Fix Status in corosync source package in Bionic: Confirmed Status in corosync source package in Disco: Won't Fix Status in corosync source package in Eoan: Confirmed Status in corosync source package in Focal: In Progress Bug description: [Environment] Ubuntu Xenial 16.04 Amd64 [Test Case] 1) sudo apt-get install corosync 2) sudo corosync-blackbox. root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep black /usr/bin/corosync-blackbox Expected results: corosync-blackbox runs OK. Current results: $ sudo corosync-blackbox /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found [Impact] * Cannot run corosync-blackbox [Regression Potential] * None identified. [Fix] Make the package dependant of libqb-dev root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep qb-bl /usr/sbin/qb-blackbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts
I'm marking Precise and Trusty as affected. The suggested fix is currently implemented by Xenial already: mcp/pacemaker.in: ... # Required-Start: $network corosync # Should-Start: $syslog # Required-Stop:$network corosync ... ** Also affects: pacemaker (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Xenial) Status: New => Fix Released ** Changed in: pacemaker (Ubuntu Trusty) Status: New => Confirmed ** Changed in: pacemaker (Ubuntu Precise) Status: New => Confirmed ** Changed in: pacemaker (Ubuntu) Status: Triaged => Fix Released ** Changed in: pacemaker (Ubuntu) Importance: High => Undecided ** Changed in: pacemaker (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: pacemaker (Ubuntu Precise) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1052449 Title: corosync hangs due to missing pacemaker shutdown scripts Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Precise: Triaged Status in pacemaker source package in Trusty: Triaged Status in pacemaker source package in Xenial: Fix Released Bug description: The pacemaker package installs the right init script but doesn't link it to the according runlevels. If corosync is activated and started on the system this leads to a hanging shutdown / reboot because corosync only ends if pacemaker is stopped beforehand. In addition to this the pacemaker daemon has to start after corosync but has to stop before corosync. A possible solution would be to link the init script accordingly an enable it throug /etc/default/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1412831] Re: crm_mon crashed with SIGABRT in g_return_if_fail_warning()
** Also affects: pacemaker (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Trusty) Status: New => Triaged ** Changed in: pacemaker (Ubuntu) Status: Confirmed => Fix Released ** Changed in: pacemaker (Ubuntu) Importance: Medium => Undecided ** Changed in: pacemaker (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1412831 Title: crm_mon crashed with SIGABRT in g_return_if_fail_warning() Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Trusty: Triaged Bug description: $ sudo crm_mon -1fA will generate a crash report. $ sudo crm_mon -1fA Last updated: Tue Jan 20 15:02:21 2015 Last change: Tue Jan 20 14:42:22 2015 via crmd on juju-nobuto-machine-46 Stack: corosync Current DC: juju-nobuto-machine-45 (1002) - partition with quorum Version: 1.1.10-42f2063 3 Nodes configured 4 Resources configured Online: [ juju-nobuto-machine-44 juju-nobuto-machine-45 juju-nobuto-machine-46 ] Clone Set: cl_ping [ping] Started: [ juju-nobuto-machine-44 juju-nobuto-machine-45 juju-nobuto-machine-46 ] Resource Group: grp_percona_cluster res_mysql_vip (ocf::heartbeat:IPaddr2): Started juju-nobuto-machine-44 Node Attributes: * Node juju-nobuto-machine-44: + pingd : 100 crm_glib_handler: Cannot wait on forked child 13386: No child processes (10) + pingd : 100 crm_glib_handler: Cannot wait on forked child 13388: No child processes (10) + pingd : 100 * Node juju-nobuto-machine-45: + pingd : 100 crm_glib_handler: Cannot wait on forked child 13390: No child processes (10) + pingd : 100 crm_glib_handler: Cannot wait on forked child 13392: No child processes (10) + pingd : 100 * Node juju-nobuto-machine-46: + pingd : 100 crm_glib_handler: Cannot wait on forked child 13394: No child processes (10) + pingd : 100 crm_glib_handler: Cannot wait on forked child 13396: No child processes (10) + pingd : 100 Migration summary: * Node juju-nobuto-machine-44: * Node juju-nobuto-machine-46: * Node juju-nobuto-machine-45: $ sudo crm configure show node $id="1000" juju-nobuto-machine-44 node $id="1001" juju-nobuto-machine-46 node $id="1002" juju-nobuto-machine-45 primitive ping ocf:pacemaker:ping \ params host_list="10.5.0.1" multiplier="100" \ op monitor interval="5s" primitive res_mysql_vip ocf:heartbeat:IPaddr2 \ params ip="10.5.100.1" cidr_netmask="16" nic="eth0" group grp_percona_cluster res_mysql_vip clone cl_ping ping \ meta interleave="true" location Ping-res_mysql_vip res_mysql_vip \ rule $id="Ping-res_mysql_vip-rule" -inf: pingd lte 0 property $id="cib-bootstrap-options" \ dc-version="1.1.10-42f2063" \ cluster-infrastructure="corosync" \ no-quorum-policy="stop" \ stonith-enabled="false" \ last-lrm-refresh="1421764942" rsc_defaults $id="rsc-options" \ resource-stickiness="100" ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: pacemaker-cli-utils 1.1.10+git20130802-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CrashCounter: 1 Date: Tue Jan 20 14:54:20 2015 Ec2AMI: ami-000f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 ExecutablePath: /usr/sbin/crm_mon ExecutableTimestamp: 1411498637 ProcCmdline: crm_mon -1fA ProcCwd: /home/ubuntu ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pacemaker StacktraceTop: g_return_if_fail_warning (log_domain=log_domain@entry=0x7fab566acb4e "GLib", pretty_function=pretty_function@entry=0x7fab566ba7e0 <__FUNCTION__.11709> "g_strsplit", expression=expression@entry=0x7fab56704fca "string != NULL") at /build/buildd/glib2.0-2.40.2/./glib/gmessages.c:1080 g_strsplit (string=0x0, delimiter=, max_tokens=) at /build/buildd/glib2.0-2.40.2/./glib/gstrfuncs.c:2269 print_attr_msg (node=0x7fab58af09e0, rsc_list=, attrname=0x7fab58afb5f0 "pingd", attrvalue=0x7fab58afb5d0 "100") at crm_mon.c:989 print_node_attribute (name=0x7fab58afb5f0, node_data=0x7fab58af09e0) at crm_mon.c:1042 g_list_foreach (list=, func=0x7fab5834c030 ,
