J.C. Cleaver wrote:
Hello all!
Xymon-4.3.22-beta has been posted to Sourceforge, containing bug fixes and a smattering of new features and improvements since 4.3.21. It's reachable at http://sourceforge.net/projects/xymon/files/Xymon/4.3.22/xymon-4.3.22-beta.t...
Some notable changes are at https://sourceforge.net/projects/xymon/files/Xymon/4.3.22/, while the full Changelog is at https://sourceforge.net/p/xymon/code/7707/tree/branches/4.x-master/Changes
I know there are a few pending bug fixes already that I'd like to get in before the next release (multigraphs, if I can track down the source), however the number of features warrants some testing. Please let me know if you notice any issues (especially on non-Linux systems, as I don't have as much direct access to those).
In particular, the changes in how xymonnet interprets 301/401/403 HTTP status codes could cause some confusion. Those who've customized their NTPDATE or TRACEROUTE command lines should check out the new Options variables. And finally, it would be helpful to have high volume environments (>60000 hosts) testing the "noflap" option for any notable performance impact. (It should be very slight.)
If all goes okay, I'd like to release the final 4.3.22 some time next week.
Apart from John.Thurston at alaska.gov who could not repeat my problem with integer arithmetic in combostatus, I never saw any feedback about the attached patch which fixes our problem on Linux builds.
As a reminder, this rule in combo.cfg :-
angelica.shadymint.com.combo=(angelica.shadymint.com.http + angelica.shadymint.com.bbd + angelica.shadymint.com.procs)>=3
is calculated incorrectly on Linux, but strangely is OK on Solaris.
The error message we get on Linux is :-
2015-10-13 00:39:07.263726 Item '3' has no testname part 2015-10-13 00:39:07.263762 Item '3' has no testname part 2015-10-13 00:39:07.263769 Invalid data for symbol calculation - missing host/testname: 3 6736 2015-10-13 00:39:07.263777 Symbolic '(angelica.shadymint.com.http+angelica.shadymint.com.bbd+angelica.shadymint.com.procs)>=3' converted to '(1+1+1)>=0'
You will not know from the web page that this has failed because '(1+1+1)>=0' is still true, but its not the answer we need to find.
Thanks
Andy