November 2015 - Xymon - Xymon mailman web

Terabithia RPMs updated for 4.3.22
by cleaver＠terabithia.org 10 Nov '15

10 Nov '15

Hello all, The Terabithia RPMs have been updated for Xymon 4.3.22, and I've pushed 4.3.22-2 from testing to the "live" repos at http://terabithia.org/rpms/xymon/. These RPMs are provided for EL3-EL7 in support i#86/x86_64 architectures, and Fedora 18-23 in x86_64. As has been mentioned, we're more or less beginning Xymon 4.4 development at this point. I envision Xymon 4.4 will incorporate most -- but probably not completely all -- of the features and options present there upon release. The in-source sample generic Linux packaging will also be brought more in-line with current best practices as needed, and over time I envision transitioning mostly to the packaging in the source. Regards, -jc

3 2

SSL Certificate test failure
by werner＠maiers.de 10 Nov '15

10 Nov '15

>> xymon would never be fast enough implementing checks against current ssl >> vulnerabilities >> >> ssllabs does provide a webservice API for thorough SSL checking which can >> be accessed from xymon quite easily >> > I don't think anybody asked for this functionality. We're simply asking > Xymon to be able to differentiate between a certificate with a valid > chain of trust and one that is broken or self-signed. in general, if you are using SSL w/ official certificates, it will not sufficient just to check if the chain would be ok and if the cert is still valid (it's a start, but it won't be enough - at least soon). Browsers are starting to deprecate some SSL-features, and they are talking about to drop SHA1 signatures soon. so you need to check at least: - does the certificate contain the name * CN / single name certificates * SAN / multidomain name certficiates (SNI) - is the cert still valid - is the chain of trust ok - which size is server key - which signature algorithm is used - [...] I don't want to see this IN the xymonnet script, as the needs will change faster than you want to upgrade your running xymon server. Therefore I would recommend to do this via an external script and use testssl.sh <https://github.com/drwetter/testssl.sh/> The benefit would be to be able to check not only a valid trust chain but also more things that need to be checked if you work with SSL. for example: - all mentioned things above plus: - supported ciphers - offered encryption grades - testing against known vulnerabilities so one could check exactly what is needed - there are big differences in production requirements vs. private webhosts. regards, Werner Maier -- Dipl.-Ing. Univ. Werner Maier http://www.maiers.de/

1 0

Combo status question
by cleaver＠terabithia.org 10 Nov '15

10 Nov '15

