[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standy

2014-11-10 Thread Rafael David Tinoco
Considering bug:

https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1382842

I'll have to fix dependencies together with this SRU.

Please hold while I fix this new debdiff (for this case), fixing lib
dependencies for pacemaker to be upgraded.

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/standy

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/standy

2014-10-31 Thread Rafael David Tinoco
** Description changed:

+ [IMPACT]
+ 
+   - Pacemaker seg fault on repeated crm node online/standy because:
+   - Newer glib versions uses hash_table to find GSources
+   - Glib can try to assert source being removed multiple times
+ 
+ [TEST CASE]
+ 
+   - Using same configuration as attached cib.xml :
+ 
+ #!/bin/bash
+ 
+ while true; do
+ crm node standby clustertrusty01
+ sleep 7
+ crm node online clustertrusty01
+ sleep 7
+ crm node standby clustertrusty02
+ sleep 7
+ crm node online clustertrusty02
+ sleep 7
+ crm node standby clustertrusty03
+ sleep 7
+ crm node online clustertrusty03
+ sleep 7
+ done
+ 
+ [REGRESSION POTENTIAL]
+ 
+   - Based on upstream commit 568e41d
+   - Test case ran for more than 7 hours with no problems
+ 
+ [OTHER INFO]
+ 
  It was brought to my attention the following situation:
  
  """
- [Issue] 
+ [Issue]
  
  lrmd process crashed when repeating "crm node standby" and "crm node
  online"
  
-  
- # grep pacemakerd ha-log.k1pm101 | grep core 
- Aug 27 17:47:06 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 49275 (lrmd) dumped core 
- Aug 27 17:47:06 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=49275, core=1) 
- Aug 27 18:27:14 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 1471 (lrmd) dumped core 
- Aug 27 18:27:14 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=1471, core=1) 
- Aug 27 18:56:41 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 35771 (lrmd) dumped core 
- Aug 27 18:56:41 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=35771, core=1) 
- Aug 27 19:44:09 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 60709 (lrmd) dumped core 
- Aug 27 19:44:09 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=60709, core=1) 
- Aug 27 20:00:53 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 35838 (lrmd) dumped core 
- Aug 27 20:00:53 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=35838, core=1) 
- Aug 27 21:33:52 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 49249 (lrmd) dumped core 
- Aug 27 21:33:52 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=49249, core=1) 
- Aug 27 22:01:16 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 65358 (lrmd) dumped core 
- Aug 27 22:01:16 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=65358, core=1) 
- Aug 27 22:28:02 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 22693 (lrmd) dumped core 
- Aug 27 22:28:02 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=22693, core=1) 
-  
+ 
+ # grep pacemakerd ha-log.k1pm101 | grep core
+ Aug 27 17:47:06 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 49275 (lrmd) dumped core
+ Aug 27 17:47:06 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=49275, core=1)
+ Aug 27 18:27:14 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 1471 (lrmd) dumped core
+ Aug 27 18:27:14 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=1471, core=1)
+ Aug 27 18:56:41 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 35771 (lrmd) dumped core
+ Aug 27 18:56:41 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=35771, core=1)
+ Aug 27 19:44:09 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 60709 (lrmd) dumped core
+ Aug 27 19:44:09 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=60709, core=1)
+ Aug 27 20:00:53 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 35838 (lrmd) dumped core
+ Aug 27 20:00:53 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=35838, core=1)
+ Aug 27 21:33:52 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 49249 (lrmd) dumped core
+ Aug 27 21:33:52 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=49249, core=1)
+ Aug 27 22:01:16 k1pm101 pacemakerd[49271]: error: child_waitpid: Managed 
process 65358 (lrmd) dumped core
+ Aug 27 22:01:16 k1pm101 pacemakerd[49271]: notice: pcmk_child_exit: Child 
process lrmd terminated with signal 11 (pid=65358, core=1)
+ Aug 27 22:28:02 k1pm101 pacemakerd[492

[Bug 1368737] Re: Pacemaker can seg fault on crm node online/standy

2014-10-30 Thread Rafael David Tinoco
I'm asking for sponsorship for this...

Meanwhile I have created one PPA to be used:

https://launchpad.net/~inaddy/+archive/ubuntu/lp1368737

# add-apt-repository ppa:inaddy/lp1368737 
# apt-get update 
# apt-get install pacemaker 

The right package version, for now, will be:

1.1.10+git20130802-1ubuntu2.2~lp1368737~1 (for Trusty) 
1.1.10+git20130802-4ubuntu4~lp1368737~1 (for Utopic) 

And they are going to be replaced by the appropriate version in case the 
stable release update proposal is accepted into -updates repository. 

Please provide me feedback regarding the fix (if it solved the problem 
for you). 

Thank you very much

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/standy

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/standy

2014-10-30 Thread Rafael David Tinoco
Vivid might also need a fix/update to proper handle this.

** Changed in: pacemaker (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/standy

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/standy

2014-10-30 Thread Rafael David Tinoco
Utopic Fix.

** Patch added: "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/standy

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/standy

2014-10-30 Thread Rafael David Tinoco
Running testcase for some time and couldn't get any core dump...

Services seem stable:

Every 1.0s: crm_mon -1
Fri Oct 31 00:52:57 2014

Last updated: Fri Oct 31 00:52:57 2014
Last change: Fri Oct 31 00:31:22 2014 via crm_attribute on clustertrusty04
Stack: corosync
Current DC: clustertrusty02 (12) - partition with quorum
Version: 1.1.10-42f2063
4 Nodes configured
6 Resources configured


Node clustertrusty02 (12): standby
Online: [ clustertrusty01 clustertrusty03 clustertrusty04 ]

 fenceclustertrusty01   (stonith:fence_virsh):  Started clustertrusty04
 fenceclustertrusty02   (stonith:fence_virsh):  Started clustertrusty03
 fenceclustertrusty03   (stonith:fence_virsh):  Started clustertrusty01
 fenceclustertrusty04   (stonith:fence_virsh):  Started clustertrusty01
 Resource Group: postfix
 vippostfix (ocf::heartbeat:IPaddr2):   Started clustertrusty01
 initpostfix(lsb:postfix):  Started clustertrusty01

At this time...

stonith_action_clear_tracking_data is calling g_source_remove and 
there are no problems, even when trying to remove an already
removed timer.

Judging by the developer comments on that:

"""
The glib behaviour on unbuntu seems reasonable, removing a source multiple 
times IS a valid error.
I need the stack trace to know where/how this situation can occur in pacemaker.
"""

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 2197 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".

-- 
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/standy

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/standy

2014-10-30 Thread Rafael David Tinoco
Trusty Fix.

** Patch added: "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

-- 
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/standy

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/standy

2014-10-30 Thread Rafael David Tinoco
Trusty is affected and Precise is NOT.

 libglib2.0-0 | 2.24.0-0ubuntu4 | lucid| amd64, armel, i386, ia64, 
powerpc, sparc
 libglib2.0-0 | 2.24.1-0ubuntu2 | lucid-updates| amd64, armel, i386, ia64, 
powerpc, sparc
 libglib2.0-0 | 2.32.1-0ubuntu2 | precise  | amd64, armel, armhf, i386, 
powerpc
 libglib2.0-0 | 2.32.4-0ubuntu1 | precise-updates  | amd64, armel, armhf, i386, 
powerpc
 libglib2.0-0 | 2.40.0-2| trusty   | amd64, arm64, armhf, i386, 
powerpc, ppc64el
 libglib2.0-0 | 2.40.2-0ubuntu1 | trusty-updates   | amd64, arm64, armhf, i386, 
powerpc, ppc64el
 libglib2.0-0 | 2.41.5-1| ubuntu-rtm/14.09 | amd64, armhf, i386
 libglib2.0-0 | 2.42.0-2| utopic   | amd64, arm64, armhf, i386, 
powerpc, ppc64el
 libglib2.0-0 | 2.42.0-2| vivid| amd64, arm64, armhf, i386, 
powerpc, ppc64el

since libglib2 started using the hashtable lookup in version 2.39.91 and 
precise is still
using libglib2 2.32.4.

-- 
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/standy

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/standy

2014-10-30 Thread Rafael David Tinoco
Analyzing the stacktrace for stonithd:

(gdb) bt
#0  0x7fed094febb9 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x7fed09501fc8 in __GI_abort () at abort.c:89
#2  0x7fed0a15a6c9 in crm_abort (file=0x7fed0a17e4bb "logging.c",
function=0x7fed0a17f790 <__PRETTY_FUNCTION__.22958> "crm_glib_handler", 
line=63,
assert_condition=0x7fed0af9f2c0 "Source ID 21 was not found when attempting 
to remove it",
do_core=, do_fork=) at utils.c:1118
#3  0x7fed0920fae1 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fed0920fd72 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fed09207c5c in g_source_remove () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fed09d23ef5 in stonith_action_clear_tracking_data 
(action=action@entry=0x7fed0afc6b00)
at st_client.c:536
#7  0x7fed09d23f2d in stonith_action_destroy (action=0x7fed0afc6b00) at 
st_client.c:557
#8  0x7fed0a172cd9 in child_waitpid (child=child@entry=0x7fed0afded70, 
flags=flags@entry=1)
at mainloop.c:948
#9  0x7fed0a172fce in child_death_dispatch (signal=) at 
mainloop.c:962
#10 0x7fed0a171de7 in crm_signal_dispatch (source=0x7fed0afb0920, 
callback=,
userdata=) at mainloop.c:275
#11 0x7fed09208e04 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7fed09209048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7fed0920930a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7fed0a5bd2a9 in main (argc=, argv=) at 
main.c:1136

Based on this stack trace:

crm_glib_handler ->  crm_abort -> abort

I could see one upstream fix that is exactly about this problem
(pacemaker mailing list):

http://oss.clusterlabs.org/pipermail/pacemaker/2014-October/022690.html

Explaining that this change (in glib):

https://github.com/GNOME/glib/commit/393503ba5bdc7c09cd46b716aaf3d2c63a6c7f9c
(seen first at version 2.39.91 - Trusty version is 2.40.2-0ubuntu1)

Caused g_source_remove() (frame #5 in the stacktrace, part of libglib) to 
misbehave. 
(glib is using a hash table lookup to find sources, and not an iterator.. and 
it is also 
returning NULL if source was destroyed)

corosync reports the following error on this occasions:

"""
lrmd[1632]:error: crm_abort: crm_glib_handler: Forked child 1840 to 
record non-fatal assert at logging.c:73 : Source ID 51 was not found when 
attempting to remove it
lrmd[1632]:crit: crm_glib_handler: GLib: Source ID 51 was not found 
when attempting to remove it
"""

this is happening because one resource is being removed twice and this
can't be done with newer libglibs.

the following upstream fix handle this problem:

>From 568e41db929a34106c8c2ff7c48716ab5c13ef49 Mon Sep 17 00:00:00 2001
From: Andrew Beekhof 
Date: Mon, 13 Oct 2014 13:30:58 +1100
Subject: [PATCH] Fix: lrmd: Prevent glib assert triggered by timers being 
removed from mainloop more than once
  
I'll be providing a PPA (soon) with this fix so I can get users/community 
feedback on the resolution. 

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/standy

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/standy

2014-10-30 Thread Rafael David Tinoco
Okay,

Finally I was able to reproduce the problem using:

#!/bin/bash

while true; do

crm node standby clustertrusty01
sleep 7
crm node online clustertrusty01
sleep 7

crm node standby clustertrusty02
sleep 7
crm node online clustertrusty02
sleep 7

crm node standby clustertrusty03
sleep 7
crm node online clustertrusty03
sleep 7

done

And the attached CIB (cib.xml).

 could generate the following crashes:

root@clustertrusty01:/var/crash# ls -lah -1 | grep usr 
-rw-r- 1 root root 257K Oct 30 01:18 _usr_lib_pacemaker_lrmd.0.crash 
-rw-r- 1 root root 434K Oct 30 01:18 _usr_lib_pacemaker_stonithd.0.crash 

root@clustertrusty02:/var/crash# ls -lah -1 | grep usr 
-rw-r- 1 root root 257K Oct 30 01:20 _usr_lib_pacemaker_lrmd.0.crash 
-rw-r- 1 root root 441K Oct 30 01:21 _usr_lib_pacemaker_stonithd.0.crash 

root@clustertrusty03:/var/crash# ls -lah -1 | grep usr 
-rw-r- 1 root root 258K Oct 30 01:21 _usr_lib_pacemaker_lrmd.0.crash 
-rw-r- 1 root root 434K Oct 30 01:18 _usr_lib_pacemaker_stonithd.0.crash 

root@clustertrusty04:/var/crash# ls -lah -1 | grep usr 
-rw-r- 1 root root 443K Oct 30 01:21 _usr_lib_pacemaker_stonithd.0.crash 


** Changed in: pacemaker (Ubuntu)
 Assignee: (unassigned) => Rafael David Tinoco (inaddy)

** Attachment added: "cib.xml"
   
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249543/+files/cib.xml

-- 
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/standy

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/standy

2014-10-10 Thread Jorge Niedbalski
** Tags added: cts

-- 
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/standy

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/standy

2014-09-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pacemaker (Ubuntu)
   Status: New => Confirmed

-- 
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/standy

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/standy

2014-09-25 Thread Nobuto MURATA
Also, I used an attached juju bundle to create the testbed.

** Attachment added: "keystone-ha-minimal.yaml"
   
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4215057/+files/keystone-ha-minimal.yaml

-- 
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/standy

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/standy

2014-09-25 Thread Nobuto MURATA
Hmm, I can get a crash file even with the PPA. I will upload a crash
file with retrace and procedure I tried. If you think it's an another
issue, I will open a new bug.

** Attachment added: "_usr_lib_pacemaker_lrmd.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4214469/+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/standy

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/standy

2014-09-25 Thread Nobuto MURATA
** Attachment added: "pacemaker-fix-segv-verification.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4214470/+files/pacemaker-fix-segv-verification.txt

-- 
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/standy

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/standy

2014-09-17 Thread Rafael David Tinoco
Based on my last comment, I have created one PPA for users to test and give us 
feedback for this specific case: 

https://launchpad.net/~inaddy/+archive/ubuntu/lp1368737

Instructions on how to use:

# add-apt-repository ppa:inaddy/lp1368737 
# apt-get update 
# apt-get install pacemaker 

This PPA contains both fixes:

Pacemaker: haproxy monitor NG 
Pacemaker: Pacemaker's lrmd process crashed. 

With the following changelog:

pacemaker (1.1.10+git20130802-1ubuntu4~lp1368737~1) trusty;
urgency=medium

* Fix: services: Prevent use-of-NULL when executing service actions - 1/2 (LP: 
#1368737) 
* Fix: services: Fix the executing of synchronous actions - 2/2 (LP: #1368737) 

-- Rafael David Tinoco  Fri, 12 Sep 2014
15:52:14 -0300

pacemaker (1.1.10+git20130802-1ubuntu3) trusty; urgency=medium

* Fix: services: Do not allow duplicate recurring op entries - 1/3 (LP: 
#1353473) 
* High: lrmd: Merge duplicate recurring monitor operations - 2/3 (LP: #1353473) 
* Fix: lrmd: Cancel recurring operations before stop action is executed - 3/3 
(LP: #1353473) 

-- Rafael David Tinoco  Wed, 06 Aug 2014
09:24:13 -0300

Since I was waiting for the Stable Release Update for pacemaker on Trusty but 
it did not 
get released until the date of this fix. 

If this fix solves the issue I'll push both SRUs (for 2 cases above) for our 
sponsor team 
to upload them for Trusty. 

Waiting on community feedback to request the Release Update.

Thank you in advance.

-- 
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/standy

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/standy

2014-09-12 Thread Rafael David Tinoco
There is already a Fix Released for Utopic:

https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1353473

And Trusty's fix is waiting to get released.

This way I'm working on the patch on the topic of another suggested SRU:

pacemaker (1.1.10+git20130802-1ubuntu3) trusty; urgency=medium

  * Fix: services: Do not allow duplicate recurring op entries - 1/3 (LP: 
#1353473)
  * High: lrmd: Merge duplicate recurring monitor operations - 2/3 (LP: 
#1353473)
  * Fix: lrmd: Cancel recurring operations before stop action is executed - 3/3 
(LP: #1353473)

 -- Rafael David Tinoco   Wed, 06 Aug 2014
09:24:13 -0300

-- 
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/standy

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