Gluster users - Sep 2010 - Gluster Storage Platform 3.0.5 fails to detect new nodes

I've successfully installed the first node, configured the management 
network interface, an ALB bond I want to use for the storage network, and 
the storage pool addresses.  When I boot the new node it seems to work 
correctly but just sits in "finding first server" drawing
"...." forever.
The first node is sitting in the "Add Server/Probing server ..."
dialog
box.  I've tried rebooting the new node several times without success.

When you add a new node is the management network interface used to probe 
for new nodes, or if you've defined a separate storage network (as I have) 
does it use that interface for the probes?  Any ideas on how to solve 
this would be appreciated.  There's nothing in any logs, and without shell 
access troubleshooting is extremely difficult.

Thanks,
Kevin

Kevin - 
Shell access isn't problem, ssh is running or you can switch to another
runlevel if you are using X.

User - gluster 
Pass - glusteradmin 

If you need root access just 'sudo -s' and use the
'glusteradmin' password.

We use DHCP running on an non-standard port for new server discovery. As long as
the network between the two servers isn't blocking broadcast it
shouldn't be a problem.

Let us know if that helps. 



Thanks, 

Craig 

-- 
Craig Carl 













Sales Engineer; Gluster, Inc. 
Cell - ( 408) 829-9953 (California, USA) 
Office - ( 408) 770-1884 
Gtalk - craig.carl at gmail.com 
Twitter - @gluster 
Installing Gluster Storage Platform, the movie! 
http://rackerhacker.com/2010/08/11/one-month-with-glusterfs-in-production/ 



From: brooks at netgate.net 
To: gluster-users at gluster.org 
Sent: Tuesday, September 21, 2010 6:29:48 PM 
Subject: [Gluster-users] Gluster Storage Platform 3.0.5 fails to detect new
nodes


I've successfully installed the first node, configured the management 
network interface, an ALB bond I want to use for the storage network, and 
the storage pool addresses. When I boot the new node it seems to work 
correctly but just sits in "finding first server" drawing
"...." forever.
The first node is sitting in the "Add Server/Probing server ..."
dialog
box. I've tried rebooting the new node several times without success. 

When you add a new node is the management network interface used to probe 
for new nodes, or if you've defined a separate storage network (as I have) 
does it use that interface for the probes? Any ideas on how to solve 
this would be appreciated. There's nothing in any logs, and without shell 
access troubleshooting is extremely difficult. 

Thanks, 
Kevin 
_______________________________________________ 
Gluster-users mailing list 
Gluster-users at gluster.org 
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users

Hi Kevin,

There could be two known issues.

1. Check if last IP address of storage pool is free by pinging to it.  If the IP
address is in use, please adjust storage pool to make sure the last IP address 
is not in use.

2. As the installer tries to connect to first server using eth0, you can connect
all NICs of new server into the switch where first server is connected.  After 
installation, you can switch back NIC cabling as per your required setup.

Both issues were fixed in our upcoming 3.1 release and Platform 3.1Alpha0 is 
available for testing.  You can download it from
http://dev.gluster.com/downloads/

Thanks,

Regards,
Bala


brooks at netgate.net wrote:
> 
> I've successfully installed the first node, configured the management 
> network interface, an ALB bond I want to use for the storage network, 
> and the storage pool addresses.  When I boot the new node it seems to 
> work correctly but just sits in "finding first server" drawing
"...."
> forever. The first node is sitting in the "Add Server/Probing server 
> ..." dialog box.  I've tried rebooting the new node several times 
> without success.
> 
> When you add a new node is the management network interface used to 
> probe for new nodes, or if you've defined a separate storage network
(as
> I have) does it use that interface for the probes?  Any ideas on how to 
> solve this would be appreciated.  There's nothing in any logs, and 
> without shell access troubleshooting is extremely difficult.
> 
> Thanks,
> Kevin
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users