[Pacemaker] [corosync] corosync Segmentation fault.

Andrey Groshev greenx at yandex.ru
Wed Feb 26 10:47:28 UTC 2014



26.02.2014, 12:11, "Jan Friesse" <jfriesse at redhat.com>:
> Andrey,
> what version of corosync and libqb are you using?
>
> Can you please attach output from valgrind (and gdb backtrace)?
,,,,,,,,,,,
1314            qb_loop_run (corosync_poll_handle);
(gdb) n

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff71e581c in free () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff71e581c in free () from /lib64/libc.so.6
#1  0x00007ffff7fe77ec in votequorum_readconfig (runtime=<value optimized out>) at votequorum.c:1293
#2  0x00007ffff7fe8300 in votequorum_exec_init_fn (api=<value optimized out>) at votequorum.c:2115
#3  0x00007ffff7feeb7b in corosync_service_link_and_init (corosync_api=0x7ffff8200980, service=0x7ffff8200760) at service.c:139
#4  0x00007ffff7fe4197 in votequorum_init (api=0x7ffff8200980, q_set_quorate_fn=0x7ffff7fda5b0 <quorum_api_set_quorum>) at votequorum.c:2255
#5  0x00007ffff7fda42f in quorum_exec_init_fn (api=0x7ffff8200980) at vsf_quorum.c:280
#6  0x00007ffff7feeb7b in corosync_service_link_and_init (corosync_api=0x7ffff8200980, service=0x7ffff8200c40) at service.c:139
#7  0x00007ffff7feede9 in corosync_service_defaults_link_and_init (corosync_api=0x7ffff8200980) at service.c:348
#8  0x00007ffff7fe9621 in main_service_ready () at main.c:978
#9  0x00007ffff7b90b0f in main_iface_change_fn (context=0x7ffff7f73010, iface_addr=<value optimized out>, iface_no=0) at totemsrp.c:4672
#10 0x00007ffff7b8a734 in timer_function_netif_check_timeout (data=0x7ffff8304f10) at totemudp.c:672
#11 0x00007ffff77289f8 in ?? () from /usr/lib64/libqb.so.0
#12 0x00007ffff7727016 in qb_loop_run () from /usr/lib64/libqb.so.0
#13 0x00007ffff7fea930 in main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at main.c:1314

Unfortunately, I have not yet used a valgrind. 
Or "hangs", or fast end with :

# valgrind /usr/sbin/corosync -f
==2137== Memcheck, a memory error detector
==2137== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==2137== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==2137== Command: /usr/sbin/corosync -f
==2137== 
==2137== 
==2137== HEAP SUMMARY:
==2137==     in use at exit: 29,876 bytes in 193 blocks
==2137==   total heap usage: 890 allocs, 697 frees, 100,824 bytes allocated
==2137== 
==2137== LEAK SUMMARY:
==2137==    definitely lost: 0 bytes in 0 blocks
==2137==    indirectly lost: 0 bytes in 0 blocks
==2137==      possibly lost: 539 bytes in 22 blocks
==2137==    still reachable: 29,337 bytes in 171 blocks
==2137==         suppressed: 0 bytes in 0 blocks
==2137== Rerun with --leak-check=full to see details of leaked memory
==2137== 
==2137== For counts of detected and suppressed errors, rerun with: -v
==2137== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 12 from 6)

Now read manual about valgrind.

>
> Thanks,
>   Honza
>
> Andrey Groshev napsal(a):
>
>>  Hi, ALL.
>>  Something I already confused, or after updating any package or myself something broke,
>>  but call corosycn killed by segmentation fault signal.
>>  I correctly understood that does not link the library libqb ?
>>
>>  .....
>>
>>  (gdb) n
>>  [New Thread 0x7ffff4b2b700 (LWP 9014)]
>>  1266            if ((flock_err = corosync_flock (corosync_lock_file, getpid ())) != COROSYNC_DONE_EXIT) {
>>  (gdb) n
>>  1280            totempg_initialize (
>>  (gdb) n
>>  1284            totempg_service_ready_register (
>>  (gdb) n
>>  1287            totempg_groups_initialize (
>>  (gdb) n
>>  1292            totempg_groups_join (
>>  (gdb) n
>>  1307            schedwrk_init (
>>  (gdb) n
>>  1314            qb_loop_run (corosync_poll_handle);
>>  (gdb) n
>>
>>  Program received signal SIGSEGV, Segmentation fault.
>>  0x00007ffff71e581c in free () from /lib64/libc.so.6
>>  (gdb)
>>  _______________________________________________
>>  discuss mailing list
>>  discuss at corosync.org
>>  http://lists.corosync.org/mailman/listinfo/discuss




More information about the Pacemaker mailing list