- Xymon - Xymon mailman web

[xymon] too much data in powershell client reports
by MARIO.DECHENNO＠unicampania.it 29 Jan '18

29 Jan '18

Hi all. Even after setting pretty high values for MAXMSG_CLIENT (2560) MAXMSG_STATUS (2048) i got purples from our exchange servers, mainly caused by port test being truncated after about 37000 lines. I noticed the new slimmode options in 2.27 version, but it (AFAIK) could only cut the whole port test, preventing any network port count analysis. Since most of the connections are between the (two) exchange servers, and are reported twice in IPV4 and IPV6 notation, could there be a way to filter the "internal" connections on the client side without sending them to xymon server? I attach an example. Mario

2 3

separate "uptime" status patch
by dominique.frise＠unil.ch 16 Jan '18

16 Jan '18

Hi, We recently enabled the separate "uptime" status column like described here : http://www.it-eckert.com/blog/2015/separate-uptime-status-for-all-xymon-cli… While testing we saw two issues with the uptime displayed status together with the "toolong" limit setting. Assuming this in analysis.cfg : UP 1h 9d First issue When uptime has passed 9 days,the status turns to yellow but the text only shows "System has been up: 9 days." it should display "&yellow Machine has been up more than 9 days" AND "System has been up : 9 days." [cid:b68bacd2-781b-4280-aea3-b0d8c410b9c0] Second Issue The displayed uptime string in "System has bee up: ..." should show the hh:mm in addition to days. Example: "System has been up: 9 days 01:27" The attached patch for xymon-4.3.28 fixes both issues. Hope ths helps, Dominique Frise

1 0

sslcert
by ve2cii＠canasoft.net 09 Jan '18

09 Jan '18

Hi, This is for the sslcert service: I have xymon monitoring a web site where the certificate has been changed twice over the past 2 years. And it is currently up to date. What xymon is showing for the dates of the certificate are wrong. Is there a way to fix this so it shows the correct certificate and not an old one? start date: 2014-12-02 19:29:50 GMT expire date:2015-04-01 19:29:50 GMT Tue Jan 9 10:58:46 2018 red SSL certificate for https://www.thesweetbasket.com/en/ expired 1013 days ago Server certificate: subject:/C=CA/ST=Que/L=Montreal/O=Cronomagic/OU=Web/CN=serv1.thesweetbasket… at canasoft.net start date: 2014-12-02 19:29:50 GMT expire date:2015-04-01 19:29:50 GMT key size:1024 issuer:/C=CA/ST=Que/L=Montreal/O=Cronomagic/OU=Web/CN=serv1.thesweetbasket.… at canasoft.net signature algorithm: sha256WithRSAEncryption Cipher used: ECDHE-RSA-AES256-GCM-SHA384 (256 bits) -- sysadm cronomagic.com/gemstelecom.com e-mail ve2cii at canasoft.net POWERED BY LINUX

3 7

Need Help xymond_filestore Fatal Crash
by dl1025＠att.com 09 Jan '18

09 Jan '18

I never saw this type of message before. This morning received a message stating that xymond_filestore Fatal Signal caught. I saw a purple icon appear for the xymon server for xymond_filestore column. Could someone tell me what is going on here and how to troubleshoot it? Thanks, Daniel

1 0

SSL Error
by sjpostsr＠gmail.com 05 Jan '18

05 Jan '18

One of the websites that I am trying to monitor moved to a new site from http to https. Upon changing in Xymon, I am now getting SSL error Server Info: Ubuntu 16.04 Xymon 4.3.25-1 Openssl Version: OpenSSL 1.0.2g 1 Mar 2016 Xymonnet xymonnet version 4.3.25 SSL library : OpenSSL 1.0.2f 28 Jan 2016 LDAP library: OpenLDAP 20442 Error output: Unspecified SSL error in SSL_connect to https (47873/tcp) on host x.x.x.x: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure I have tried using different combinations in the hosts.cfg httpsc:// httpst:// --sni --no-ssl >From the Xymon server, if I run the command: openssl s_client -connect weburl:443, I get the errors: CONNECTED(00000003) 140008606660248:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:769: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 305 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : 0000 Session-ID: Session-ID-ctx: Master-Key: Key-Arg : None PSK identity: None PSK identity hint: None SRP username: None Start Time: 1515083787 Timeout : 300 (sec) Verify return code: 0 (ok) --- trying: openssl s_client -connect weburl:443 -servername weburl CONNECTED(00000003) depth=3 C = US, O = "The Go Daddy Group, Inc.", OU = Go Daddy Class 2 Certification Authority verify return:1 depth=2 C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", CN = Go Daddy Root Certificate Authority - G2 verify return:1 depth=1 C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", OU = http://certs.godaddy.com/repository/, CN = Go Daddy Secure Certificate Authority - G2 verify return:1 depth=0 OU = Domain Control Validated, CN = weburl verify return:1 --- Certificate chain 0 s:/OU=Domain Control Validated/CN=weburl i:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2 1 s:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2 i:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./CN=Go Daddy Root Certificate Authority - G2 2 s:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./CN=Go Daddy Root Certificate Authority - G2 i:/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority --- Server certificate -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- subject=/OU=Domain Control Validated/CN=weburl issuer=/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2 --- No client certificate CA names sent Peer signing digest: SHA512 Server Temp Key: ECDH, P-256, 256 bits --- SSL handshake has read 4411 bytes and written 458 bytes --- New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256 Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES128-GCM-SHA256 Session-ID: 31590AD5C7EC70D6738AE51265DE3B3351503E280EDC0F147616E93CEA374BE3 Session-ID-ctx: Master-Key: FE4C481FDFEDC7933F5732859AEA6E6840848A8633E04BA4AA454ED256942E401846033109F1E9AA73534EA2B3261531 Key-Arg : None PSK identity: None PSK identity hint: None SRP username: None TLS session ticket lifetime hint: 10800 (seconds) TLS session ticket: 0000 - bc 67 70 3b a5 1f 62 23-2a 74 e8 04 33 5a e4 8b .gp;..b#*t..3Z.. 0010 - 4d d0 77 a5 6f 5a 88 06-26 9e 19 78 da 59 ce 49 M.w.oZ..&..x.Y.I 0020 - e1 29 8a ec c7 7e 46 07-8c 5a f1 a4 b1 4a 3d c7 .)...~F..Z...J=. 0030 - 83 56 f7 d1 78 b4 0f 12-e6 ca 42 cd 30 b2 63 ac .V..x.....B.0.c. 0040 - e1 a3 0d fe d3 cf 37 4d-73 05 ae 99 cc 7e f1 7d ......7Ms....~.} 0050 - 92 fb 7f 87 95 f0 8e 12-17 bf 68 11 44 a1 83 45 ..........h.D..E 0060 - 2a bb 4c 9a 3e 63 ab ab-0a 3d a8 2f 5d e6 c5 f0 *.L.>c...=./]... 0070 - e1 37 5a 9d 3d ae 15 c3-2f ab 2a 0f 07 a5 f8 ee .7Z.=.../.*..... 0080 - 2b df 77 03 6b 40 d2 4a-19 d8 01 c6 18 ab 58 f1 +.w.k at .J......X. 0090 - 26 85 ff b2 b8 20 da 8f-8b c6 83 6d 94 5d 28 d4 &.... .....m.](. 00a0 - 6f d3 f0 0f 9e f8 70 ef-df 85 39 d9 1c cc 12 60 o.....p...9....` Start Time: 1515083843 Timeout : 300 (sec) Verify return code: 0 (ok) ---

2 1

Alerts Stopped Working with DURATION Keyword
by scarville＠lereta.com 02 Jan '18

02 Jan '18

While trying to add a new alert to alerts.cfg I seem to have killed all my alerts. For testing I whittled the alerts.cfg down to one entry: ## proxy servers HOST=scadmzprx01.lereta.com SERVICE=conn,http MAIL covinacomputerroom at lereta.com COLOR=red DURATION>10 SCRIPT /var/xymon/server/bin/sendsms 2135551212 at txt.att.net FORMAT=sms I ran xymond_alert $ ./xymond_alert --test scadmzprx01.lereta.com conn 00064299 2017-12-30 21:11:40 send_alert scadmzprx01.lereta.com:conn state Paging 00064299 2017-12-30 21:11:40 Matching host:service:dgroup:page 'scadmzprx01.lereta.com:conn:Proxies:CADMZ' against rule line 14 00064299 2017-12-30 21:11:40 *** Match with 'HOST=scadmzprx01.lereta.com SERVICE=conn,http' *** 00064299 2017-12-30 21:11:40 Matching host:service:dgroup:page 'scadmzprx01.lereta.com:conn:Proxies:CADMZ' against rule line 15 00064299 2017-12-30 21:11:40 Failed 'MAIL covinacomputerroom at lereta.com COLOR=red DURATION>10' (min. duration 0<601) 00064299 2017-12-30 21:11:40 Matching host:service:dgroup:page 'scadmzprx01.lereta.com:conn:Proxies:CADMZ' against rule line 14 00064299 2017-12-30 21:11:40 *** Match with 'HOST=scadmzprx01.lereta.com SERVICE=conn,http' *** 00064299 2017-12-30 21:11:40 Script alert with command '/var/xymon/server/bin/sendsms' and recipient 2135551212 at txt.att.net Why does the MAIL option fail? It works if I remove the DURATION keyword. FTTB I removed the delayed notifications but I'd like them back I am using xymon version 4.3.28.

