Andrey, what version of corosync and libqb are you using? Can you please attach output from valgrind (and gdb backtrace)?
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 > disc...@corosync.org > http://lists.corosync.org/mailman/listinfo/discuss > _______________________________________________ Pacemaker mailing list: Pacemaker@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