[xymon] CPU load average not being graphed for some servers

[Ward, Martin]

Hi Buchan,

I did provide the output from the client data for the particular
section, I didn't think it made sense to dump the whole output packet
when it's only two lines that are the problem. Still, here it is again
with more detailed information on the issue, hopefully this will help
someone to code around this.

The original issue I had was that if the /var/adm/utmpx file didn't
exist or didn't contain a BOOT_TIME record then the output of the
uptime(1) command looked like this in the Xymon client data:

[uptime]
 11:25am  1 user,  load average: 1.21, 0.64, 0.46
[who]
...

For reasons unknown (because I haven't dug through the code) this
stopped Xymon from logging the load average data even though it
displayed it at the top of the "cpu" web page.

The Xymon code seems to require the output of uptime to look like this:
[uptime]
 12:29pm  up 133 day(s),  2:34,  5 users,  load average: 4.90, 4.63,
4.41
[who]
...

If it helps you any I have also seen uptime output, when the uptime is
less than one day, of:
[uptime]
 12:29pm  up 2:34,  5 users,  load average: 4.90, 4.63, 4.41
[who]
...

I hope this helps,

|\/|
--  
Martin Ward
Manager, Technical Services

DDI:+44 (0) 20 7863 5218 / Fax: +44 (0)20 7863 9999 /  www.colt.net
Colt Technology Services, Unit 12, Powergate Business Park, Volt Avenue,
Park Royal, London, NW10 6PW, UK.

Help reduce your carbon footprint | Think before you print. Registered
in England and Wales, registered number 02452736, VAT number GB 645 4205
50


> -----Original Message-----
> From: Buchan Milne [mailto:bgmilne at staff.telkomsa.net]
> Sent: 15 October 2010 12:21
> To: xymon at xymon.com
> Cc: Ward, Martin
> Subject: Re: [xymon] CPU load average not being graphed for some
servers
> 
> 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

[Colt Disclaimer]
The message is intended for the named addressee only and may not be disclosed
to or used by anyone else, nor may it be copied in any way. The contents of
this message and its attachments are confidential and may also be subject to
legal privilege. If you are not the named addressee and/or have received this
message in error, please advise us by e-mailing abuse at colt.net and delete the
message and any attachments without retaining any copies. Internet
communications are not secure and Colt does not accept responsibility for this
message, its contents nor responsibility for any viruses. No contracts can be
created or varied on behalf of Colt Technology Services, its subsidiaries,
group companies or affiliates ("Colt") and any other party by email
communications unless expressly agreed in writing with such other party.
Please note that incoming emails will be automatically scanned to eliminate
potential viruses and unsolicited promotional emails. For more information
refer to www.colt.net or contact us on +44(0)20 7390 3900