[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [xymon] CPU load average not being graphed for some servers
- To: <xymon (at) xymon.com>
- Subject: RE: [xymon] CPU load average not being graphed for some servers
- From: "Brand, Thomas R." <TRBrand (at) cvs.com>
- Date: Wed, 13 Oct 2010 12:52:34 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=cvs.com; i=TRBrand (at) cvs.com; q=dns/txt; s=Retail; t=1286988766; x=1318524766; h=x-mimeole:content-class:mime-version:content-type: subject:date:message-id:in-reply-to:x-ms-has-attach: x-ms-tnef-correlator:thread-topic:thread-index:references: from:to:x-originalarrivaltime:x-rsa-inspected: x-rsa-classifications:x-rsa-action; z=X-MimeOLE:=20Produced=20By=20Microsoft=20Exchange=20V6.5 |Content-class:=20urn:content-classes:message |MIME-Version:=201.0|Content-Type:=20multipart/alternativ e=3B=0D=0A=09boundary=3D"----_=3D_NextPart_001_01CB6AF7.0 8BEB802"|Subject:=20RE:=20[xymon]=20CPU=20load=20average =20not=20being=20graphed=20for=20some=20servers|Date:=20W ed,=2013=20Oct=202010=2012:52:34=20-0400|Message-ID:=20<E 38DCD6606C55F499A4125611AB8D9960B62E5B4 (at) cvsexbpd2.Corp.CV S.com>|In-Reply-To:=20<31955_1286986056_4CB5D948_31955_34 7354_1_1F7B01020EC4D04DA17703634B9E888E112CE817 (at) ULPGCTMVM AI003.EU.COLT>|X-MS-Has-Attach:=20|X-MS-TNEF-Correlator: =20|Thread-Topic:=20[xymon]=20CPU=20load=20average=20not =20being=20graphed=20for=20some=20servers|Thread-Index: =20Actq8LqhnmVbGk0/S1yHhaC2Gn4SogABOGqA|References:=20<31 955_1286986056_4CB5D948_31955_347354_1_1F7B01020EC4D04DA1 7703634B9E888E112CE817 (at) ULPGCTMVMAI003.EU.COLT>|From:=20"B rand,=20Thomas=20R."=20<TRBrand (at) cvs.com>|To:=20<xymon (at) xym on.com>|X-OriginalArrivalTime:=2013=20Oct=202010=2016:52: 38.0191=20(UTC)=20FILETIME=3D[0ADCF3F0:01CB6AF7] |X-RSA-Inspected:=20yes|X-RSA-Classifications:=20public |X-RSA-Action:=20allow; bh=YtGQEktsI3UPlyy0AvCP9mCBUzOhfTj/mwgjTLy3lGw=; b=UksMYhW933j50MRlNx7/3mSKU4TZz/v4qgMXaneQuPEEpLVQF04epnys tPC6pk2n3daCAZhzLE2iTm8oj9rSwc4/Bg9jmHNjjSKz2RmG8mI+x7rBP efBetrH50SIcwD5;
- Domainkey-signature: s=Retaildk; d=cvs.com; c=nofws; q=dns; h=Received:Received:Received:X-MimeOLE:Content-class: MIME-Version:Content-Type:Subject:Date:Message-ID: In-Reply-To:X-MS-Has-Attach:X-MS-TNEF-Correlator: Thread-Topic:Thread-Index:References:From:To: X-OriginalArrivalTime:X-RSA-Inspected: X-RSA-Classifications:X-RSA-Action; b=NfDAJDA185g6DCXRZ9MT0w00rEHUW+SEETkceLgGtt2q4iuYsn0+1ae8 wrWUF59SuGl20PKOBbbTwpJGCI5LrUc5P1vyQ3tO54QB8kJcgqSUD/h5j W6PB+zAA4fXDRWV;
- References: <31955_1286986056_4CB5D948_31955_347354_1_1F7B01020EC4D04DA17703634B9E888E112CE817 (at) ULPGCTMVMAI003.EU.COLT>
- Thread-index: Actq8LqhnmVbGk0/S1yHhaC2Gn4SogABOGqA
- Thread-topic: [xymon] CPU load average not being graphed for some servers
From: Ward, Martin [mailto:Martin.Ward (at) colt.net]
Hi all,
I'm having trouble tracking this one down. For many of my
Xymon-monitored servers I can see the graphs on the CPU load page and
they have data in them. Yet for many others the CPU graphs are empty. I
can see the graphs but there is no data.
Investigation reveals that for those servers who are missing data the
.cpu file has not been updated in months, yet when I look at the client
data available it shows the load average in the uptime section, as in:
[uptime]
5:07pm 2 users, load average: 0.53, 0.71, 0.62
which is, I believe, where Xymon gets the LA from.
Martin,
This may be related to an issue I came across last year.
The (cpu load and users & processes) graphs appear to be dependent on
the exact output of the 'uptime' command.
In my case, the graphs did show for the first 24 hours of uptime,
didn't show after 24 hours, then started showing again after 48 hours of
uptime.
I was finally able to isolate this to the output of 'uptime' for the
first full day - it showed 'day' not 'days'.
# uptime
12:41pm up 196 days 21:49, 5 users, load average: 0.23, 0.19, 0.17
# uptime
12:41pm up 1 day 21:49, 2 users, load average: 0.06, 0.02, 0.00
I 'fixed' this by updating hobbitclient-linux.sh and modified the output
of the 'uptime' command replacing 'day ' with 'days '.
echo "[uptime]"
uptime | perl -pe "s/^(.*) day (.*)/\1 days \2/"
It appears your uptime command does not show the 'up x days HH:MM'.
Cheers,
Tom Brand