Hi Chuck:
For the first issue - give it time, it should sort itself out. Alternatively,
you can find out which node is reporting incorrect information, and restart
gmond on it.
For the second issue, you can group nodes in different data_source via the
multicast port in /etc/gmond.conf. Use
I need help understanding two things.
I currently have a grid. One of the clusters in the grid is named
"staiu" and the "grid" level web page reports that this has 8 hosts
containing 4 cpus. In actuality, this has 8 hosts each containing 4
cpus, but apparently the hosts are not reporting the
I would like to start a discussion of how to enhance Ganglia to address
issues like removing a host from the grid and reorganizing one cluster
into two clusters.
Today, I was installing ganglia on an 8-node cluster. Apparently, this
cluster could communicate via multicast with a 4-node cluste
How come the source code for ganglia contains multiple versions of
'libtool'? How come these implementations define the location of SED
differently?
"
[EMAIL PROTECTED] ganglia-3.0.2]$ egrep "^SED=" `find . -name "*libtool*"`
./libtool:SED="/bin/sed"
./srclib/apr/build/libtool.m4:SED=$lt_SED
.
On Mar 22, 2006, at 12:33 AM, Martin Knoblauch wrote:
Matt,
after looking at your patch to process_xml.c I just want to ask
whether this is really the right solution.
no. :)
you're right. please feel free to overwrite my half-baked patch.
-matt
Before (-r1.45) the code tried to mark
Matt/Martin and all.
I am finding that I am still getting occassional truncated XML from
gmond, even
after the EAGAIN patches to gmond.c. Interestingly, when the data was
truncated, it ended with a tag. i.e. a host boundary.
Looking at the code, I see this:
/* Walk the host hash */
for(hi =
Matt,
after looking at your patch to process_xml.c I just want to ask
whether this is really the right solution.
Before (-r1.45) the code tried to mark any protocol prior to "2.5" as
old (ignoring the case of 1.x :-). The code broke with the release of
3.0.
Now (-r1.46) you are marking *any*
