[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: Buchan Milne <bgmilne (at) staff.telkomsa.net>
- Date: Fri, 15 Oct 2010 12:20:47 +0100
- Cc: "Ward, Martin" <Martin.Ward (at) colt.net>
- References: <31955_1286986056_4CB5D948_31955_347354_1_1F7B01020EC4D04DA17703634B9E888E112CE817 (at) ULPGCTMVMAI003.EU.COLT> <E38DCD6606C55F499A4125611AB8D9960B62E5B4 (at) cvsexbpd2.Corp.CVS.com> <21320_1287067615_4CB717DE_21320_385153_1_1F7B01020EC4D04DA17703634B9E888E112CEA60 (at) ULPGCTMVMAI003.EU.COLT>
- User-agent: KMail/1.13.3 (Linux/2.6.33.7-desktop-2mnb; KDE/4.4.3; x86_64; ; )
On Thursday, 14 October 2010 15:46:28 Ward, Martin wrote:
> Thanks Tom, that got me sorted. It seems that Solaris relies on the
> BOOT_TIME record held in the /var/adm/utmpx file. This file has been
> rotated out of the way in order to save disk space so I got no uptime
> values at all. It looks like this messed with the load average data
> since the uptime output didn't have any uptime in it.
>
>
>
> Like you I have hacked the hobbitclient-sunos.sh file and put in a small
> perl scriptlet so that if there is no uptime it adds a fake value in
> just to ensure that the load averages get stored properly.
It would be useful if you could instead supply the "client data" for the host
in the events where this breaks, so it can be fixed in hobbitd_client instead.
Regards,
Buchan