November 2017 - Xymon - Xymon mailman web

Http Status Column and Https
by rich＠corporationpop.co.uk 08 Nov '17

08 Nov '17

Hi all, Have finally got around to upgrading our Xymon installation, mostly all good (still some plugins and extensions to add in), however I'm seeing a strange issue where the http test is returning a HTTP/1.1 400 Bad Request for all sites using https. This used to work in our previous (admittedly VERY out-of date) instance. Any ideas? Hosts.cfg looks something like this for the affected rows: 1.2.3.4 someurl.com # https://someurl.com COMMENT:somecomment While I'm at it, I can't recall how to get the ssl certificate test to work and show the expiry dates, is this related? Cheers, Rich

2 5

XYmon doing Cricket's job
by scarville＠lereta.com 07 Nov '17

07 Nov '17

I have about a dozen interfaces I want to monitor total traffic on, Right now I use Cricket for this but that server is running CentOS 5 and I am shutting it down as soon as possible. Can XYmon take over this task or should I just move Cricket over?

2 2

Xymonfetch, msgcache and personal scripts
by pierre.lapha＠gmail.com 02 Nov '17

02 Nov '17

Hello all, I managed to make the xymonfetch work through a ssh tunnel and the default tests are now visible in the xymon page (thanks to Thomas and John). But I have personal scripts that I used to launch via clientlaunch.cfg and I do not know how to tell the script to write data locally (in msgcache) instead of sending the datas to the xymon server. Thank you again for your help. Pierre

2 1

Top output not current for host app129015.sjc5
by mike.smith＠servicenow.com 02 Nov '17

02 Nov '17

Hi, Attempting to view TOP output by going to CPU-->Service History-->(Full HTML log) Link: https://monitor01.iad9.service-now.com/xymon-cgi/history.sh?HISTFILE=app129… This shows no data since October 10 and yet there was Datacenter alert for high CPU yesterday: Alert63284041<https://datacenter.service-now.com/em_alert.do?sys_id=05add5e7dbc28b402b157…> Here is another link shows crazy high CPU for an app node on this host yesterday: https://stats.servicenow.net/instance_view?impala=true&selection=metlifepro… I’ve not checked other application nodes, but was curious what’s up? Thanks, Mike

2 2

missing information
by thannhi.nguyen＠solvay.com 02 Nov '17

02 Nov '17

Hello, A few of our client servers didn't show information for a few columns, and they all have Aspen IP21 running on them. Those servers with IP didn't have any issue. We thought it may be firewall related issue, but if that was the case, then no information should show up at all. We couldn't figure out why. Could you give us some hint? *Best regards,* *ThanNhi Nguyen* *IS MES Support* *3737 Buffalo Speedway* *Houston, TX 77098-3701T: 1-713-525-6740M: 1-713-247-9278* [image: SOLVAY] www.solvay.com -- *This message and any attachments is intended for the named addressee(s) only and may contain information that is privileged and/or confidential. If you receive this message in error, please delete it and immediately notify the sender. Any copying, dissemination or disclosure, either whole or partial, by a person who is not the named addressee is prohibited. We use virus scanning software but disclaim any liability for viruses or other devices which remain in this message or any attachments.*******************************Ce message, ainsi que toute piece jointe, est exclusivement adresse au(x) destinataire(s) nomme(s) et peut contenir des informations confidentielles. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'emetteur. Toute copie, transmission ou divulgation, integrale ou partielle, par une personne qui n'est pas nommee comme destinataire est interdite. Nous utilisons un logiciel anti-virus mais nous denions toute responsabilite au cas ou des virus, ou tout autre procede, seraient contenus dans ce message ou toute piece jointe.*

2 5

[XYMON] agents with pulldata - xymonfetch and ssh tunelling
by pierre.lapha＠gmail.com 02 Nov '17

02 Nov '17

Hello, I am trying to set up xymonfetch/msgcache with ssh tunnelling (because security does not want to open flows on port 1984). I have enabled xymonfetch (in tasks.cfg) and added pulldata (in hosts.cfg) on server side and also msgcache (in clientlaunch.cfg) and XYMSRV=127.0.0.1 (in xymonclient.cfg). I have done a ssh tunnel (ssh -L 1234:127.0.0.1:1984 IP_of_the_client) from the xymon server. My tunnel is ok but xymon logs still show that nothing happens, no pulldata. Is there something else I should do to enable this function? Any help would be appreciated. Thank you! Pierre

3 5

Bogus hosts filling up alert.log
by David.Mills＠hhsc.state.tx.us 01 Nov '17

01 Nov '17

Hi, all! I have recently set up a new Xymon (Xymon 4.3.28-1.el6.terabithia<http://xymon.sourceforge.net/>) server on RHEL 6.7 that, for the most part, is doing just fine. However, I've discovered that my /var/log/xymon/alert.log file is growing at a crazy rate to the point it periodically needs to zero'd-out or it will swamp the file system. The problem is every 15 seconds the /var/log/xymon/alert.log file receives a flurry of log entries like this: ... 2017-10-31 14:53:55 Checking criteria for host '0FS_94_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_94_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_94_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_94_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_94_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_94_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_94_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_94_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_95_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_95_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_95_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_95_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_95_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_95_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_95_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_95_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_96_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_96_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_96_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_96_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_96_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_96_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_96_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire 2017-10-31 14:53:55 Checking criteria for host '0FS_96_192_168_22_1__export_', which is not yet defined; some alerts may not immediately fire ... The '0FS_96_192_168_22_1__export_' is actually the name of a host I've defined in the past, but is no longer in xymon's memory (AFAIK!!) I have reduced the alerts.cfg down to a minimal stub, commenting out the "directory /etc/xymon/alerts.d/..." directive, "rm -r"'d any reference to this host (and others similar to it) under the data files directories (e.g. rrd/, hist/, histlogs/, hostdata/, etc.). I have gone as far as running "find /etc/xymon -type f | xargs egrep 0FS_" looking for "surprises". I've also stopped / restarted the server and scanned what's active in memory via "xymon localhost xymondboard | egrep 0FS_". This "host" is not a real client host but an artifact I've created on the server side to represent a file system I'm monitoring in a server-side ext script, so I know it is not announcing it's presence over port 1984. For the life of me I can't figure out where the alerts daemon is running across this hostname. Help? ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ David Mills Systems Administrator Northrop Grumman (512) 595-1238 (mobile)

3 7

flapping status and emailed alerts
by Phil.Crooker＠orix.com.au 01 Nov '17

01 Nov '17

?We've had a web server flapping recently which is fine, but with an alert DELAY>10 set, we tend to get emailed alerts showing the status happens to be green (when the message was sent), yet that service is red because of the flapping. The default alert message (which shows the http response) doesn't mention flapping which causes some confusion. Is there a way to show the alert was sent because of flapping without writing my own alert script and message? Yes, I can turn set the service to noflap, but that is not optimal as I do want to know when that is occurring. ta, Phil

1 0