markp wrote:
Is anyone experiencing a high load with gmetad? I've run this daemon on
a high end intel 933mhz dual proc machine with 1gb of memory and RH
7.2. Loads get and stay as high as 3. I get worse results on single
processor machines, loads as high as 6.7 Kill the daemon and it drops
back to normal. Is it supposed to be such a resource hog? I ran the
old web-frontend and didn't have any problems.
Of all the problems I have with gmetad, this ain't one of 'em. (although
I'm the only person on this list who admits to running it on Solaris 8...)
If the usage stays high even when the front end isn't being accessed (in
other words, gmetad's TCP listen process is idle), then your problem is
somewhere within the polling/RRD storage process. Maybe there's something
wacky in the Perl XML parser that gmetad uses (upgrade your version of
expat?) ... I can't imagine a socket library causing such bad behavior ...
and I've heard people complain about RRD being very I/O-intensive when
updating several hundred hosts with several dozen metrics apiece (I haven't
run into this yet).
On my monitoring front end box, the load average is consistently below 0.5.
Is there anything helpful in the (ho ho) log file?
That's all I can think of in the way of troubleshooting gmetad (I didn't
write it :) ).
Good luck, all the same...
