[Xymon] localmode, got over-size message, truncating

[Christoph Zechner]

Hi Jeremy,

first of all: I solved it with your help, thanks!

On 08/03/2022 07:48, Jeremy Laidman wrote:
> Christoph
> 
> There's no limit on the client side. The log "Got oversized message, 
> truncating at ..." comes from xymond running on the Xymon server.

Thank you for confirming, I wasn't sure, if localmode changed any of that.
> 
> The limit for client messages (where your [ps] output is being 
> truncated) is defined by MAXMSG_CLIENT, set in xymonserver.cfg, as an 
> integer for the number of kibibytes (ie, it's multiplied by 1024). The 
> default MAXMSG_CLIENT is 512 (meaning 524288 bytes).
> 
> You've probably set the value correctly, but something else is 
> preventing it from being used. You can confirm that it's set correctly 
> with something like:
> 
> $ xymoncmd --env=/etc/xymon/xymonserver.cfg env | grep MAXMSG_CLIENT
> MAXMSG_CLIENT=2048

This indeed gives me the correct value of 2048.

> 
> If this gives the wrong value of 512, then there's something wrong 
> with/in the file xymonserver.cfg. If this gives the correct value, your 
> xymond probably just needs to be restarted so that it can pick up the 
> configuration change.
> 
> On Linux you can view the environment of a running process in 
> /proc/<pid>/env. This pseudo-file has null line terminators so running 
> it through "strings" makes it more palatable:
> 
> $ sudo -u xymon strings /proc/`pgrep -f '^xymond '`/environ | grep 
> MAXMSG_CLIENT
> MAXMSG_CLIENT=2048

This also showed 2048.

> 
> If you don't get the value that's set in xymonserver.cfg, kill the 
> xymond process and it'll restart using the current setting:
> 
> $ sudo -u xymon pkill -f '^xymond '

Thanks for the hint, I of course restarted the xymonserver, but some odd 
process did seem to survive that. After I manually killed all the 
remaining processes and restarted xymon, the errors in my log have 
stopped and everything is working as expected.

Thank you very much!

Cheers
Christoph


> 
> Cheers
> Jeremy
> 
> 
> On Tue, 8 Mar 2022 at 16:48, Christoph Zechner <zechner at vrvis.at 
> <mailto:zechner at vrvis.at>> wrote:
> 
> 
>     Hi,
> 
>     I've got a problem with a client running in local mode:
> 
>     from /var/log/xymon/xymonclient.log
> 
>     2022-03-08 06:40:22.713067 Got over-size message, truncating at 528383
>     bytes (max: 524288)
>     2022-03-08 06:40:22.725069 Dropping (more) garbled data
> 
>     I already increased the following values on the xymon server:
> 
>     MAXMSG_CLIENT=2048
>     MAXMSG_STATUS=2048
> 
>     but it does not seem to have any effect on my client, because some
>     checks (procs e.g.) still show up red respectively do not show all
>     the data.
> 
>     Is there any other value I have to adjust? Where is the limit of 524288
>     bytes defined on the client?
> 
>     Thanks in advance!
> 
>     Cheers
>     Christoph
>     _______________________________________________
>     Xymon mailing list
>     Xymon at xymon.com <mailto:Xymon at xymon.com>
>     http://lists.xymon.com/mailman/listinfo/xymon
>     <http://lists.xymon.com/mailman/listinfo/xymon>
>