Re: Unable to join cluster from a newly-installed centos 6.2 node

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss


[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux