Eu tenho enfrentado esse problema quando o Ganglia está instalado no Ubuntu. De acordo com o documento , parece que o gmond perdeu metadados e não sabe o que fazer com a métrica dados. Como você está configurando o Ganglia no modo unicast, é necessário instruir o gmond periodicamente a enviar metadados alterando send_metadata_interval
para um valor diferente de zero:
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 = 0 /*secs */
cleanup_threshold = 300 /*secs */
gexec = no
send_metadata_interval = 30 /*secs */
}
Tente!
Leia mais:
3.1 collectors will request a gmond to resend its metric description information if needed and if using multicast, if you are using unicast there is no way to do that yet and so if you restart your collector will be left with partial or no data from the cluster that is being collected through it untill all gmond in that cluster are restarted. To workaround this problem if using unicast setup
send_metadata_interval
to a reasonable value so that all gmond resent their metadata periodically to the collector in case it gets lost.
In recent versions of gmond (3.1.x), a new global variable was added in
gmond.conf
calledsend_metadata_interval
, with a default setting of 0. Purpose was to reduce network traffic. In 3.1 metric data is sent separately from metadata e.g. metadata contains detailed description, grouping, other possible setting. A value of zero means that the gmond will send metadata when it starts, and no other time (which is consistent with older versions of ganglia).If you plan on using unicast mode, please set
send_metadata_interval
to something other than 0. 30-60 seconds has been found to work reliably in most cases. Setting this variable to a non-zero value will make the gmond processes periodically announce their metrics and the graphs will reappear on the host-view page.