On Mon, Jul 26, 2010 at 7:08 PM, Guillaume Chanaud <guillaume.chan...@connecting-nature.com> wrote: > Le 26/07/2010 14:38, Andrew Beekhof a écrit : >> >> On Fri, Jul 16, 2010 at 5:44 PM, Guillaume Chanaud >> <guillaume.chan...@connecting-nature.com> wrote: >>> >>> Hello, >> >> [snip] >> >>> # Optionally assign a fixed node id (integer) >>> nodeid: 30283707487 >> >> In addition to changing the node's ip address, did you change this too? >> > Yes, as i said in the mail i changed the nodeid and bindnetaddress for each > node. Even non fixed values doesn't work. >> >> Looks like corosync crashed. Possibly related to the duplicate nodeid? >> Was there a core file in /var/run/corosync? >> what does "ulimit -c" say? > > There is a /var/run/corosync.pid (whith the correct pid) which stay there > even after the corosync crash. > For ulimit : > [r...@www01 run]# ulimit -c > 0 > > These values are the same on the second node running fine (and if i stop > this second node, the first node will run fine, but not the second...)
Yes, but that doesn't help us find out why the first one is crashing. Please run "ulimit -c unlimited" before starting corosync so that we can get a core file and stack trace. _______________________________________________ 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
