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
