[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
And here is the last core dump of my production system from today in the morning, also core included. ** Attachment added: _usr_lib_pacemaker_stonithd.0.crash https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4302102/+files/_usr_lib_pacemaker_stonithd.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
And this is the current cluster configuration of the testing environment. ** Attachment added: cib https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4302101/+files/cib -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Here is the crash file from my virtual testing environment, including core. I updated the nodes today with all current packages from trusty- proposed. The core dump happened just after restarting the nodes after the updates. ** Attachment added: _usr_lib_pacemaker_stonithd.0.crash https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4302100/+files/_usr_lib_pacemaker_stonithd.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
And here is the last core dump of my production system from today in the morning, also core included. ** Attachment added: _usr_lib_pacemaker_stonithd.0.crash https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4302102/+files/_usr_lib_pacemaker_stonithd.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Here is the crash file from my virtual testing environment, including core. I updated the nodes today with all current packages from trusty- proposed. The core dump happened just after restarting the nodes after the updates. ** Attachment added: _usr_lib_pacemaker_stonithd.0.crash https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4302100/+files/_usr_lib_pacemaker_stonithd.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
And this is the current cluster configuration of the testing environment. ** Attachment added: cib https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4302101/+files/cib -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Okay,
So the cherry-pick (for version
trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2, based on a upstream
commit) seems ok since it makes lrmd (services, services_linux) to avoid
repeating a timer when the source was already removed from glib main
loop context:
example:
+ if (op-opaque-repeat_timer) {
+ g_source_remove(op-opaque-repeat_timer);
++op-opaque-repeat_timer = 0;
etc...
This actually solved lrmd crashes I was getting with the testcase
(explained inside this bug summary).
===
Explanation:
g_source_remove -
http://oss.clusterlabs.org/pipermail/pacemaker/2014-October/022690.html
libglib2 changes -
http://oss.clusterlabs.org/pipermail/pacemaker/2014-October/022699.html
===
Analyzing your crash file (from stonith and not lrm), it looks like we
have the following scenario:
==
exited = child_waitpid(child, WNOHANG);
|_ child-callback(child, child-pid, core, signo, exitcode);
|_ stonith_action_async_done (stack shows: stonith_action_destroy())
call g_resource_remove 2 times
|_ stonith_action_clear_tracking_data(action);
|_ g_source_remove(action-timer_sigterm);
|_ g_critical (Source ID %u was not found when attempting to
remove it, tag);
WHERE
==
Child here is the monitor (0x7f1f63a08b70 monitor): /usr/sbin/fence_legacy
Helper that presents a RHCS-style interface for Linux-HA stonith plugins
This is the script responsible to monitor a stonith resource and it has
returned (triggering monitor
callback) with the following data on it:
-- data (begin) --
agent=fence_legacy
action=monitor
plugin=external/ssh
hostlist=kjpnode2
timeout=20
async=1
tries=1
remaining_timeout=20
timer_sigterm=13
timer_sigkill=14
max_retries=2
pid=1464
rc=0 (RETURN CODE)
string buffer: Performing: stonith -t external/ssh -S\nsuccess: 0\n
-- data (end) --
OBS: This means that fence_legacy returned, after checking that
st_kjpnode2 was ok, and its cleanup operation (callback) caused
the problem we faced.
As soon as it dies, the callback for this process is called:
if (child-callback) {
child-callback(child, child-pid, core, signo, exitcode);
In our case, callback is:
0x7f1f6189cec0 stonith_action_async_donewhich
calls
0x7f1f6189af10 stonith_action_destroyand
then
0x7f1f6189ae60 stonith_action_clear_tracking_datagenerating the
2nd removal (g_source_remove)
with the 2nd call to g_source_remove, after glib2.0 change explained
before this comment, we get a
g_critical (Source ID %u was not found when attempting to remove it,
tag);
and this generates the crash (since g_glob is called with a critical
log_level causing crm_abort to be called).
POSSIBLE CAUSE:
==
Under stonith_action_async_done we have:
stonith_action_t *action = 0x7f1f639f5b50.
if (action-timer_sigterm 0) {
g_source_remove(action-timer_sigterm);
}
if (action-timer_sigkill 0) {
g_source_remove(action-timer_sigkill);
}
Under stonith_action_destroy we have stonith_action_t *action =
0x7f1f639f5b50.
and a call to: stonith_action_clear_tracking_data(action);
Under stonith_action_clear_tracking_data(stonith_action_t * action) we
have AGAIN:
stonith_action_t *action = 0x7f1f639f5b50.
if (action-timer_sigterm 0) {
g_source_remove(action-timer_sigterm);
action-timer_sigterm = 0;
}
if (action-timer_sigkill 0) {
g_source_remove(action-timer_sigkill);
action-timer_sigkill = 0;
}
This logic probably triggered the same problem the cherry pick addressed for
lrmd,
but now for stonith (calling g_source_remove 2 times for the same source after
glib2.0 was changed).
I'll try to discuss this with upstream and confirm that this is
happening.
Thank you
Rafael Tinoco
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Okay,
So the cherry-pick (for version
trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2, based on a upstream
commit) seems ok since it makes lrmd (services, services_linux) to avoid
repeating a timer when the source was already removed from glib main
loop context:
example:
+ if (op-opaque-repeat_timer) {
+ g_source_remove(op-opaque-repeat_timer);
++op-opaque-repeat_timer = 0;
etc...
This actually solved lrmd crashes I was getting with the testcase
(explained inside this bug summary).
===
Explanation:
g_source_remove -
http://oss.clusterlabs.org/pipermail/pacemaker/2014-October/022690.html
libglib2 changes -
http://oss.clusterlabs.org/pipermail/pacemaker/2014-October/022699.html
===
Analyzing your crash file (from stonith and not lrm), it looks like we
have the following scenario:
==
exited = child_waitpid(child, WNOHANG);
|_ child-callback(child, child-pid, core, signo, exitcode);
|_ stonith_action_async_done (stack shows: stonith_action_destroy())
call g_resource_remove 2 times
|_ stonith_action_clear_tracking_data(action);
|_ g_source_remove(action-timer_sigterm);
|_ g_critical (Source ID %u was not found when attempting to
remove it, tag);
WHERE
==
Child here is the monitor (0x7f1f63a08b70 monitor): /usr/sbin/fence_legacy
Helper that presents a RHCS-style interface for Linux-HA stonith plugins
This is the script responsible to monitor a stonith resource and it has
returned (triggering monitor
callback) with the following data on it:
-- data (begin) --
agent=fence_legacy
action=monitor
plugin=external/ssh
hostlist=kjpnode2
timeout=20
async=1
tries=1
remaining_timeout=20
timer_sigterm=13
timer_sigkill=14
max_retries=2
pid=1464
rc=0 (RETURN CODE)
string buffer: Performing: stonith -t external/ssh -S\nsuccess: 0\n
-- data (end) --
OBS: This means that fence_legacy returned, after checking that
st_kjpnode2 was ok, and its cleanup operation (callback) caused
the problem we faced.
As soon as it dies, the callback for this process is called:
if (child-callback) {
child-callback(child, child-pid, core, signo, exitcode);
In our case, callback is:
0x7f1f6189cec0 stonith_action_async_donewhich
calls
0x7f1f6189af10 stonith_action_destroyand
then
0x7f1f6189ae60 stonith_action_clear_tracking_datagenerating the
2nd removal (g_source_remove)
with the 2nd call to g_source_remove, after glib2.0 change explained
before this comment, we get a
g_critical (Source ID %u was not found when attempting to remove it,
tag);
and this generates the crash (since g_glob is called with a critical
log_level causing crm_abort to be called).
POSSIBLE CAUSE:
==
Under stonith_action_async_done we have:
stonith_action_t *action = 0x7f1f639f5b50.
if (action-timer_sigterm 0) {
g_source_remove(action-timer_sigterm);
}
if (action-timer_sigkill 0) {
g_source_remove(action-timer_sigkill);
}
Under stonith_action_destroy we have stonith_action_t *action =
0x7f1f639f5b50.
and a call to: stonith_action_clear_tracking_data(action);
Under stonith_action_clear_tracking_data(stonith_action_t * action) we
have AGAIN:
stonith_action_t *action = 0x7f1f639f5b50.
if (action-timer_sigterm 0) {
g_source_remove(action-timer_sigterm);
action-timer_sigterm = 0;
}
if (action-timer_sigkill 0) {
g_source_remove(action-timer_sigkill);
action-timer_sigkill = 0;
}
This logic probably triggered the same problem the cherry pick addressed for
lrmd,
but now for stonith (calling g_source_remove 2 times for the same source after
glib2.0 was changed).
I'll try to discuss this with upstream and confirm that this is
happening.
Thank you
Rafael Tinoco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
I just found one upstream commit fixing this:
##
commit 0326f05c9e26f39a394fa30830e31a76306f49c7
Author: Andrew Beekhof and...@beekhof.net
Date: Thu Aug 7 13:49:24 2014 +1000
Fix: stonith-ng: Reset mainloop source IDs after removing them
diff --git a/lib/fencing/st_client.c b/lib/fencing/st_client.c
index 64bd8f3..2837682 100644
--- a/lib/fencing/st_client.c
+++ b/lib/fencing/st_client.c
@@ -663,9 +663,11 @@ stonith_action_async_done(mainloop_child_t * p, pid_t pid,
int core, int signo,
if (action-timer_sigterm 0) {
g_source_remove(action-timer_sigterm);
+action-timer_sigterm = 0;
}
if (action-timer_sigkill 0) {
g_source_remove(action-timer_sigkill);
+action-timer_sigkill = 0;
}
if (action-last_timeout_signo) {
##
under stonith_action_async_done.
Will provide you a hotfix with this fix and ask for feedback.
Thank you
Rafael
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
I just found one upstream commit fixing this:
##
commit 0326f05c9e26f39a394fa30830e31a76306f49c7
Author: Andrew Beekhof and...@beekhof.net
Date: Thu Aug 7 13:49:24 2014 +1000
Fix: stonith-ng: Reset mainloop source IDs after removing them
diff --git a/lib/fencing/st_client.c b/lib/fencing/st_client.c
index 64bd8f3..2837682 100644
--- a/lib/fencing/st_client.c
+++ b/lib/fencing/st_client.c
@@ -663,9 +663,11 @@ stonith_action_async_done(mainloop_child_t * p, pid_t pid,
int core, int signo,
if (action-timer_sigterm 0) {
g_source_remove(action-timer_sigterm);
+action-timer_sigterm = 0;
}
if (action-timer_sigkill 0) {
g_source_remove(action-timer_sigkill);
+action-timer_sigkill = 0;
}
if (action-last_timeout_signo) {
##
under stonith_action_async_done.
Will provide you a hotfix with this fix and ask for feedback.
Thank you
Rafael
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Peter, (1) During the test execution, does using more then 2 nodes AND/OR changing no-quorum-policy to something else (freeze, stop, suicide) does help ? (2) Your crash files do not contain the core file, could you please provide me the core file (probably changing ulimit inside /etc/security/limits.conf to allow core file generation). I'm executing the testcase again on a 4-node lab machine and still no dump (only difference is that I'm running the test on a 4 node setup with quorum policy=stop and ssh fencing (ssh fencing just like your last attempt)). I'm also curious about this: ii pacemaker-cli-utils 1.1.10+git20130802-1ubuntu2.1amd64 Command line interface utilities for Pacemaker On the package update, pacemaker-cli-utils did not get update together ? Thank you Rafael PS: Meanwhile my testcase is running to see if I can trigger this problem again (before the patch I was getting core files in between each 10 minutes). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Peter, (1) During the test execution, does using more then 2 nodes AND/OR changing no-quorum-policy to something else (freeze, stop, suicide) does help ? (2) Your crash files do not contain the core file, could you please provide me the core file (probably changing ulimit inside /etc/security/limits.conf to allow core file generation). I'm executing the testcase again on a 4-node lab machine and still no dump (only difference is that I'm running the test on a 4 node setup with quorum policy=stop and ssh fencing (ssh fencing just like your last attempt)). I'm also curious about this: ii pacemaker-cli-utils 1.1.10+git20130802-1ubuntu2.1amd64 Command line interface utilities for Pacemaker On the package update, pacemaker-cli-utils did not get update together ? Thank you Rafael PS: Meanwhile my testcase is running to see if I can trigger this problem again (before the patch I was getting core files in between each 10 minutes). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
For now, I have tested the following scenarios: - 4 nodes - stonith-enabled=true - no-quorum-policy=stop AND - 2 nodes only - stonith-enabled=true - no-quorum-policy=ignore I ran the test case (bug description) for hours and could not get a crash, although I do get the following messages (expected) from time to time: Jan 19 16:52:23 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 12418 to record non-fatal assert at logging.c:63 : Source ID 73 was not found when attempting to remove it Jan 19 16:52:23 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 12439 to record non-fatal assert at logging.c:63 : Source ID 74 was not found when attempting to remove it Jan 19 16:52:38 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 13413 to record non-fatal assert at logging.c:63 : Source ID 76 was not found when attempting to remove it Jan 19 16:52:38 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 13429 to record non-fatal assert at logging.c:63 : Source ID 77 was not found when attempting to remove it Jan 19 16:52:52 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 14411 to record non-fatal assert at logging.c:63 : Source ID 79 was not found when attempting to remove it Jan 19 16:52:52 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 14423 to record non-fatal assert at logging.c:63 : Source ID 80 was not found when attempting to remove it Jan 19 16:53:07 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 15410 to record non-fatal assert at logging.c:63 : Source ID 82 was not found when attempting to remove it Jan 19 16:53:07 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 15427 to record non-fatal assert at logging.c:63 : Source ID 83 was not found when attempting to remove it Jan 19 16:53:21 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 16409 to record non-fatal assert at logging.c:63 : Source ID 85 was not found when attempting to remove it Jan 19 16:53:21 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 16425 to record non-fatal assert at logging.c:63 : Source ID 86 was not found when attempting to remove it Jan 19 16:53:35 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 17408 to record non-fatal assert at logging.c:63 : Source ID 88 was not found when attempting to remove it Jan 19 16:53:35 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 17420 to record non-fatal assert at logging.c:63 : Source ID 89 was not found when attempting to remove it Jan 19 16:53:50 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 18409 to record non-fatal assert at logging.c:63 : Source ID 91 was not found when attempting to remove it Jan 19 16:53:50 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 18422 to record non-fatal assert at logging.c:63 : Source ID 92 was not found when attempting to remove it Jan 19 16:54:04 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 19410 to record non-fatal assert at logging.c:63 : Source ID 94 was not found when attempting to remove it Jan 19 16:54:04 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 19426 to record non-fatal assert at logging.c:63 : Source ID 95 was not found when attempting to remove it Depending on Peter to get his crash + core dump for the analysis. Thank you Rafael Tinoco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
For now, I have tested the following scenarios: - 4 nodes - stonith-enabled=true - no-quorum-policy=stop AND - 2 nodes only - stonith-enabled=true - no-quorum-policy=ignore I ran the test case (bug description) for hours and could not get a crash, although I do get the following messages (expected) from time to time: Jan 19 16:52:23 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 12418 to record non-fatal assert at logging.c:63 : Source ID 73 was not found when attempting to remove it Jan 19 16:52:23 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 12439 to record non-fatal assert at logging.c:63 : Source ID 74 was not found when attempting to remove it Jan 19 16:52:38 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 13413 to record non-fatal assert at logging.c:63 : Source ID 76 was not found when attempting to remove it Jan 19 16:52:38 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 13429 to record non-fatal assert at logging.c:63 : Source ID 77 was not found when attempting to remove it Jan 19 16:52:52 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 14411 to record non-fatal assert at logging.c:63 : Source ID 79 was not found when attempting to remove it Jan 19 16:52:52 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 14423 to record non-fatal assert at logging.c:63 : Source ID 80 was not found when attempting to remove it Jan 19 16:53:07 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 15410 to record non-fatal assert at logging.c:63 : Source ID 82 was not found when attempting to remove it Jan 19 16:53:07 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 15427 to record non-fatal assert at logging.c:63 : Source ID 83 was not found when attempting to remove it Jan 19 16:53:21 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 16409 to record non-fatal assert at logging.c:63 : Source ID 85 was not found when attempting to remove it Jan 19 16:53:21 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 16425 to record non-fatal assert at logging.c:63 : Source ID 86 was not found when attempting to remove it Jan 19 16:53:35 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 17408 to record non-fatal assert at logging.c:63 : Source ID 88 was not found when attempting to remove it Jan 19 16:53:35 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 17420 to record non-fatal assert at logging.c:63 : Source ID 89 was not found when attempting to remove it Jan 19 16:53:50 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 18409 to record non-fatal assert at logging.c:63 : Source ID 91 was not found when attempting to remove it Jan 19 16:53:50 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 18422 to record non-fatal assert at logging.c:63 : Source ID 92 was not found when attempting to remove it Jan 19 16:54:04 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 19410 to record non-fatal assert at logging.c:63 : Source ID 94 was not found when attempting to remove it Jan 19 16:54:04 [941] trusty01 stonith-ng:error: crm_abort: crm_glib_handler: Forked child 19426 to record non-fatal assert at logging.c:63 : Source ID 95 was not found when attempting to remove it Depending on Peter to get his crash + core dump for the analysis. Thank you Rafael Tinoco -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Attachment added: dpkg-versions https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4298137/+files/dpkg-versions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
I set up a testing environment with 2 VMs, trusty-proposed enabled, all updates installed and the following minimal cluster configuration: node $id=168427521 kjpnode1 \ attributes standby=off node $id=168427522 kjpnode2 \ attributes standby=on primitive st_kjpnode1 stonith:external/ssh \ params hostlist=kjpnode1 primitive st_kjpnode2 stonith:external/ssh \ params hostlist=kjpnode2 location st_kjpnode1_loc st_kjpnode1 -inf: kjpnode1 location st_kjpnode2_loc st_kjpnode2 -inf: kjpnode2 property $id=cib-bootstrap-options \ dc-version=1.1.10-42f2063 \ cluster-infrastructure=corosync \ no-quorum-policy=ignore I still get core dumps of stonithd. Peter ** Attachment added: _usr_lib_pacemaker_stonithd.0.crash https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4298136/+files/_usr_lib_pacemaker_stonithd.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Attachment added: dpkg-versions https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4298137/+files/dpkg-versions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
I set up a testing environment with 2 VMs, trusty-proposed enabled, all updates installed and the following minimal cluster configuration: node $id=168427521 kjpnode1 \ attributes standby=off node $id=168427522 kjpnode2 \ attributes standby=on primitive st_kjpnode1 stonith:external/ssh \ params hostlist=kjpnode1 primitive st_kjpnode2 stonith:external/ssh \ params hostlist=kjpnode2 location st_kjpnode1_loc st_kjpnode1 -inf: kjpnode1 location st_kjpnode2_loc st_kjpnode2 -inf: kjpnode2 property $id=cib-bootstrap-options \ dc-version=1.1.10-42f2063 \ cluster-infrastructure=corosync \ no-quorum-policy=ignore I still get core dumps of stonithd. Peter ** Attachment added: _usr_lib_pacemaker_stonithd.0.crash https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4298136/+files/_usr_lib_pacemaker_stonithd.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Okay, I'm revisiting this today. Tks for the crash, I'll try to reproduce what you are getting also. Tinoco -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
If I configure the test environment like my production system (with the exception of the stonith agent, of course) I get additional core dumps of lrmd. Peter ** Attachment added: _usr_lib_pacemaker_lrmd.0.crash https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4298316/+files/_usr_lib_pacemaker_lrmd.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
If I configure the test environment like my production system (with the exception of the stonith agent, of course) I get additional core dumps of lrmd. Peter ** Attachment added: _usr_lib_pacemaker_lrmd.0.crash https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4298316/+files/_usr_lib_pacemaker_lrmd.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Okay, I'm revisiting this today. Tks for the crash, I'll try to reproduce what you are getting also. Tinoco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
I also experience crashes of stonithd, alone 2 times yesterday, always
on both nodes at the same time. Here is the stack trace:
root@kjp03:/var/crash# apport-retrace -Rs _usr_lib_pacemaker_stonithd.0.crash
E: Can not find version '1.1.10+git20130802-1ubuntu2.2' of package 'pacemaker'
E: Quellpaket für pacemaker kann nicht gefunden werden.
--- stack trace ---
#0 0x7ffa6f17abb9 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 40008
selftid = 40008
#1 0x7ffa6f17dfc8 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0},
sa_mask = {__val = {0, 17179869185, 140713634797360, 140713634496512, 0,
140734633026224, 140713582943175, 140713586093704, 140734633026160, 397168, 32,
140713586088608, 0, 140713586088608, 140713582942786, 140713579551566}},
sa_flags = 1876903824, sa_restorer = 0x3f}
sigs = {__val = {32, 0 repeats 15 times}}
#2 0x7ffa6fdcf6c9 in crm_abort (file=0x7ffa6fdf34bb logging.c,
function=0x7ffa6fdf4790 __PRETTY_FUNCTION__.22958 crm_glib_handler,
line=63, assert_condition=0x7ffa72376ce0 Source ID 541 was not found when
attempting to remove it, do_core=optimized out, do_fork=optimized out) at
utils.c:1118
rc = 0
pid = optimized out
status = 0
__func__ = crm_abort
#3 0x7ffa6ee8bae1 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7ffa6ee8bd72 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7ffa6ee83c5c in g_source_remove () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6 0x7ffa6f999ef5 in stonith_action_clear_tracking_data
(action=action@entry=0x7ffa723350b0) at st_client.c:536
No locals.
#7 0x7ffa6f999f2d in stonith_action_destroy (action=0x7ffa723350b0) at
st_client.c:557
No locals.
#8 0x7ffa6fde7cd9 in child_waitpid (child=child@entry=0x7ffa7236bb20,
flags=flags@entry=1) at mainloop.c:948
rc = optimized out
core = optimized out
signo = 0
status = 0
exitcode = 0
__func__ = child_waitpid
#9 0x7ffa6fde7fce in child_death_dispatch (signal=optimized out) at
mainloop.c:962
saved = 0x0
child = 0x7ffa7236bb20
iter = 0x7ffa7222d200
exited = optimized out
__func__ = child_death_dispatch
#10 0x7ffa6fde6de7 in crm_signal_dispatch (source=0x7ffa7236ba50,
callback=optimized out, userdata=optimized out) at mainloop.c:275
__func__ = crm_signal_dispatch
#11 0x7ffa6ee84e04 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#12 0x7ffa6ee85048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#13 0x7ffa6ee8530a in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#14 0x7ffa702282a9 in main (argc=optimized out, argv=optimized out) at
main.c:1136
flag = optimized out
lpc = 0
argerr = optimized out
option_index = 0
cluster = {uuid = 0x7ffa7222fba0 167772162, uname = 0x7ffa72230280
kjp03, nodeid = 167772162, destroy = 0x7ffa70229b40
stonith_peer_cs_destroy, hb_conn = 0x0, hb_dispatch = 0x7ffa702299c0
stonith_peer_hb_callback, group = {length = 128, value = stonith-ng, '\000'
repeats 117 times}, cpg = {cpg_deliver_fn = 0x7ffa702298e0
stonith_peer_ais_callback, cpg_confchg_fn = 0x7ffa6fbb04a0
pcmk_cpg_membership}, cpg_handle = 7749363892505018368}
actions = {0x7ffa70236d7d reboot, 0x7ffa70236d84 off,
0x7ffa7023893f list, 0x7ffa70236d88 monitor, 0x7ffa70236d90 status}
__func__ = main
I also attach the crash report
Peter
** Attachment added: _usr_lib_pacemaker_stonithd.0.crash
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4293914/+files/_usr_lib_pacemaker_stonithd.0.crash
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
I also experience crashes of stonithd, alone 2 times yesterday, always
on both nodes at the same time. Here is the stack trace:
root@kjp03:/var/crash# apport-retrace -Rs _usr_lib_pacemaker_stonithd.0.crash
E: Can not find version '1.1.10+git20130802-1ubuntu2.2' of package 'pacemaker'
E: Quellpaket für pacemaker kann nicht gefunden werden.
--- stack trace ---
#0 0x7ffa6f17abb9 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 40008
selftid = 40008
#1 0x7ffa6f17dfc8 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0},
sa_mask = {__val = {0, 17179869185, 140713634797360, 140713634496512, 0,
140734633026224, 140713582943175, 140713586093704, 140734633026160, 397168, 32,
140713586088608, 0, 140713586088608, 140713582942786, 140713579551566}},
sa_flags = 1876903824, sa_restorer = 0x3f}
sigs = {__val = {32, 0 repeats 15 times}}
#2 0x7ffa6fdcf6c9 in crm_abort (file=0x7ffa6fdf34bb logging.c,
function=0x7ffa6fdf4790 __PRETTY_FUNCTION__.22958 crm_glib_handler,
line=63, assert_condition=0x7ffa72376ce0 Source ID 541 was not found when
attempting to remove it, do_core=optimized out, do_fork=optimized out) at
utils.c:1118
rc = 0
pid = optimized out
status = 0
__func__ = crm_abort
#3 0x7ffa6ee8bae1 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7ffa6ee8bd72 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7ffa6ee83c5c in g_source_remove () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6 0x7ffa6f999ef5 in stonith_action_clear_tracking_data
(action=action@entry=0x7ffa723350b0) at st_client.c:536
No locals.
#7 0x7ffa6f999f2d in stonith_action_destroy (action=0x7ffa723350b0) at
st_client.c:557
No locals.
#8 0x7ffa6fde7cd9 in child_waitpid (child=child@entry=0x7ffa7236bb20,
flags=flags@entry=1) at mainloop.c:948
rc = optimized out
core = optimized out
signo = 0
status = 0
exitcode = 0
__func__ = child_waitpid
#9 0x7ffa6fde7fce in child_death_dispatch (signal=optimized out) at
mainloop.c:962
saved = 0x0
child = 0x7ffa7236bb20
iter = 0x7ffa7222d200
exited = optimized out
__func__ = child_death_dispatch
#10 0x7ffa6fde6de7 in crm_signal_dispatch (source=0x7ffa7236ba50,
callback=optimized out, userdata=optimized out) at mainloop.c:275
__func__ = crm_signal_dispatch
#11 0x7ffa6ee84e04 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#12 0x7ffa6ee85048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#13 0x7ffa6ee8530a in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#14 0x7ffa702282a9 in main (argc=optimized out, argv=optimized out) at
main.c:1136
flag = optimized out
lpc = 0
argerr = optimized out
option_index = 0
cluster = {uuid = 0x7ffa7222fba0 167772162, uname = 0x7ffa72230280
kjp03, nodeid = 167772162, destroy = 0x7ffa70229b40
stonith_peer_cs_destroy, hb_conn = 0x0, hb_dispatch = 0x7ffa702299c0
stonith_peer_hb_callback, group = {length = 128, value = stonith-ng, '\000'
repeats 117 times}, cpg = {cpg_deliver_fn = 0x7ffa702298e0
stonith_peer_ais_callback, cpg_confchg_fn = 0x7ffa6fbb04a0
pcmk_cpg_membership}, cpg_handle = 7749363892505018368}
actions = {0x7ffa70236d7d reboot, 0x7ffa70236d84 off,
0x7ffa7023893f list, 0x7ffa70236d88 monitor, 0x7ffa70236d90 status}
__func__ = main
I also attach the crash report
Peter
** Attachment added: _usr_lib_pacemaker_stonithd.0.crash
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4293914/+files/_usr_lib_pacemaker_stonithd.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Could you provide your cluster configuration (cib file with configured stonith resources and parameters) and all packages versions (dpkg -l) ? I'll try to reproduce what you are facing.. tks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Could you provide your cluster configuration (cib file with configured stonith resources and parameters) and all packages versions (dpkg -l) ? I'll try to reproduce what you are facing.. tks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
The cluster consists of 2 HP ProLiant DL120 G7 Rack-Server as file server with DRBD and Samba. I used the same configuration with 12.04 for 2 years without any problems. The cluster configuration: node $id=167772161 kjp02 \ attributes standby=off node $id=167772162 kjp03 \ attributes standby=off primitive drbd ocf:linbit:drbd \ params drbd_resource=srv \ op monitor interval=29 role=Master \ op monitor interval=31 role=Slave primitive ip ocf:heartbeat:IPaddr2 \ params ip=161.42.184.40 \ op monitor interval=30 \ meta target-role=Started primitive mail ocf:heartbeat:MailTo \ params email=root \ meta target-role=Started primitive nmb upstart:nmbd \ op monitor interval=60 \ meta target-role=Started primitive quota lsb:quota \ op monitor interval=60 \ op start timeout=300 interval=0 \ meta target-role=Started primitive smb upstart:smbd \ op monitor interval=60 \ meta target-role=Started primitive srv ocf:heartbeat:Filesystem \ op monitor interval=60 \ params device=/dev/drbd0 directory=/srv fstype=ext4 options=noatime,acl,usrquota,user_xattr \ meta target-role=Started primitive st_kjp02 stonith:external/ipmi \ params hostname=kjp02 ipaddr=161.42.184.42 userid=Administrator passwd=*** interface=lanplus \ op monitor interval=120 primitive st_kjp03 stonith:external/ipmi \ params hostname=kjp03 ipaddr=161.42.184.44 userid=Administrator passwd=*** interface=lanplus \ op monitor interval=120 primitive winbind upstart:winbind \ op monitor interval=60 \ meta target-role=Started ms drbd_ms drbd \ meta master-max=1 master-node-max=1 clone-max=2 clone-node-max=1 notify=true location st_kjp02_loc st_kjp02 -inf: kjp02 location st_kjp03_loc st_kjp03 -inf: kjp03 colocation ip_srv inf: ip srv colocation mail_ip inf: mail ip colocation nmb_ip inf: nmb ip colocation quota_srv inf: quota srv colocation smb_winbind inf: smb winbind colocation srv_drbd inf: srv drbd_ms:Master colocation winbind_ip inf: winbind ip order drbd_srv inf: drbd_ms:promote srv:start order ip_mail inf: ip mail order ip_nmb inf: ip nmb order ip_winbind inf: ip winbind order srv_ip inf: srv:start ip order srv_quota inf: srv:start quota order winbind_smb inf: winbind smb property $id=cib-bootstrap-options \ dc-version=1.1.10-42f2063 \ cluster-infrastructure=corosync \ no-quorum-policy=ignore \ last-lrm-refresh=1416995137 dpkg versions are attached. Peter ** Attachment added: dpkg-versions https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4294035/+files/dpkg-versions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
The cluster consists of 2 HP ProLiant DL120 G7 Rack-Server as file server with DRBD and Samba. I used the same configuration with 12.04 for 2 years without any problems. The cluster configuration: node $id=167772161 kjp02 \ attributes standby=off node $id=167772162 kjp03 \ attributes standby=off primitive drbd ocf:linbit:drbd \ params drbd_resource=srv \ op monitor interval=29 role=Master \ op monitor interval=31 role=Slave primitive ip ocf:heartbeat:IPaddr2 \ params ip=161.42.184.40 \ op monitor interval=30 \ meta target-role=Started primitive mail ocf:heartbeat:MailTo \ params email=root \ meta target-role=Started primitive nmb upstart:nmbd \ op monitor interval=60 \ meta target-role=Started primitive quota lsb:quota \ op monitor interval=60 \ op start timeout=300 interval=0 \ meta target-role=Started primitive smb upstart:smbd \ op monitor interval=60 \ meta target-role=Started primitive srv ocf:heartbeat:Filesystem \ op monitor interval=60 \ params device=/dev/drbd0 directory=/srv fstype=ext4 options=noatime,acl,usrquota,user_xattr \ meta target-role=Started primitive st_kjp02 stonith:external/ipmi \ params hostname=kjp02 ipaddr=161.42.184.42 userid=Administrator passwd=*** interface=lanplus \ op monitor interval=120 primitive st_kjp03 stonith:external/ipmi \ params hostname=kjp03 ipaddr=161.42.184.44 userid=Administrator passwd=*** interface=lanplus \ op monitor interval=120 primitive winbind upstart:winbind \ op monitor interval=60 \ meta target-role=Started ms drbd_ms drbd \ meta master-max=1 master-node-max=1 clone-max=2 clone-node-max=1 notify=true location st_kjp02_loc st_kjp02 -inf: kjp02 location st_kjp03_loc st_kjp03 -inf: kjp03 colocation ip_srv inf: ip srv colocation mail_ip inf: mail ip colocation nmb_ip inf: nmb ip colocation quota_srv inf: quota srv colocation smb_winbind inf: smb winbind colocation srv_drbd inf: srv drbd_ms:Master colocation winbind_ip inf: winbind ip order drbd_srv inf: drbd_ms:promote srv:start order ip_mail inf: ip mail order ip_nmb inf: ip nmb order ip_winbind inf: ip winbind order srv_ip inf: srv:start ip order srv_quota inf: srv:start quota order winbind_smb inf: winbind smb property $id=cib-bootstrap-options \ dc-version=1.1.10-42f2063 \ cluster-infrastructure=corosync \ no-quorum-policy=ignore \ last-lrm-refresh=1416995137 dpkg versions are attached. Peter ** Attachment added: dpkg-versions https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4294035/+files/dpkg-versions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Per comment #10: Those error messages from glib (not being able to remove the resource), that are still there : Oct 31 00:30:20 [2054] clustertrusty03 stonith-ng: error: crm_abort: crm_glib_handler: Forked child 2 197 to record non-fatal assert at logging.c:63 : Source ID 15 was not found when attempting to remove it Can be interpreted as normal and non-fatal. Upstream discussion (explaining behavior, fix and error messages) can be found here: http://oss.clusterlabs.org/pipermail/pacemaker/2014-October/thread.html#22690 If you, together with error messages (non fatal and expected on some conditions like the ones we can trigger here with this testcase) face a crash, please attach the crash report to this case. Thank you very much Best Regards Rafael Tinoco -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Per comment #10: Those error messages from glib (not being able to remove the resource), that are still there : Oct 31 00:30:20 [2054] clustertrusty03 stonith-ng: error: crm_abort: crm_glib_handler: Forked child 2 197 to record non-fatal assert at logging.c:63 : Source ID 15 was not found when attempting to remove it Can be interpreted as normal and non-fatal. Upstream discussion (explaining behavior, fix and error messages) can be found here: http://oss.clusterlabs.org/pipermail/pacemaker/2014-October/thread.html#22690 If you, together with error messages (non fatal and expected on some conditions like the ones we can trigger here with this testcase) face a crash, please attach the crash report to this case. Thank you very much Best Regards Rafael Tinoco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Hi Brian, this fix did not solve the bug for me. I still get the following error message every 2 minutes: Jan 7 08:28:25 kjp02 stonith-ng[1868]:error: crm_abort: crm_glib_handler: Forked child 4647 to record non-fatal assert at logging.c:63 : Source ID 28 was not found when attempting to remove it Since it is an production system I can not play with crm standby/online, but I suspect that it will crash again as it did before, because this error was the cause for all previous crashes. I use 14.04.1 amd64, 3.13.0-43-generic # apt-cache policy pacemaker pacemaker: Installiert: 1.1.10+git20130802-1ubuntu2.2 Installationskandidat: 1.1.10+git20130802-1ubuntu2.2 Versionstabelle: *** 1.1.10+git20130802-1ubuntu2.2 0 400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.1.10+git20130802-1ubuntu2.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 1.1.10+git20130802-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Peter -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Hi Brian, this fix did not solve the bug for me. I still get the following error message every 2 minutes: Jan 7 08:28:25 kjp02 stonith-ng[1868]:error: crm_abort: crm_glib_handler: Forked child 4647 to record non-fatal assert at logging.c:63 : Source ID 28 was not found when attempting to remove it Since it is an production system I can not play with crm standby/online, but I suspect that it will crash again as it did before, because this error was the cause for all previous crashes. I use 14.04.1 amd64, 3.13.0-43-generic # apt-cache policy pacemaker pacemaker: Installiert: 1.1.10+git20130802-1ubuntu2.2 Installationskandidat: 1.1.10+git20130802-1ubuntu2.2 Versionstabelle: *** 1.1.10+git20130802-1ubuntu2.2 0 400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.1.10+git20130802-1ubuntu2.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 1.1.10+git20130802-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Peter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Also affects: pacemaker (Ubuntu Vivid) Importance: Undecided Assignee: Rafael David Tinoco (inaddy) Status: In Progress ** Also affects: pacemaker (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Utopic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Changed in: pacemaker (Ubuntu Vivid) Importance: Undecided = High ** Changed in: pacemaker (Ubuntu Utopic) Importance: Undecided = High ** Changed in: pacemaker (Ubuntu Trusty) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Branch linked: lp:ubuntu/vivid-proposed/pacemaker -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
This bug was fixed in the package pacemaker - 1.1.11-1ubuntu1 --- pacemaker (1.1.11-1ubuntu1) vivid; urgency=medium * Merge from Debian experimental, remaining changes: - d/control: Build-Depends on libcfg-dev. - Corosync's pacemaker plugin is disabled, hence not built: + d/libcrmcluster4-dev.install: Do not install plugin.h. + d/pacemaker.install,rules: Do not install pacemaker.lcrso. - Cherry picked fixes from upstream VCS: + Fix: services: Do not allow duplicate recurring op entries + High: lrmd: Merge duplicate recurring monitor operations + Fix: lrmd: Cancel recurring operations before stop action is executed - d/p/*: Refreshed. * Dropped changes, included in Debian: - d/control: Depend on libheartbeat2. * d/control: Ensure that pacemaker binary package uses matched binary versions of pacemaker libraries, avoiding upgrade problems (LP: #1382842). * d/p/Fix-lrmd-Prevent-glib-assert-triggered-by-timers-being.patch: Prevent glib assert triggered by timers being removed from mainloop more than once, cherry picked from upstream VCS (LP: #1368737). * d/control,compat,rules: Bump debhelper compat level to 9, drop use of hardening-wrapper. * d/control: Bumped Standards-Version, no changes. pacemaker (1.1.11-1) experimental; urgency=medium * New upstream release * debian/patches/series: Disable 5 patches added for the last release as these are included in the upstream source now * debian/control: Bump Standards-Version -- James Page james.p...@ubuntu.com Thu, 18 Dec 2014 10:26:17 + ** Changed in: pacemaker (Ubuntu Vivid) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Branch linked: lp:ubuntu/pacemaker -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
utopic and trusty fixes uploaded for sru team review. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Hello Rafael, or anyone else affected, Accepted pacemaker into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pacemaker/1.1.10+git20130802-1ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: pacemaker (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed ** Changed in: pacemaker (Ubuntu Utopic) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Branch linked: lp:ubuntu/trusty-proposed/pacemaker ** Branch linked: lp:ubuntu/utopic-proposed/pacemaker -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Also affects: pacemaker (Ubuntu Vivid) Importance: Undecided Assignee: Rafael David Tinoco (inaddy) Status: In Progress ** Also affects: pacemaker (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Utopic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Changed in: pacemaker (Ubuntu Vivid) Importance: Undecided = High ** Changed in: pacemaker (Ubuntu Utopic) Importance: Undecided = High ** Changed in: pacemaker (Ubuntu Trusty) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Branch linked: lp:ubuntu/vivid-proposed/pacemaker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
This bug was fixed in the package pacemaker - 1.1.11-1ubuntu1 --- pacemaker (1.1.11-1ubuntu1) vivid; urgency=medium * Merge from Debian experimental, remaining changes: - d/control: Build-Depends on libcfg-dev. - Corosync's pacemaker plugin is disabled, hence not built: + d/libcrmcluster4-dev.install: Do not install plugin.h. + d/pacemaker.install,rules: Do not install pacemaker.lcrso. - Cherry picked fixes from upstream VCS: + Fix: services: Do not allow duplicate recurring op entries + High: lrmd: Merge duplicate recurring monitor operations + Fix: lrmd: Cancel recurring operations before stop action is executed - d/p/*: Refreshed. * Dropped changes, included in Debian: - d/control: Depend on libheartbeat2. * d/control: Ensure that pacemaker binary package uses matched binary versions of pacemaker libraries, avoiding upgrade problems (LP: #1382842). * d/p/Fix-lrmd-Prevent-glib-assert-triggered-by-timers-being.patch: Prevent glib assert triggered by timers being removed from mainloop more than once, cherry picked from upstream VCS (LP: #1368737). * d/control,compat,rules: Bump debhelper compat level to 9, drop use of hardening-wrapper. * d/control: Bumped Standards-Version, no changes. pacemaker (1.1.11-1) experimental; urgency=medium * New upstream release * debian/patches/series: Disable 5 patches added for the last release as these are included in the upstream source now * debian/control: Bump Standards-Version -- James Page james.p...@ubuntu.com Thu, 18 Dec 2014 10:26:17 + ** Changed in: pacemaker (Ubuntu Vivid) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Branch linked: lp:ubuntu/pacemaker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
utopic and trusty fixes uploaded for sru team review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Hello Rafael, or anyone else affected, Accepted pacemaker into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pacemaker/1.1.10+git20130802-1ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: pacemaker (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed ** Changed in: pacemaker (Ubuntu Utopic) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Branch linked: lp:ubuntu/trusty-proposed/pacemaker ** Branch linked: lp:ubuntu/utopic-proposed/pacemaker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
It looks like the format chosen for SRU for this package :
pacemaker (1.1.10+git20130802-1ubuntu2.1) trusty
pacemaker (1.1.10+git20130802-1ubuntu2) trusty
pacemaker (1.1.10+git20130802-1ubuntu1) saucy
makes dh helpers not to calculate shlibs version properly:
$ fakeroot dh_makeshlibs -a -V
$ find . | grep shlib
./debian/libcrmcommon3/DEBIAN/shlibs
./debian/libpengine4/DEBIAN/shlibs
./debian/libpe-status4/DEBIAN/shlibs
./debian/libcrmservice1/DEBIAN/shlibs
./debian/libtransitioner2/DEBIAN/shlibs
./debian/libcib3/DEBIAN/shlibs
./debian/libpe-rules2/DEBIAN/shlibs
./debian/libcrmcluster4/DEBIAN/shlibs
./debian/libstonithd2/DEBIAN/shlibs
./debian/liblrmd1/DEBIAN/shlibs
$ cat ./debian/libcib3/DEBIAN/shlibs
libcib 3 libcib3 (= 1.1.10+git20130802)
When the requested version, considering the following line in
debian/control:
Package: pacemaker
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, ...
Should be:
libcib 3 libcib3 (= 1.1.10+git20130802-1ubuntu2.2).
I'm fixing this problem together with this BUG so next pacemaker
upgrade can have its dependencies properly calculated.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
I recommend, if possible, Vivid to use 1.1.12 (from upstream) and to use a different versioning scheme. Asking for sponsorship. Thank you Rafael Tinoco -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Trusty fix. ** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2.debdiff https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4258483/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu2.2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
Utopic fix. ** Patch added: utopic_pacemaker_1.1.10+git20130802-4ubuntu4.debdiff https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4258484/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
The way this package's versioning was made makes the tool dh_makeshlibs (debian helper) not to append proper suffix to dependencies (using (= 1.1.10+git20130802) instead of (= 1.1.10+git20130802-1ubuntu2.1) for example). I changed debian/rules so the proper version is considered for dependencies: dh_makeshlibs -a -V dh_makeshlibs -plibcrmcommon3 -V libcrmcommon3 (= $(RELEASE)) dh_makeshlibs -plibpengine4 -V libpengine4 (= $(RELEASE)) dh_makeshlibs -plibpe-status4 -V libpe-status4 (= $(RELEASE)) dh_makeshlibs -plibcrmservice1 -V libcrmservice1 (= $(RELEASE)) dh_makeshlibs -plibtransitioner2 -V libtransitioner2 (= $(RELEASE)) dh_makeshlibs -plibcib3 -V libcib3 (= $(RELEASE)) dh_makeshlibs -plibpe-rules2 -V libpe-rules2 (= $(RELEASE)) dh_makeshlibs -plibcrmcluster4 -V libcrmcluster4 (= $(RELEASE)) dh_makeshlibs -plibstonithd2 -V libstonithd2 (= $(RELEASE)) dh_makeshlibs -pliblrmd1 -V liblrmd1 (= $(RELEASE)) And I recommend further releases not to use this versioning scheme, to guarantee dh_makeshlibs to work properly. Thank you Rafael Tinoco PS: attaching debdiffs in a few moments. ** Patch removed: trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2.debdiff https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249612/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu2.2.debdiff ** Patch removed: utopic_pacemaker_1.1.10+git20130802-4ubuntu4.debdiff https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249614/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
It looks like the format chosen for SRU for this package :
pacemaker (1.1.10+git20130802-1ubuntu2.1) trusty
pacemaker (1.1.10+git20130802-1ubuntu2) trusty
pacemaker (1.1.10+git20130802-1ubuntu1) saucy
makes dh helpers not to calculate shlibs version properly:
$ fakeroot dh_makeshlibs -a -V
$ find . | grep shlib
./debian/libcrmcommon3/DEBIAN/shlibs
./debian/libpengine4/DEBIAN/shlibs
./debian/libpe-status4/DEBIAN/shlibs
./debian/libcrmservice1/DEBIAN/shlibs
./debian/libtransitioner2/DEBIAN/shlibs
./debian/libcib3/DEBIAN/shlibs
./debian/libpe-rules2/DEBIAN/shlibs
./debian/libcrmcluster4/DEBIAN/shlibs
./debian/libstonithd2/DEBIAN/shlibs
./debian/liblrmd1/DEBIAN/shlibs
$ cat ./debian/libcib3/DEBIAN/shlibs
libcib 3 libcib3 (= 1.1.10+git20130802)
When the requested version, considering the following line in
debian/control:
Package: pacemaker
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, ...
Should be:
libcib 3 libcib3 (= 1.1.10+git20130802-1ubuntu2.2).
I'm fixing this problem together with this BUG so next pacemaker
upgrade can have its dependencies properly calculated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Utopic fix. ** Patch added: utopic_pacemaker_1.1.10+git20130802-4ubuntu4.debdiff https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4258484/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
I recommend, if possible, Vivid to use 1.1.12 (from upstream) and to use a different versioning scheme. Asking for sponsorship. Thank you Rafael Tinoco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
Trusty fix. ** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2.debdiff https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4258483/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu2.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
The way this package's versioning was made makes the tool dh_makeshlibs (debian helper) not to append proper suffix to dependencies (using (= 1.1.10+git20130802) instead of (= 1.1.10+git20130802-1ubuntu2.1) for example). I changed debian/rules so the proper version is considered for dependencies: dh_makeshlibs -a -V dh_makeshlibs -plibcrmcommon3 -V libcrmcommon3 (= $(RELEASE)) dh_makeshlibs -plibpengine4 -V libpengine4 (= $(RELEASE)) dh_makeshlibs -plibpe-status4 -V libpe-status4 (= $(RELEASE)) dh_makeshlibs -plibcrmservice1 -V libcrmservice1 (= $(RELEASE)) dh_makeshlibs -plibtransitioner2 -V libtransitioner2 (= $(RELEASE)) dh_makeshlibs -plibcib3 -V libcib3 (= $(RELEASE)) dh_makeshlibs -plibpe-rules2 -V libpe-rules2 (= $(RELEASE)) dh_makeshlibs -plibcrmcluster4 -V libcrmcluster4 (= $(RELEASE)) dh_makeshlibs -plibstonithd2 -V libstonithd2 (= $(RELEASE)) dh_makeshlibs -pliblrmd1 -V liblrmd1 (= $(RELEASE)) And I recommend further releases not to use this versioning scheme, to guarantee dh_makeshlibs to work properly. Thank you Rafael Tinoco PS: attaching debdiffs in a few moments. ** Patch removed: trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2.debdiff https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249612/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu2.2.debdiff ** Patch removed: utopic_pacemaker_1.1.10+git20130802-4ubuntu4.debdiff https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249614/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Summary changed: - Pacemaker can seg fault on crm node online/standy + Pacemaker can seg fault on crm node online/standby -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+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 1368737] Re: Pacemaker can seg fault on crm node online/standby
** Summary changed: - Pacemaker can seg fault on crm node online/standy + Pacemaker can seg fault on crm node online/standby -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368737 Title: Pacemaker can seg fault on crm node online/standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
