- Xymon - Xymon mailman web

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

xymon "hostinfo" does not honour tags set by `.default.`
by thomas.eckert＠it-eckert.de 31 Oct '17

31 Oct '17

Brothers, I found that the information returned by `xymon 127.0.0.1 "hostinfo"` does not honour tags by `.default.`. Steps to reproduce: root at pi3:/etc/xymon# egrep -i 'default|pi3' hosts.cfg 0.0.0.0 .default. # nosslcert 127.0.0.1 pi3 # bbd http://pi3/ root at pi3:/etc/xymon# xymon 127.0.0.1:1984 "hostinfo host=^pi3" pi3|127.0.0.1|bbd|http://pi3/ (note the missing `nosslcert`-tag) Not using `.default.` the correct set of tags is returned: root at pi3:/etc/xymon# egrep -i 'default|pi3' hosts.cfg 127.0.0.1 pi3 # bbd http://pi3/ nosslcert root at pi3:/etc/xymon# xymon 127.0.0.1:1984 "hostinfo host=^pi3" pi3|127.0.0.1|bbd|http://pi3/|nosslcert This makes `hostinfo` not a usable source for getting the monitoring configuration for hosts or prevents the use of `.default.`. All the best Thomas

3 2

Graphing Question
by dl1025＠att.com 27 Oct '17

27 Oct '17

I was hoping you can give me some advice in regard to graphing data. I have data coming in that is posted in xymon with HTML tags. I need to parse the data out and post it into rrdtool then display it on the status page. I am fairly new to xymon, in BB I used bb-larrd.pl to parse the data and post it into rrd. What is the best way of doing it in xymon? I think there are several ways of accomplishing this in xymon if I am not mistaken: 1. As the data comes into xymon and displays on the status message, I can parse out the data that I need and send it through the rrd channel 2. I could also within the script that generates the data include an rrd module that will create the rrd file and post the results that I need directly to the rrdtool, but then I need to include it where so it can appear on the status page Any suggestions will be greatly appreciated. Here is an example of the data that I want to graph. This is how it appears on the status page. Orders in DF staging table by Process Flag Org Creation Date Process Flag Reqs with no Orders [red]FDC 10/19/17 P 458 [red]MDC 10/19/17 P 3249

2 1

not generate webpage in xymon
by ajitsurat＠gmail.com 27 Oct '17

27 Oct '17

not generate webpage in xymon help me

2 1

terabithia rpm repo is broken
by Scot.Kreienkamp＠la-z-boy.com 26 Oct '17

26 Oct '17

Hi JC, It looks like the Terabithia rpm repo is broken. It keeps redirecting you until the allowed number of redirects are exhausted. It redirected me to this: https://terabithia.org/rpms/xymon/rpms/xymon/rpms/xymon/rpms/xymon/rpms/xym… Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | * 734-384-6403 | | * 7349151444 | * Scot.Kreienkamp at la-z-boy.com<mailto:%7BE-mail%7D> www<http://www.la-z-boy.com/>.la-z-boy.com<http://www.la-z-boy.com/> | facebook.<https://www.facebook.com/lazboy>com<https://www.facebook.com/lazboy>/<https://www.facebook.com/lazboy>lazboy<http://facebook.com/lazboy> | twitter.com/lazboy<https://twitter.com/lazboy> | youtube.com/<https://www.youtube.com/user/lazboy>lazboy<https://www.youtube.com/user/lazboy> [cid:lzbVertical_hres.jpg] This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.

2 1

how to monitor SharePoint Online with Xymon
by storerr＠nibco.com 23 Oct '17

23 Oct '17

Kris, please have a look at the Microsoft Graph API https://docs.microsoft.com/en-us/azure/active-directory/develop/active-dire… If you don't find the above useful, please provide more specifics on exactly what you want to monitor in your reply. Ray Storer NIBCO INC. | Intel Systems Specialist P: 574.295.3457 | F: 574.295.1298 | M: 574.742.0192 storerr at nibco.com | www.nibco.com -----Original Message----- Date: Mon, 16 Oct 2017 13:49:28 -0700 From: Kris Springer <kspringer at innovateteam.com> To: Xymon MailingList <xymon at xymon.com> Subject: [Xymon] how to monitor SharePoint Online with Xymon Message-ID: <c4de5e5e-38e7-cf69-239f-1ac1ef720aae at innovateteam.com> Content-Type: text/plain; charset="utf-8" An HTML attachment was scrubbed... URL: <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xymon…> ________________________________ CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.

2 2

request: xymonnet lookup failure of fully qualified name ending in .local with dialup tag shouldn't be an error
by rlhamil2＠gmail.com 22 Oct '17

22 Oct '17

Given that .local is reserved for Multicast DNS https://en.wikipedia.org/wiki/.local#Multicast_DNS_.28mDNS.29_standard <https://en.wikipedia.org/wiki/.local#Multicast_DNS_.28mDNS.29_standard> which is usually resolved by a response by the host in question to a multicast query, if the host is tagged "dialup", it seems to me that it should not be an error (i.e. not of itself cause xymonnet's status to go yellow). If an MDNS name isn't resolvable, and the host is tagged as dialup...heck, it's probably perfectly normal. When my laptop (named "lapple") is at home, lapple.local resolves; when it isn't, it doesn't resolve*. In other words, I'm asking for a special case of treating unresolvable the same as unreachable only when all of three conditions apply: name has 0.0.0.0 in hosts.cfg (external resolution); name ends in .local; "dialup" tag present. A fourth condition - that xymonnet was run with the --no-ares option (or building without c-ares support, I suppose) could also be applied, in the non-recommended case of someone having .local resolved by an internal unicast DNS server. * something might be responding on its behalf, but that's not the norm.

1 0