I have one more patch to submit for the Xymon 4.3.29 for the xymonnet application. The attached context diff file makes these changes:
- If host is down, do not run rpcinfo or NTP tests on it. Otherwise runtime can be very long (cmdtimeout times the number of hosts down that have an rpcinfo and/or NTP test)
- Change "xymonnet: Cannot resolve IP for host" from an error to a warning. This then allows xymonnet check to not always be yellow when hostnames do not resolve in DNS. The host in the hosts.cfg file will still be marked as failing the conn test as before.
- Add --cmdtimeout option to the --help usage
Thanks...Tom
-----Original Message-----
From: Tom Schmidt (tschmidt)
Sent: Thursday, March 28, 2019 4:18 PM
To: 'Japheth Cleaver' <cleaver at terabithia.org>; Xymon Mailing List <xymon at xymon.com>
Subject: RE: [EXT] [Xymon] Call for 4.3.29 Patches
I have a few patches to submit as well. Attached is a context diff file for my changes to the 4.3.28 source files. Comments includes for most of the changes.
Tom
-----Original Message-----
From: Xymon <xymon-bounces at xymon.com> On Behalf Of Japheth Cleaver
Sent: Tuesday, March 26, 2019 2:38 PM
To: Xymon Mailing List <xymon at xymon.com>
Subject: [EXT] [Xymon] Call for 4.3.29 Patches
Hello all,
I'm pushing for a release of 4.3.29 relatively soon. I've been trying to go through the backlog to identify un-applied patches, but I know there are some that I'm missing. If you have build fixes or runtime changes that have not yet been put in in 4.3.29 already (see:
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourcefor…)
I'd appreciate if you could point them out.
Regards,
-jc
_______________________________________________
Xymon mailing list
Xymon at xymon.comhttps://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xymo…
Ok, thank you for your help :)
Il giorno dom 31 mar 2019 alle ore 13:39 Martin Lenko <lenko99 at gmail.com>
ha scritto:
> Hi Luca,
> the answer is a bit more complex than that, but basically, load 2 on 2 CPU
> machine means that the machine is just about able to cope with the load
> thrown at it. If the load is higher than the number of CPUs for a longer
> period of time, you might have a performance problem.
> More detailed explanation here:
> https://www.howtogeek.com/194642/understanding-the-load-average-on-linux-an…
>
> I usually set the warning/yellow threshold to a value slightly higher than
> the number of CPUs and the critical/red to twice the number of
> warning/yellow value. At least on machines with a small number of CPUs.
>
> I case of 2CPU machine I would set it to:
> LOAD 2.5 5.0
>
> Obviously, if you should review the CPU load patterns of your server and
> update the LOAD config accordingly to make sure the thresholds are not:
> - too low - you might get a lot of false positive alerts
> - too high - you might not notice there is something going and the machine
> is struggling to cope with the load
>
> Regards,
> Martin
>