Wow... I didn't know there was an O'Reilly book on Ganglia! I will look
into that for sure. Thanks for mentioning it.
To answer your questions:
1. deaf and mute are set to 'no'. that must be the default setting
since I've never messed with those settings before in all my years of
working
I'm still racking my brain with this problem I'm having. I've even
ran 'tcpdump -i any port 8204' on my gmetad server and watched the
traffic when I've got two gmond clients sending out multicast
packets on port 8204 I can see handshaking between my server and
I'm still racking my brain with this problem I'm having. I've even ran
'tcpdump -i any port 8204' on my gmetad server and watched the
traffic when I've got two gmond clients sending out multicast
packets on port 8204 I can see handshaking between my server and *one*
client. The other
Being that I work at NASA, I'd rather not put entire files out there
with names of hosts and ports and the like. :) My initial post had in
it part of the gmond config's.
My datasource line in my gmetad.conf file (for this one port) is simply
something like this:
data_source my_name
Are you afraid that we could see performance data of the Curiosity? :D
First of all I would really suggest you read the Monitoring with Ganglia
book (2012). It answers many questions and solves major problems.
About your issue:
1. How do you set deaf and mute in gmond nodes?
2. How many
On Dec 4, 2014, at 2:06 PM, Chris Jones christopher.r.jo...@nasa.gov wrote:
This makes no sense. I don't believe I've oversubscribed the number of
gmond's on my server (around 150 maybe?). The gmetad server is running
RHEL 6.2, and my two gmond clients are running RHEL 6.5. The strange
I'm curious as of what the correct answer would be, but..
We have similar problem (forgive if not, I just scanned through your
email), and some kind of solution was to use different data_source
(@gmetad) for each of such issues and give them same cluster { name =
} (@gmond).
I think this
7 matches
Mail list logo
