Hi, On Wed, Oct 19, 2011 at 8:12 AM, <manish.gu...@ionidea.com> wrote: > thank you > Andreas > > Now I am facing core dump issue with > corosync-1.4.2 > cluster-glue-1.0.7 > pacemaker-1.0.11 >
To report a crash of corosync, please follow this guide => http://corosync.org/doku.php?id=faq:crash Regards, Dan > 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. > > On Tue, October 18, 2011 2:05 pm, Andreas Kurz wrote: >> Hello, >> >> >> On 10/18/2011 08:11 AM, manish.gu...@ionidea.com wrote: >> >>> Hi, >>> >>> >>> I am using corosync.1.2.1. I want to upgrade corosync from 1.2 to >>> 1.4.2. >>> >>> >>> >>> please can you let me know which version of cluster-glue and pacemekr >>> are compatiable with corosync1.4.2 >>> >>> Currentely with corosync1.4.2 I am using pacemaker 1.0.10 and >>> cluster-glue1.0.3 and I am getting error .. >> >> You should also upgrade Pacemaker to 1.0.11 and especially cluster-glue >> to latest version 1.0.7 ... though this old versions might not be the cause >> for your problems here. >> >>> >>> service failed to load pacemaker ... >> >> Hard to say without having a look at your corosync configuration. >> >> >> Regards, >> Andreas >> >> >> -- >> Need help with Pacemaker? >> http://www.hastexo.com/now >> >> >>> >>> >>> Regards >>> Manish >>> >>> >>> >>> _______________________________________________ >>> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemak >>> er >> >> >> >> _______________________________________________ >> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >> >> > > > > _______________________________________________ > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > -- Dan Frincu CCNA, RHCE _______________________________________________ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
