i too would be interested in a stable 2.5.x release.
- joel
See my second patch this morning, to get_ganglia.php. Basically added
another check for clusters existance.
-fds
On Dec 14, 2004, at 1:17 PM, Jason A. Smith wrote:
Hi Federico,
So you setup the 2.5.7 webfrontend reading from a gmetad with the
scalable option set so it doesn't output the gri
Hi Federico,
So you setup the 2.5.7 webfrontend reading from a gmetad with the
scalable option set so it doesn't output the grid tag? When I had that
setup the other day I would get this error when viewing a cluster:
Ganglia cannot find a data source. Is gmond running?
I did forget to mention t
Well, I personally think you should continue your development on the
next major version. 2.5.x is pretty stable. If someone wants to
maintain it, I would think Matt would be glad to let someone support
2.5.
I feel that if you spend alot of time maintaining 2.5, or bouncing back
between 2.5
Excellent! I'll give it a shot right now.
Cheers!
-Eric
Eric Wages
University of Maine
Advanced Computing Research Lab
20 Godfrey Drive
Orono, ME 04473
(P)(F) 207-866-6510
On Dec 14, 2004, at 7:37 AM, Matt Massie wrote:
http://matt-massie.com/ganglia/ganglia-2.6.0.200412141232.tar.gz
compiles
http://matt-massie.com/ganglia/ganglia-2.6.0.200412141232.tar.gz
compiles and runs on darwin.
-matt
Eric Wages wrote:
Matt,
Did you ever get a chance to fix the duplicate key_metrics issue on
darwin? I'm just getting down to taking a stab at Ganglia again and are
getting stuck at that point.
Matt,
I really want this to be a positive thing. Ganglia is a great tool with huge
potential.
ALL improvements are welcome but I'd like to see changes introduced in a
regular cycle.
BTW, you are more than welcome to come down to SLAC and give a presentation.
You're based at Berkeley, right?
Got it tested and into CVS. I see no parse errors when the scalable
mode is off.
-Federico
On Dec 14, 2004, at 8:33 AM, Jason A. Smith wrote:
Besides the TN fix, it is the only thing that has changed in gmetad's
server.c file since version 2.5.4. I attached a patch which reverts it
back to t
I would also like to see a stable 2.5.x continue for a while with at
least bug fixes and preferably even useful features, like unicast. We
will probably continue to use 2.5.x in production, even well after
2.6/3.0? is released while we come up with a migration strategy, since
we will have to coord
before i respond directly to adeyemi's frustration i'd like to hear from
everyone in the group. don't hold any punches and feel free to express
your feelings, ideas and frustrations especially if they include
workable solutions.
-matt
--
PGP fingerprint 'A7C2 3C2F 8445 AD3C 135E F40B 242A 59
Hi There.
It appears that 2.6.0 is quite a significant step from 2.5.x especially
since there isn't 100% backwards compatibility with 2.5.x. I don't want
to sound too pessimistic but I sense that it may be sometime before we
see an official 2.6.0 release. Why don't we see more frequent minor
This question was recently posted to the discuss list, I am sending it
to the development list because it is related to a suggestion that Matt
posted several months ago, see the attached email.
Is this code to customize the rrd creation still going to make it into
the next or a future release of g
FYI,
Just tried to build the monitor-core on an NFS mounted drive and it
hung on the checking strdup... line. What happens is that it causes
the local NFS server to stall and start dumping nfs server not
responding messages in the system.log. You can recover by a umount -f
and remount.
Pr
Besides the TN fix, it is the only thing that has changed in gmetad's
server.c file since version 2.5.4. I attached a patch which reverts it
back to the 2.5.4 behavior of making the scalable option determine if
gmetad will write the grid tags also. Maybe the parsing & writing of
the grid tags sho
14 matches
Mail list logo
