[Pacemaker] stonithd crash on exit

Jacek Konieczny jajcus at jajcus.net
Tue Oct 30 13:42:15 UTC 2012


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

Greets,
        Jacek




More information about the Pacemaker mailing list