The SRU for LP: #1740892 is not started yet, but base on nacc's comment, It
should start soon :
I would suggest to wait for LP: #1740892 SRU to be completed first since
it affects package upgrade (corosync/pacemaker relation).
Additionally, IMHO, it may be "safer" to not introduce too much change
in one SRU, especially considering LP: #1740892 mark as Critical.
1) Please keep monitoring LP: #1740892 and let's wait for the SRU to turn "Fix
Released" for Trusty.
2) Then let's start LP: #1316970 SRU right after using either "STS-Sponsor" or
"Ubuntu Sponsors Team"
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
g_dbus memory leak in lrmd
Status in glib2.0 package in Ubuntu:
Status in pacemaker package in Ubuntu:
Status in glib2.0 source package in Trusty:
Status in pacemaker source package in Trusty:
lrmd daemon with upstart resource has memory leak in Trusty
affected to pacemaker 1.1.10.
affected to glib2.0 2.40.2-0ubuntu1
Please note that patch for pacemaker is created myself.
1. deploy 3 trusty instance.
2. install corosync, pacemaker, mysql.
3. setting with below info
3.1 corosync.conf, proper setting for 3 node
3.2 crm configure < setup.crm ( which has upstart:mysql setting )
3.3 monitor lrmd daemon's memory usage
Restarting daemon after upgrading this pkg will be needed. this patch added
NULL check for several parts. prior commit changed file structure. and This
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free
function myself. This might affect to system.
For glib2.0, commit  is critical, but ,, is needed for building
 commit a7b61e276120184c7586a3217ed3571a982f5017
Author: Andrew Beekhof <and...@beekhof.net>
Date: Fri Aug 23 16:25:35 2013 +1000
Refactor: attrd: Move to its own directory and create a stub for
$ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
$ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
$ rmadison pacemaker
pacemaker | 1.1.10+git20130802-1ubuntu2 | trusty
pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates
pacemaker | 1.1.14-2ubuntu1 | xenial
pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
pacemaker | 1.1.16-1ubuntu1 | zesty
pacemaker | 1.1.16-1ubuntu1 | artful
pacemaker | 1.1.18~rc3-1ubuntu1 | bionic
I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
(13.10) and have encountered a memory leak in lrmd.
The details of the bug are covered here in this thread
but to summarise, the Pacemaker developers believe the leak is caused
by the g_dbus API, the use of which was removed in Pacemaker 1.11.
I've also attached the Valgrind output from the run that exposed the
Given that this issue affects production stability (a periodic restart
of Pacemaker is required), will a version of 1.11 be released for
Trusty? (I'm happy to upgrade the OS to Trusty to get it).
If not, can you advise which version of the OS will be the first to
take 1.11 please?
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~sts-sponsors
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~sts-sponsors
More help : https://help.launchpad.net/ListHelp