the gaps in the gmetad graphs are caused by *UNKNOWN* data. let's walk
through this is figure out what is going on
here is the relavent gmetad code...in ./gmetad/rrd_helpers.c RRD_create().
- begin code snip -
/* Our heartbeat is twice the step interv
On Friday, March 14, 2003, at 08:47 AM, Jason A. Smith wrote:
I am seeing two major problems:
First, what exactly is the purpose of the new GRID tag? It seems that
it is a mandatory part of the new gmetad system, and more importantly
the authority attribute is mandatory. Is this correct? It
... real logging facility.
You know.
Specified in the config file.
Defaults to "/var/log/gmetad".
Spews timestamped error-and-above-level messages.
Might help me figure out why my gmetad stopped working about 30 minutes
ago, or why it comes right up when I restart it.
Yet running it in ful
Jason A. Smith wrote:
I do agree with you about making sure that the second gmetad has a
polling interval set to be the same or greater than the interval in the
gmetad that it is getting data from. What is a safe value to use here
anyway? This does help, but not eliminate the problem. It looks
matt,
Thank you for the quick response:
gstat -a
CLUSTER INFORMATION
Name: This is my desktop machine
Hosts: 0
Gexec Hosts: 0
Dead Hosts: 0
Localtime: Fri Mar 14 17:45:06 2003
There are no hosts up at this time
-john
On Fri, 14 Mar 2003, matt massie wrote:
> john-
>
> what do you see when you
matt massie wrote:
john-
what do you see when you run
% gstat -a
you might want to alias gstat to "gstat -a". right now, gstat only shows
hosts running "gexec" unless you specify the -a flag.
that behavior is very likely to change in the future. sorry for the
hassle.
How odd - he's n
john-
what do you see when you run
% gstat -a
you might want to alias gstat to "gstat -a". right now, gstat only shows
hosts running "gexec" unless you specify the -a flag.
that behavior is very likely to change in the future. sorry for the
hassle.
--
matt
Today, John M Hicks wrote forth
Hi,
On 2002-12-06 John Shedletsky wrote:
Hello,
I've been trying to set up Ganglia for some days now and I could really
use some help. Right now, I've just got gmond running on a single computer.
Gmond and gmetad start up fine, but after they do, shouldn't I be able to
see a host under gstat
Sorry about my first email, I didn't mean to imply that there was
something wrong with your patch, just that it may have exposed another
problem. I have been thinking about this more and I guess this bug was
only exposed by my change to gmetad to remove the GRID tag from its xml
output so it would
I do agree with you about making sure that the second gmetad has a
polling interval set to be the same or greater than the interval in the
gmetad that it is getting data from. What is a safe value to use here
anyway? This does help, but not eliminate the problem. It looks like I
still get freque
Jason A. Smith wrote:
Which cause the now famous gaps in the rrd graphs when looking at the
hour resolution. The 2.5.2 version of gmetad does not have a problem
getting data from gmetad with the grid tag removed, but 2.5.3 does so I
can only assume it must be related to the new timestamp patch.
I am seeing two major problems:
First, what exactly is the purpose of the new GRID tag? It seems that
it is a mandatory part of the new gmetad system, and more importantly
the authority attribute is mandatory. Is this correct? It appears that
if you setup one gmetad to collect data from another
12 matches
Mail list logo
