I am facing core dump issue with corosync-1.4.2 cluster-glue-1.0.7 pacemaker-1.0.11 In many scenario I getting core dump during corosync start operation for 2 rings like. 1. Configure 2 rings ring0 10.16.16.0, ring1 192.168.1.0 ring1 network(ifconfig eth1 192.168.1.14 down) is down before corosync startup 2. Configure 2 rings ring0 10.16.16.0, ring1 192.168.1.0(invalid network) ring1 network(ifconfig eth1 193.167.1.14 up) is different. means network is not present for ring1. start corosync All the core dump are generated from the same files. core was generated by 'corosync' programme terminate with signal 6 C File where problem encountered totemsrp.c.2526 totemsrp.c.3545 totemrrp.c.1036 totemrrp.c.1736 totemudp.c.1252 coropoll.c.513 main.c.1846 With corosync1.2 also we are facing core dump issue. Is there any way, to avoid only corosync core dump. _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
