[Pacemaker] stonithd crash on exit

[Andrew Beekhof]

On Thu, Nov 1, 2012 at 7:40 AM, Jacek Konieczny <jajcus at jajcus.net> wrote:
> On Wed, Oct 31, 2012 at 05:33:03PM +1100, Andrew Beekhof wrote:
>> I havent seen that before. What version?
>
> Pacemaker 1.1.8, corosync 2.1.0, cluster-glue 1.0.11

I think you want these two patches:

https://github.com/beekhof/pacemaker/commit/7282066
https://github.com/beekhof/pacemaker/commit/280926a

They came after the official release

>
>
>> On Wed, Oct 31, 2012 at 12:42 AM, Jacek Konieczny <jajcus at jajcus.net> wrote:
>> > Hello,
>> >
>> > Probably this is not a critical problem, but it become annoying during
>> > my cluster setup/testing time:
>> >
>> > Whenever I restart corosync with 'systemctl restart corosync.service' I
>> > get message about stonithd crashing with SIGSEGV:
>> >
>> >> stonithd[3179]: segfault at 10 ip 0000000000403144 sp 00007fffe83d6370 error 4 in stonithd (deleted)[400000+13000]
>> >> stonithd/3179: potentially unexpected fatal signal 11.
>> >
>> > GDB shows this:
>> >
>> >> Program received signal SIGTERM, Terminated.
>> >> 0x00007fd6ec319c18 in poll () from /lib64/libc.so.6
>> >> (gdb) signal SIGTERM
>> >> Continuing with signal SIGTERM.
>> >>
>> >> Program received signal SIGSEGV, Segmentation fault.
>> >> 0x0000000000403144 in main (argc=<optimized out>, argv=0x7fff4648f318)
>> >>     at main.c:933
>> >> 933             cluster.hb_conn->llc_ops->delete(cluster.hb_conn);
>> >> (gdb) bt
>> >> #0  0x0000000000403144 in main (argc=<optimized out>, argv=0x7fff4648f318)
>> >>     at main.c:933
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org