[Xymon] no vmstat data for 8 hours on weekdays?

[Mike Burger]

Right...it wasn't logging, but CPU utilization data that was missing in
the graphs. Logging was fine, and all other graphs were fine...just the
CPU utilization graph was having issues. J

 

From: Chris.Morris at rwe.com [mailto:Chris.Morris at rwe.com] 
Sent: Friday, November 16, 2012 4:02 AM
To: jlaidman at rebel-it.com.au; Mike Burger
Cc: xymon at xymon.com
Subject: RE: [Xymon] no vmstat data for 8 hours on weekdays?

 

I think Mike said yesterday that is was his "procs" section that was
causing the client to generate oversized client message. This test
precedes the vmstat test in xymonclient-aix.sh

	 

________________________________

	From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com]
On Behalf Of Jeremy Laidman
	Sent: 15 November 2012 23:17
	To: Mike Burger
	Cc: xymon at xymon.com
	Subject: Re: [Xymon] no vmstat data for 8 hours on weekdays?

	On 16 November 2012 02:48, Mike Burger
<Mike.Burger at freedommortgage.com> wrote:

		That did it. I'm not sure if MAXMSG_STATUS or
MAXMSG_DATA is the culprit, though I suspect it's _DATA.

	 

	Nice one.  Pretty sure it would be MAXMSG_CLIENT, which relates
to the client messages.  I have this set to 2048 on my server because I
have some particularly fast-moving log files I want to monitor on a
couple of my servers.

	 

	Rather than increasing the limit, you might want to find out why
the client message is so large and try to reduce the size if you can.
Perhaps the server is logging heeeeaps of messages into a logfile that's
being monitored. Have a browse through the client data and see if
there's one section that's really big and can probably be adjusted or
eliminated.

	 

	$ xymoncmd xymon localhost 'clientlog name-of-client' | less

	 

	If it's log data, and you don't actually report on log messages,
you might consider removing the "log:" entry from client-local.cfg on
the Xymon server - either from the [aix] section, or (if it exist) from
the [name-of-host] section.

	 

	Or you can have the client put a cap on the size of log data
being sent back in its client message by adjusting the "log:" entry in
the file client-local.cfg on the server.  This limit is fetched by the
client from the server after it reports its client data.  So an
adjustment on the server can take up to 10 minutes to be honoured by the
client.  The default for AIX syslog.log is 10k, so it's unlikely that
this alone could push your client messages beyond 512k.

	 

	J

	 

************************************************************************
**** 

The information contained in this email is intended only for the use of
the intended recipient at the email address to which it has been
addressed. If the reader of this message is not an intended recipient,
you are hereby notified that you have received this document in error
and that any review, dissemination or copying of the message or
associated attachments is strictly prohibited. If you have received this
email in error, please contact the sender by return email or call 01793
877777 and ask for the sender and then delete it immediately from your
system.Please note that neither the RWE Group of Companies nor the
sender accepts any responsibility for viruses and it is your
responsibility to scan attachments (if any). 

 

************************************************************************
***** 

 




CONFIDENTIALITY NOTICE: This e-mail message, including all attachments, is for
the sole use of the intended recipient(s) and may contain confidential
information. Any unauthorized review, use, disclosure, alteration or
distribution is strictly prohibited and may violate state or federal law. If you
are not the intended recipient, please contact the sender by reply e-mail,
delete this email and destroy all copies of the message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20121116/39a43da7/attachment.html>