On Fri, October 30, 2015 4:15 pm, Colin Coe wrote: > Hi all > > Is it possible to have a combo status for switch ports on non-stacked > switches? For example, gi1/0/24 on either switch sw01 or sw02 must be > up. > > Thanks > > CC Well, I think anything is possible :) It depends on how you're modeling it. Is this something being probed by devmon, or some other type of snmp utility? If so, then if they're reporting as distinct tests into xymon, it should just be a matter of aligning your combostatus.cfg tests to boolean logic around those individual ports / tests: If device1.porta + device1.porta > 1, then <unified switch hostname>.porta = green. If by "port" you're more or less meaning "IP address", one way to do it would be to use the extended "conn={best,|worst,}IP1[,IP2...]" functionality on your hosts.cfg(5) specification. The problem there is that you're forfeiting whatever other ping awareness you wanted to have WRT the device in question. Honestly, if you're going to be doing a lot of this across lots of devices, I'd look into writing a channel parser (or intermittent status query mechanism) that can look at raw data from all the devices at once (as reported by... whatever's reporting it now), do some unified evaluations, and report it back as a new column against the device. This is basically duplicating the intent of the combostatus function, but with logic specific to what you're looking for out of it. Again, it depends on how xymon is seeing the port information now... HTH, -jc

2 2

corporate donations
by Phil.Crooker＠orix.com.au 09 Nov '15

09 Nov '15

My company is willing to make a donation (call it yearly maintanance) for xymon but we need a yearly invoice for this to happen. Paypal won't work with the accountants. Any suggestions? thanks, Phil

3 3

downtime globally
by jlaidman＠rebel-it.com.au 09 Nov '15

09 Nov '15

On 26 June 2015 at 06:01, Dito <dito74 at gmail.com> wrote: > The test that I need NOT reporting on weekends are NOT network tests, they > are custom ALC that written on the agent folder and forwarded to the xymon > server. Can I only use Downtime for Network tests? > I don't believe it's only for network tests; should work for all tests. > Right now now I have this line, but I am still getting alerts on weekends > > 10.51.0.203 bosutil.domainname.com # smtp > DOWNTIME=ALC1:5:2300:2359:check_op_con,ALC2:5:2300:2359:check_op_con,ALC1:0:0000:1200:check_op_con,ALC1:6:0000:2359:check_op_con,ALC2:0:0000:1200:check_op_con,ALC2:6:0000:2359:check_op_con,mq:0:0300:1000:snapshots > This all looks OK to me. It says to me that you want the server to be in "downtime" state from Friday 11pm to Sunday midday. What day/time are you getting alerts? Just a hint, you can specify multiple tests in one DOWNTIME specification. So for example: DOWNTIME=ACL1,ACL2:5:2300:2359:check_op_con,... I doubt this would help though, but might shorten your config a bit. Interestingly, an example in the Changes file uses a semicolon instead of a comma to separate the different DOWNTIME specifications, so perhaps see if that helps. Have you looked at the "info" page for the server? It should show what Xymon thinks are the down-times for that server. Can you confirm that this page matches your expectations? J

2 3

Xymon 4.3.22 Released
by olivier＠minas.fr 06 Nov '15

06 Nov '15

the same !! <div>-------- Message d'origine --------</div><div>De : James Louis <jglouisjr at gmail.com> </div><div>Date :06/11/2015 18:25 (GMT+01:00) </div><div>À : John Thurston <john.thurston at alaska.gov> </div><div>Cc : xymon at xymon.com </div><div>Objet : Re: [Xymon] Xymon 4.3.22 Released </div><div> </div>Agreed! Many thanks! Jim On Fri, Nov 6, 2015 at 11:23 AM, John Thurston <john.thurston at alaska.gov> wrote: On 11/6/2015 7:24 AM, J.C. Cleaver wrote: - snip - Thank you to everyone who's contributed code, ideas, suggestions, and bug reports for this release. Xymon could not succeed without you! We owe deep thanks to J.C. and Henrik for their time and effort. I tip my hat and say, "Well done. Thank you." -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon -- ---------------------------------------- Jim Louis \\\\||//// \ ~ ~ / | @ @ | --oOo---(_)---oOo-- "The software isn't finished until the last user is dead." ~ Anonymous

1 0

Xymon 4.3.22 Released
by cleaver＠terabithia.org 06 Nov '15

06 Nov '15

Hello all, Xymon 4.3.22 has been released and is now available for download at https://sourceforge.net/projects/xymon/ 4.3.22 brings with it a number of bug fixes, improvements, and a smattering of new features for users since the last release, including: - improved reliability and reporting in the Mac OS X client - fixes to compact xymongen test summaries and combostatus.cfg parsing - per-host and per-test exclusion options for automatic flap detection - more standardized 'group' HTML display on pages and subpages - SHA2 digest options for checksum testing of files or URLs - optional use of custom HTTP headers when polling servers - better options for custom parsing of incoming "name-colon-value" data into RRD - clearer rules for HTTP status parsing of tested URLs Of particular note is that HTTP 401 and 403 errors (including the default OS "welcome" pages in some Linux distributions) are now considered critical alerts by default. These HTTP errors can be explicitly tested for, and allowed by, by using the httpstatus= option. Thank you to everyone who's contributed code, ideas, suggestions, and bug reports for this release. Xymon could not succeed without you! For a full list of changes and features, please see the included changelog and release notes. Regards, Japheth "J.C." Cleaver Xymon v4 Maintainer

3 2

Data flooding?
by Galen.Johnson＠sas.com 06 Nov '15

06 Nov '15

Hey, I've never seen this message before: Data flooding from 10.12.9.59 - 1st line client wdev5.linux linux? What does that even mean? I'm using xymonfetch but it typically truncates the file. This time it's causing tests to go purple. =G=

2 1

weird http test issue on 4.3.21
by bferrell＠baywinds.org 05 Nov '15

05 Nov '15

I have a set of name based virtual hosts that I am testing. the hosts.cfg for this looks like this: page Web_Sites "Web Sites" group-only http|info|trends WWW.XXX.YYY.ZZZ site1.org # noconn http://site1.org/sitemap.xml WWW.XXX.YYY.ZZZ site2.com # noconn http://site2.com/sitemap.xml WWW.XXX.YYY.ZZZ site3.com # noconn http://bbjsails.com/sitemap.xml WWW.XXX.YYY.ZZZ site4.com # noconn http://dhluxuries.com/sitemap.xml WWW.XXX.YYY.ZZZ site5.com # noconn http://ferrellsystemsengineering.com/sitemap.xml WWW.XXX.YYY.ZZZ site6.com # noconn http://plainjaneofficeworks.com/sitemap.xml WWW.XXX.YYY.ZZZ site7.org # noconn http://sg-creations.org/sitemap.xml all of the sites but the first work. I've tried, just for fun, re-arranging the order of the sites... No change. I notice the XYMONNETSVCS set is : smtp telnet ftp pop pop3 pop-3 ssh imap ssh1 ssh2 imap2 imap3 imap4 pop2 pop-2 nntp ftps telnets smtps submission msa pop3s imaps nntps ldap ldaps rsync bbd clamd spamd svn oratns qmtp qmqp amqp amqps vnc cupsd ajp13 rdp netbios-ssn snpp ircd lpd There doesn't seem to be any http test defined. The apache logs for the failing site show no access to sitemap.xml Anyone have any thoughts?

2 3

Xymon-4.22-rc3 Available
by cleaver＠terabithia.org 05 Nov '15

05 Nov '15

Hello all! Xymon-4.3.22-rc3 is now available on SourceForge:https://sourceforge.net/projects/xymon/files/Xymon/4.3.22/ The largest change *since rc1/2* is the addition of the 'ACCEPTONLY:' semantic to restrict a specific hosts.cfg entry to a defined set of tests (all other tests for that host will be silently discarded). Other changes: - display group names using HTML tags or special characters should now display properly - combostatus should handle bad config entries without segfaulting on non-glibc systems, like Solaris - multi-hostgraph RRDs for Connection Time should be fixed Please give it a test if you have a chance. I expect this will be the last RC before the 4.3.22 release unless major issues pop up. Regards, -jc

2 2