In my experience you need to shut down the gmetad as well as the gmonds.
In addition, you may need to move the RRDs:
1.
Stop all gmonds
2.
Stop gmetad
3.
Move RRDs (for instance cd /var/lib/ganglia ; mv rrds rrds.6 ;
mkdir rrds )
4.
Start
Leaving the clarity and findability of the documented answer
aside,
does anyone know the actual answer to the original question?
We have a cluster with about twenty gmond nodes and one gmetad host.
host_dmax is set to 3600.
Hosts that die never just disappear from the set of graphs.
We go
From: Cameron L. Spitzer cspit...@nvidia.com
To: Bernard Li bern...@vanhpc.org
Cc: Louis Coilliot louis.coill...@think.fr;
ganglia-general@lists.sourceforge.net ganglia-general@lists.sourceforge.net
Sent: Wed, November 17, 2010 10:36:00 PM
Subject: Re: [Ganglia-general] restarting the gmond
Hi Bernard,
- Original Message
From: Bernard Li bern...@vanhpc.org
To: Louis Coilliot louis.coill...@think.fr
Cc: ganglia-general@lists.sourceforge.net
Sent: Wed, November 17, 2010 9:16:22 PM
Subject: Re: [Ganglia-general] restarting the gmond collector node causes no
data to be
On Thu, Nov 18, 2010 at 02:44:13AM -0800, Martin Knoblauch wrote:
besides that this is really unclear and difficult to find, we may want to
consider a different default for unicast mode. It is always better to not let
people run into forseeable problems.
You can get the same problems with
- Original Message
From: Kostas Georgiou k.georg...@atreides.org.uk
To: ganglia-general@lists.sourceforge.net
Sent: Thu, November 18, 2010 11:57:29 AM
Subject: Re: [Ganglia-general] restarting the gmond collector node causes no
data to be reported
On Thu, Nov 18, 2010 at
I second Martin's request. This has been an ongoing issue so we ought to
simply change the default to e.g. 30 seconds or so. We can put in a comment
in the config file that if you are in multicast environment you may want to
set this to 0.
What's the downside of setting it != 0 ? A bit more
I have updated the entry on the FAQ page with what I hope is some clearer
commentary on this issue.
-Original Message-
From: Bernard Li [mailto:bern...@vanhpc.org]
Sent: Thursday, November 18, 2010 1:32 AM
To: Bostjan Skufca
Cc: Louis Coilliot;
I'm running ganglia 3.1.7 on some RHEL computers.
I have four separate clusters configured, with each one running in
unicast mode. Each cluster uses a different port number in their
gmond.conf files.
Here's one example:
udp_send_channel {
#bind_hostname = yes # Highly recommended, soon to be
Hello, this behaviour is reported from time to time with unicast :)
Use:
send_metadata_interval = 600
(600, for example)
on the gmond.conf for your nodes.
The metrics should get back after a while.
Louis
2010/11/17 Auld, Russell G CSC russell.a...@pw.utc.com:
I'm running ganglia
Hello:
This is actually documented in both the release notes and the FAQs in our Wiki:
http://sourceforge.net/apps/trac/ganglia/wiki
Please let us know if anything is unclear.
Thanks,
Bernard
On Wed, Nov 17, 2010 at 1:14 PM, Louis Coilliot louis.coill...@think.fr wrote:
Hello, this
Just out of curiosity, I followed the link in Bernard's message.
I didn't find anything related to Russell's question.
I followed the link to Current Release Notes, and searched the page for
send_metadata_interval, which is cheating,
because I would only have Russell's question if I didn't know
It definitely is unclear.
I, for one, did have a bit (large bit:) of a problem with this. If
only faq would say ...or when graphs are not updated or something
similar.
b.
On 17 November 2010 22:36, Cameron L. Spitzer cspit...@nvidia.com wrote:
Just out of curiosity, I followed the link in
Thanks for the feedback guys. Would one of you like to edit the Wiki
and add more clarity to it? Please let me know if you run into any
issues with the edits (I think you just need a SF.net id to do so).
Cheers,
Bernard
On Wed, Nov 17, 2010 at 8:14 PM, Bostjan Skufca bost...@a2o.si wrote:
It
14 matches
Mail list logo
