Como configurar o Ganglia no Unicast corretamente?

Question

Estou trabalhando com o Ganglia, ótima ferramenta pelo caminho! Estou tentando fazer esta topologia , com alguns nós executando centOS 6.4 centOS 5.9 .

Então, para isso eu estou tentando esta configuração para o GMetad (o resto é o padrão):

##########################################################################
Head Monitor Cluster (GMetad + Gmond > mute no > deaf no + GWeb ) | centOS 6.4 (desktop)
##########################################################################
data_source "head monitor clusters" 10 192.168.1.100 # 192.168.1.100 == localhost
data_source "monitor cluster" 10 192.168.1.51:8649
gridname "Company"
authority "http://192.168.1.100/ganglia/"



##########################################################################
Monitor Cluster (GMond > mute no > deaf no ) | centOS 6.4 (minimal)
##########################################################################

globals {
  daemonize = yes
  setuid = yes
  user = ganglia
  debug_level = 0
  max_udp_msg_len = 1472
  mute = no
  deaf = no
  allow_extra_data = yes
  host_dmax = 86400 /*secs */
  cleanup_threshold = 300 /*secs */
  gexec = no
  send_metadata_interval = 5 /*secs */
}

cluster {
  name = "Monitor"
  owner = "unspecified"
  latlong = "unspecified"
  url = "unspecified"
}

/* The host section describes attributes of the host, like the location */
host {
  location = "unspecified"
}

udp_send_channel {
  host = 192.168.1.51 # send the data collect to itself
  port = 8649
  ttl = 1
}

udp_send_channel {
  host = 192.168.1.100 #send the data to 
  port = 8649
  ttl = 1
}


/* You can specify as many udp_recv_channels as you like as well. */
udp_recv_channel {
  port = 8649
}

/* You can specify as many tcp_accept_channels as you like to share
   an xml description of the state of the cluster */
tcp_accept_channel {
  port = 8649
}


##########################################################################
Node (Gmond > mute no > deaf yes ) | centOS 5.9 (minimal)
##########################################################################

/* This configuration is as close to 2.5.x default behavior as possible
   The values closely match ./gmond/metric.h definitions in 2.5.x */
globals {
  daemonize = yes
  setuid = yes
  user = ganglia
  debug_level = 0
  max_udp_msg_len = 1472
  mute = no
  deaf = yes
  host_dmax = 86400 /*secs */
  cleanup_threshold = 300 /*secs */
  gexec = no
}

cluster {
  name = "Monitor"
  owner = "unspecified"
  latlong = "unspecified"
  url = "unspecified"
}

/* The host section describes attributes of the host, like the location */
host {
  location = "unspecified"
}

/* Feel free to specify as many udp_send_channels as you like.  Gmond
   used to only support having a single channel */
udp_send_channel {
  host=192.168.1.51 #send to monitor cluster
  port = 8649
  ttl = 1
}

/* You can specify as many udp_recv_channels as you like as well. */
udp_recv_channel {
#  mcast_join = 239.2.11.71
  port = 8649
#  bind = 239.2.11.71
}

/* You can specify as many tcp_accept_channels as you like to share
   an xml description of the state of the cluster */
tcp_accept_channel {
  port = 8649
}

E é isso. Mas esta configuração não está funcionando, eu já configurei 9 máquinas virtuais para fazer isso funcionar, mas nada até agora. Eu disabled iptables, ip6tables and selinux . Eu estou trabalhando nisso por 3 dias e noite e nada parece funcionar .. Eu gostaria de alguma ajuda, por favor, por favor, peço ajuda. Eu realmente não entendo porque esta configuração não está funcionando, depois de ler tantos tutoriais e o livro O'Reilly sobre o Ganglia. Qualquer ideia ? Ou ajuda?

E sim, se eu fizer: de 192.168.1.100 8649 telnet 192.168.100 8649 , todos os dados coletados são exibidos .

O mesmo acontece com 192.168.1.51 , de 192.168.1.100 , mas este não é exibido na Web do Ganglia. Os gráficos, são sempre -nan.

Alguma ideia? Obrigada!

    

Answer 1

Consegui corrigir o problema. Por alguma razão ganglia-gmond que veio com o centOS 5. * é gmond-3.0.7 que veio com EPEL package, mas eu adicionei rpmforge repository e descobri a versão 3.1.7 que parece suportar a configuração unicast, agora tudo está funcionando bem.

Obrigado!