That did it. I'm not sure if MAXMSG_STATUS or MAXMSG_DATA is the culprit, though I suspect it's _DATA.
From: Mike Burger Sent: Thursday, November 15, 2012 8:08 AM To: Mike Burger; 'Jeremy Laidman' Cc: 'xymon at xymon.com' Subject: RE: [Xymon] no vmstat data for 8 hours on weekdays?
Ok...I've modified the following options in the xymonserver.cfg file:
MAXMSG_CLIENT changed from 512 to 1024
MAXMSG_STATUS changed from 256 to 512
MAXMSG_DATA changed from 256 to 512
I'll be watching to see how things look as we get to/past the 9AM hour.
From: Mike Burger Sent: Thursday, November 15, 2012 8:03 AM To: Mike Burger; Jeremy Laidman Cc: xymon at xymon.com Subject: RE: [Xymon] no vmstat data for 8 hours on weekdays?
I think I've found it in the server's xymond.log:
Oversize status msg from <client IP> for <hostname>:procs truncated (n=<some #>, limit=262144)
Oversize data/client msg from <client IP <truncated (n=<some #>, limit=524288).
Now, I need to figure out how to change those limits.
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Mike Burger Sent: Thursday, November 15, 2012 7:46 AM To: Jeremy Laidman Cc: xymon at xymon.com Subject: Re: [Xymon] no vmstat data for 8 hours on weekdays?
Good to know...I was trying (unsuccessfully) to compile the 4.3.10 client for AIX, in case it was the client side.
On the other side...I did stop the client, killed any remaining vmstat processes and started the client back up. Initially, only one vmstat process was running, and then eventually there were two at any given time, again. They kick off every 5 minutes, outputting to a vmstat file tied to that process' PID (hobbit_vmstat.<hostname>.PID), and at the end of the run, the PID specific vmstat file is supposed to be renamed to hobbit_vmstat.<hostname>. The one thing I notice is that I never see a file hobbit_vmstat.<hostname>...even now, while there is still data actually being reported in the graph (it's only 7:44AM at present), there is no vmstat file without the PID as part of the file name present. Not that I think that is the problem.
Is there anything I can do to increase verbosity in the client and/or server logging to determine if there's some sort of communication issue (or lack thereof)?
From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] Sent: Wednesday, November 14, 2012 6:20 PM To: Mike Burger Cc: xymon at xymon.com Subject: Re: [Xymon] no vmstat data for 8 hours on weekdays?
On 15 November 2012 02:04, Mike Burger <Mike.Burger at freedommortgage.com> wrote:
Silly question time...is that code in the server or client?There are no silly questions: all questions lead to enlightenment!
The parser runs on the server.
J
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.
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.