2 6

Bounty: Cash for Fix for: Recovery notifications not generated when test goes red->yellow->green?
by spah＠syntec.co.uk 31 Dec '17

31 Dec '17

I realise that there are no paid Xymon staff developers, so I wonder if anyone would be interested in earning some money for fixing this issue: Recovery notifications not generated when test goes red->yellow->green? http://lists.xymon.com/archive/2017-December/045162.html The relevant source code is probably in https://sourceforge.net/p/ xymon/code/HEAD/tree/branches/4.3.29/xymond/do_alert.c If you are interested in working on this, please contact me off-list with your best price and using the same subject line preferably describing what, if any, feature or other changes you would make. This will be sealed bids. Assuming bids are received, the closing date for bids will be 27th December. If anyone is interested in contributing money to this bounty, also contact me with the same subject line preferably by 27th December. I don't know what our budget is for fixing this yet, so any help with it, er, may help! If the best price is reasonable, the winning bidder will be informed and a plan agreed. We would make your patches available to the community for all to enjoy and hopefully be merged into a future release. Kind regards and Happy Christmas, SebA

2 2

"Xymon [0] myhost:xymond stopped reporting (PURPLE)" status
by earle＠isolar.DynDNS.ORG 31 Dec '17

31 Dec '17

We recently set up automated ReaR/fsarchiver backups on our systems, and on some of our machines running older OSes this created havoc as something ("fsarchiver5", we think) ran roughshod over the disk and deleted thousands of files instead of archiving/backing them up. This caused "xymonlaunch" to crash on a few of them. Despite having restored the missing files from tape backups, repeated re-launchings of the "xymon-client" service and even a reinstall/upgrade (to 4.3.28) we're still getting these purple alerts. (It feels like Xymon is seeing some file lying around and deciding that "xymonlaunch" is still in crashed status because of it.) How do I fix this? I suppose I could do 'xymon 127.0.0.1 "drop myhost xymond"' on my monitoring host but that just doesn't feel right ... Thanks, - Greg Forwarded message: > From: xymon Monitor <xymon at monitor.my.do.main> > To: root at xymonmonitor.my.do.main > Subject: Xymon [0] myhost:xymond stopped reporting (PURPLE) > Date: Sat, 30 Dec 2017 15:37:04 -0800 > > red (Check time of report) - xymonlaunch program crashed > > Fatal signal caught! > > See http://myhost/xymon-cgi/svcstatus.sh?HOST=myhost&SERVICE=xymond

1 0

Xymon Notes Editor
by spah＠syntec.co.uk 22 Dec '17

22 Dec '17

Hi Galen, I have been trying to get your Xymon Notes Editor working. I have fixed a number of issues in the code or with your instructions, but I'm stuck on probably the last issue. Most of the issues may be caused by your code getting munged when you uploaded it to Xymonton - I'm not sure. For example I needed to add a few carriage returns: Line 24 and before 'HTML': Can't find string terminator "HTML" anywhere before EOF at /usr/share/xymon/cgi-secure/bbnote_editor.cgi line 161 As well as somewhere around: Unmatched right curly bracket at /usr/share/xymon/cgi-secure/bbnote_editor.cgi line 46, at end of line But I still have this error and I'm not sure where the issue really is because this is the end of the file: Missing right curly or square bracket at /usr/share/xymon/cgi-secure/bbnote_editor.cgi line 234, at end of line With the instructions, there should have been instructions to install perl-CGI and create the www/notes directory. Can you help with EOF right clurly or square bracket error please? And / or try re-uploading to Xymon, or posting a copy of the code for download either from this list or from somewhere else. A download saves time if anyone else wants to use this too. Many thanks, SebA

3 8

alerts.cfg question...
by goebel＠emunix.emich.edu 20 Dec '17

20 Dec '17

Hi, Using xymon-4.3.28 on SLES 11sp4, and had a hopefully quick alert.cfg question. I have the following stanza ... CLASS=TEST SERVICE=cpu COLOR=purple,red MAIL me at some.site REPEAT=120m RECOVERED DURATION>10m TIME=W:0800:2000 It alerts me when a test box goes status turns purple or red during the time window, but never sends a recovered email. It works find with our disk stanza... CLASS=TEST SERVICE=disk COLOR=purple,red MAIL me at some.siteu REPEAT=60m RECOVERED DURATION>5m TIME=W:0800:2000 Any suggestions, or are cpu alerts odd in some way? Thanks, Matt -- Matthew Goebel : goebel at emunix.emich.edu : Unix Jockey @ EMU : Hail Eris Neo-Student, Net Lurker, Donut consumer, and procrastinating medher... "Always with the negative waves, Moriarty" - Oddball "Comfort the troubled, and trouble the comfortable." - Dietrich Bonhoeffer

2 2