Heya, that's the output I get from gdb:
r...@samarqand:~# gdb corosync GNU gdb (GDB) 7.0.1-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/corosync...(no debugging symbols found)...done. (gdb) run -f Starting program: /usr/sbin/corosync -f [Thread debugging using libthread_db enabled] [New Thread 0x7ffff542b710 (LWP 16503)] [New Thread 0x7ffff7ff7db0 (LWP 16504)] [New Thread 0x7ffff4c2a710 (LWP 16505)] Nov 25 08:07:21 corosync [MAIN ] main.c:1300 Corosync Cluster Engine ('1.2.1'): started and ready to provide service. Nov 25 08:07:21 corosync [MAIN ] main.c:1301 Corosync built-in features: nss rdma Nov 25 08:07:21 corosync [MAIN ] main.c:1376 Successfully read main configuration file '/etc/corosync/corosync.conf'. Nov 25 08:07:21 corosync [TOTEM ] totemnet.c:204 Initializing transport (Infiniband/IP). Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7bcdc0a in ?? () from /usr/lib/libtotem_pg.so.4 (gdb) thr a a bt Thread 4 (Thread 0x7ffff4c2a710 (LWP 16505)): #0 0x00007ffff738c330 in sem_wait () from /lib/libpthread.so.0 #1 0x0000000000406ce0 in ?? () #2 0x00007ffff73858ba in start_thread () from /lib/libpthread.so.0 #3 0x00007ffff6ee902d in clone () from /lib/libc.so.6 #4 0x0000000000000000 in ?? () Thread 3 (Thread 0x7ffff7ff7db0 (LWP 16504)): #0 0x00007ffff6ede113 in poll () from /lib/libc.so.6 #1 0x000000000040918e in ?? () #2 0x00007ffff73858ba in start_thread () from /lib/libpthread.so.0 #3 0x00007ffff6ee902d in clone () from /lib/libc.so.6 #4 0x0000000000000000 in ?? () Thread 2 (Thread 0x7ffff542b710 (LWP 16503)): #0 0x00007ffff738a16c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x00007ffff79acd38 in ?? () from /usr/lib/liblogsys.so.4 #2 0x00007ffff73858ba in start_thread () from /lib/libpthread.so.0 #3 0x00007ffff6ee902d in clone () from /lib/libc.so.6 #4 0x0000000000000000 in ?? () Thread 1 (Thread 0x7ffff7fd0700 (LWP 16500)): #0 0x00007ffff7bcdc0a in ?? () from /usr/lib/libtotem_pg.so.4 #1 0x00007ffff7bb6e99 in poll_run () from /usr/lib/libtotem_pg.so.4 #2 0x0000000000405c24 in main () The segfault doesn't happen when using IPv4 on the same device. But I have some other issues there. Cheers, Christine On 25/11/10 00:16, Angus Salkeld wrote: > On Wed, Nov 24, 2010 at 08:43:00PM +0100, pebcak wrote: >> Heya all, >> >> I have a problem with corosync via iba& ipv6. >> >> I want to build a storage cluster (sheepdog) with corosync while using >> infiniband. However when I use "transport: iba" I get a segmentation >> fault when starting corosync > > (sounds like a bug) > > Can you get a backtrace? > gdb corosync > run -f > # after segfault > thr a a bt > > Thanks > Angus > >> >> I took the source from the debian-packages and rebuild them with >> --enable-rdma. >> >> -- >> >> corosync [MAIN ] main.c:1300 Corosync Cluster Engine ('1.2.1'): started >> and ready to provide service. >> corosync [MAIN ] main.c:1301 Corosync built-in features: nss rdma >> >> -- >> >> The relevant part of my config looks like this: >> >> -- >> transport: iba >> interface { >> ringnumber: 0 >> bindnetaddr: 2a02:2478:0:1:218:f104:396:e131 >> mcastport: 5405 >> mcastaddr: ff04::1 >> } >> -- >> >> And that's what I get when start it: >> >> -- >> >> r...@caspar:~# corosync -f >> corosync [MAIN ] main.c:1300 Corosync Cluster Engine ('1.2.1'): started >> and ready to provide service. >> corosync [MAIN ] main.c:1301 Corosync built-in features: nss rdma >> corosync [MAIN ] main.c:1376 Successfully read main configuration file >> '/etc/corosync/corosync.conf'. >> corosync [TOTEM ] totemnet.c:204 Initializing transport (Infiniband/IP). >> Segmentation fault >> >> -- >> >> Everything works fine when I change transport to udp, using the same >> device and config. >> >> Did I forget or overlook something? >> >> Cheers, >> Christine >> >> _______________________________________________ >> Openais mailing list >> [email protected] >> https://lists.linux-foundation.org/mailman/listinfo/openais > _______________________________________________ > Openais mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/openais _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
