RE: [Linux-cluster] trouble trying to get ccs/cman working on onemachine, not the other

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

 



> -----Original Message-----
> From: linux-cluster-bounces@xxxxxxxxxx 
> [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of 
> Lennert Buytenhek
> Sent: Saturday, June 26, 2004 6:08 PM
> To: linux-cluster@xxxxxxxxxx
> Subject: Re: [Linux-cluster] trouble trying to get ccs/cman 
> working on onemachine, not the other
> 
> On Sat, Jun 26, 2004 at 11:30:57PM +0200, Lennert Buytenhek wrote:
> 
> 
> OK, found out why they didn't see each other.  If your /etc/hosts has
> something like this:
> 
> 127.0.0.1               phi localhost.localdomain localhost
> 
> (which might be a remnant from an earlier Red Hat install on this box,
> created by the installer if you install without initially 
> configuring a
> network adapter) the port 6809 broadcasts will happily be 
> sent out over
> the loopback interface towards 10.255.255.255, and no wonder that your
> machines are not going to see each other.
> 

I ran into similar problem on fresh FC2 install (not upgrade), in which
I configured my cluster nodes to have static addresses 192.168.1.110 and
192.168.1.111.  (IOW, neither of Lennert's guesses above as to source of
problem applied to my situation).

I manually changed /etc/hosts to replace 127.0.0.1 with, e.g.,
192.168.1.110 and was able to join the cluster.

Was this the "right thing to do"?  Is this a bug in FC2?  What should
set up /etc/hosts??

Thanks.

-- Ben --

Opinions are mine, not Intel's


[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux