Hello, Unfortunately I'm still waiting for a position on the server's RAM, as the server hardware is not managed by our team. I'll post as soon as I have more info on this issue. 2012/3/6 Andrew Beekhof <andrew@xxxxxxxxxxx>: > Did you ever resolve if this was a RAM issue afterall as suspected on irc? > > On Sun, Mar 4, 2012 at 1:57 PM, Diego Lima <lists@xxxxxxxxxxxxx> wrote: >>> What is different between the two? >>> Software? Hardware? >> >> Both are CentOS release 6.2 (Final), fully updated, with Pacemaker >> 1.1.6-3.el6 and Corosync Cluster Engine version 1.4.1. They're both >> identical machines running quad-core Intel Xeon processors and 4gb of >> RAM. >> The packages have been installed using distro packages through yum and >> default repos. >> >> The corosync.conf file is here: http://pastebin.com/KxuS3fyD >> Corosync-objctl from the first node (which is working fine) is here: >> http://pastebin.com/XrvUG7hV >> >> I couldn't obtain the objctl from the second node as I stopped >> corosync altogether as leaving it connected caused the cluster never >> to elect a DC. >> >> >> -- >> Diego Lima >> http://www.diegolima.org -- Diego Lima http://www.diegolima.org _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
