Hello Jeff,

On 21 Jul 2012, at 16:55, Jeff Layton wrote:

> Good morning,
> 
> Apologies for the simple question. I've got a simple cluster
> with a master node and one compute node. I installed the
> latest Ganglia on the master node (3.4.0) - libganglia, 
> ganglia-gmond, ganglia-metad, ganglia-web (3.5.1). I can
> use ganglia-web to "see" the master node with no problems.
> 
> I'm using Warewulf for the compute node and I installed
> libganglia and ganglia-gmond in the VNFS and rebooted the
> node. When the node comes back up, I tested ganglia via
> "gstat -all" on the compute node and it seems to work
> correctly.
> 
> However, ganglia-web doesn't display anything for the compute
> node even though I've added it to the data_source line in
> gmetad.conf:
> 
> 
> data_source "my cluster" 10.1.0.250 10.1.0.1:8649
> 
> 
> I also checked if the master node could access the data from
> the compute node via "gstat -all" and I only get data from the
> master node (i.e. no compute node).
> 
> I checked the Ethernet interfaces on both nodes and both
> are listed as MULTICAST. iptabbles on the master node and the
> compute node are off and the services are not running (checked
> that 3 times). 
> 
> There is a simple Netgear GigE switch between the nodes
> (unmanaged). I don't think that's a problem.
> 
> One thing I think is interesting is that the master node has
> eth0 with an IP of 192.168.1.250 which is to the outside world
> and eth1 is 10.1.0.250 which is the cluster network. The compute
> node has eth0 as 10.1.0.1. But when I go to http://localhost/ganglia
> I can only access the master node as 192.168.1.250, not
> 10.1.0.250 (i.e. the list of nodes is only 192.168.1.250).
> 
> Otherwise i can login into the compute node, ping it, etc. It works
> fine but somehow I'm missing a configuration piece for ganglia.

make sure your multicast address is bound to the internal interface, and that 
gmond on the master is listening on that - e.g. with netstat -tulp.
You can use tcpdump to check if the master is receiving packets from the 
worker, on the port that gmond is listening to.
Actually, in non-trivial networks it may be clearer / easier to configure for 
unicast instead - in case you can go back to use multicast once you're sure it 
works with unicast.

Cheers,
  Sergio

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general

Reply via email to