July 2020 - Xymon - Xymon mailman web

Where are xymonproxy errors?!
by jeremy＠laidman.org 28 Jul '20

28 Jul '20

Rodrigo Disclaimer: I don't use xymonproxy, so I'm having a bit of a guess as to what might be wrong and what to look for. Typically xymonproxy is allowed to send messages to STDOUT and STDERR, which are redirected by the LOGFILE parameter in tasks.cfg to $XYMONSERVERLOGS/xymonproxy.log (same directory as xymond.log, on my servers it's /var/log/xymon/). However it can be run with the "--logfile <filepath>" switch, to specify another location. The errprintf() function calls send to STDERR, so should go to the logfile, whatever that is. Perhaps if you run something like, "sudo lsof -p `pgrep -f xymond_proxy`" you will be able to see what filename is bound to file descriptors 1 and 2. It could be that there's not a lot of logging going on anyway. Perhaps edit tasks.cfg and edit the entry for [xymonproxy] to append "--debug" onto the CMD command line, to increase the chance of getting a log entry. Failing that (or as well as), append an invalid switch value (eg "--listen=999.999.999.999:999") so that it has no choice to log an error and die. Or even simpler, send a HUP signal to the process, which should cause the message "Caught SIGHUP, reopening logfile" to be logged. I'd expect it to log "Attempting recovery from write error" or "Connect to server failed: <servername> - retrying" in your situation. But it could be that a failed connection is not detected until the next time a message is ready to be sent to the server. Could it be possible that the USR1 signal was sent to the process at some point? Apparently this toggles the logging of details, and without this logging, you might not see as much. Cheers Jeremy On Tue, 12 May 2020 at 10:16, Rodrigo Borges Pereira < rodrigoborgespereira at gmail.com> wrote: > Hi there, > > So, I'm trying to run xymonproxy as a standalone daemon, to facilitate the > broadcast of status messages to multiple xymon servers with a single local > machine listener. > > And that is working very well, I must say. > > But.. if one of the xymon servers is unreachable.. (I'm testing with an > iptables DROP on the server side) I don't see any errors at all from > xymonproxy. Even running it in foreground in the shell, nada. > > I've looked at the code on GitHub, and I do see some errprintf calls I > would expect would result in some output in this type of situation. > > Am I missing something? > > Appreciate any pointers, thanks in advance. > > Rodrigo > > > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

1 0

mq.sh script
by neilsimmonds1808＠gmail.com 27 Jul '20

27 Jul '20

Hi all, I'm seeing some really strange behaviour from the MQ.SH script/ We have the standard mq.sh script that comes with Xymon and we have it setup in /xymon/client/etc/clientlaunch.cfg as follows [mq] ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg CMD $XYMONCLIENTHOME/ext/mq.sh queuemanagername LOGFILE $XYMONCLIENTLOGS/xymonmq2client.log INTERVAL 1m The behaviour that we are seeing is that,as expected MQ.SH writes nothing in the way of errors into xymonmq2client.log but what it does write into there is the contents of /xymon/client/tmp/logfetch.hostname.cfg (i.e. log:/applogs/broker/broker.log:20480 ignore MARK ) I'm at a loss to explain this so am reaching out to the list to see if anyone has come across this Regards, Neil.

2 1

Alerts not working as expected
by companydavid49＠gmail.com 24 Jul '20

24 Jul '20

Hi, My Alerts are Not Working as expected. I have The following in my hosts.cfg and my alerts.cfg. The result I'm after is that the Servers in the DoNotAlert subpages should not alert but the pages in subpage Alerts must. Currently, they are all alerting despite the EXPAGE setting in the alerts.cfg file. When I switch off any of them the conn sends an alert no matter what permutations I try. Any help would be appreciated. *host.cfg*page Prod Prod Hosts subpage Alert Alert 0.0.0.0 .default. # NOPROPRED:* NOPROPPURPLE:* NOPROPYELLOW:* 127.0.0.1 prod1.domain.com # conn subpage DoNotAlert DoNotAlert 127.0.0.2 prod2.domain.com # conn subpage DoNotAlert1 DoNotAlert1 127.0.0.3 prod3.domain.com # conn *alerts.cfg* COLOR=red EXPAGE=Prod/DoNotAlert EXPAGE=Prod/DoNotAlert1 SCRIPT /usr/share/xymon-client/ext/Notifications/notifications.sh <emailaddress> REPEAT=1h TIME=W:0700:1700

2 1

xymonpsclient CPU utilisation graph
by rcohen55＠gmail.com 22 Jul '20

22 Jul '20

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20200721/8b5f460a/attach…>

4 6

Alert for WHO column possible?
by mark-rankin＠hotmail.com 21 Jul '20

21 Jul '20

Hi, Am new to this mailing list, but not new to Xymon. Awesome tool and have been using it for many years! This said, have probably only ever needed to scrape the surface of deeper capabilities and features. Is it possible to monitor for a user being logged in (who column) and go red if that user is not logged in? Unfortunately, we have a few servers that need to be logged in (sigh....) with a certain user and it would be neat to see if they were not. Example under "Who": SESSIONNAME USERNAME STATE >Console svcaccount Active Test would be that if svcaccount is not present, go red. I have read that I might be able to use DS override in analysis.cfg, have never created an RRD file before, but is that is a feasible approach? Xymon version 4.3.30 CentOS 6.10 Thanks! Kind Regards, Mark Rankin

3 3

acknowledge.sh / acknowledge.cgi list incomplete
by lk＠man-da.de 20 Jul '20

20 Jul '20

Hi List, today I noticed we are missing some alerts in the List displayed by acknowledge.sh or more in background acknowledge.cgi. As far as I see size of this list is hardcoded to 16 hosts, but since also hosts tagged with nonongreen are listed there this is to few. ;-) Any ideas? Kind regards, Lars -- Lars Kollstedt Telefon: +49 6151 16-71027 E-Mail: lk at man-da.de man-da.de GmbH Dolivostra?e 11 64293 Darmstadt Sitz der man-da.de GmbH: Darmstadt Amtsgericht Darmstadt, HRB 9484 Gesch?ftsf?hrer: Andreas Ebert

1 0

How to add Xymon libs exceptions for this Ubuntu 20.20 bummer
by pto＠linuxbog.dk 17 Jul '20

17 Jul '20

After booting my Ubuntu 20.20 box I have this dead process every time root 401 0.0 0.0 2488 588 ? S Jul14 0:00 bpfilter_umh This annoys Xymon on the SERVICE=libs page I have a dead process detected yellow The following processes have libs linked that were upgraded: root: / (deleted) (401) It seems that I can silence "noise" like this via /etc/xymon/libs.local.yaml but I cannot get the syntax right. Help :) Cheers -- Peter Toft <pto at linuxbog.dk>

2 2

Any known issues with https testing via proxy
by dmallor＠gmail.com 13 Jul '20

13 Jul '20

Trying to get https testing working via proxy and works fine via curl but xymon reports proxy 501 not implemented errors so I assume its showing up malformed. I see in sourceforce release notes a fix from 4.2 > 4.2.2 for this related to Debian but I am running above this (4.3.17) snip: Changes from 4.2.0 -> 4.2.2 =========================== *) Patches from Debian and Mandriva source archives and elsewhere have been merged, fixing: - The bb-hosts syntax for HTTP testing via a proxy could not support https target-URL's (from Debian) Thx in advance Danny

2 1

custom email alert sample
by jeremy＠laidman.org 09 Jul '20

09 Jul '20

Kris On rare occasions, we enable an SMS alerting script, using the SMS format. We added to alerts.cfg: $SendSms=/usr/local/sbin/xymon-sendsms.sh $Mobile1=0123456789 $Mobile1=0123456798 Then: HOST=%^hostname00[0-3].example.com SERVICE=conn SCRIPT $SendSMS $Mobile1 FORMAT=SMS COLOR=red REPEAT=60 DURATION>10 RECOVERED SCRIPT $SendSMS $Mobile2 FORMAT=SMS COLOR=red REPEAT=60 DURATION>10 RECOVERED The script: #!/bin/sh # This script is called by the xymon alerts sub-system (see /etc/xymon/alerts.cfg) # and simply sends an email to an Email -> SMS gateway. # The email is sent using the smtp-source program due to mail being disabled on the # Xymon server for security and reliability reasons. # This script expects the following environmental variables to be set when called: # BBALPHAMSG - The full text of the status log triggering the alert # RCPT - The recipient mobile number. LogFile="/var/log/xymon/xymon-sendsms.log" Sender="xymon@`/bin/hostname -f`" Recipient="$RCPT at sms.example.org" Server="smtp.example.org" Subject="Xymon Alert" Date="`/bin/date`" Smtp="/usr/sbin/smtp-source" { echo "Subject: $Subject" echo "Date: $Date" echo "To: $Recipient" echo "" echo "$BBALPHAMSG" } | $Smtp -M `hostname -f` -f "$Sender" -t "$Recipient" -F /dev/stdin $Server echo "$Date" >> $LogFile echo "$Recipient" >> $LogFile echo "$BBALPHAMSG" >> $LogFile echo "" >> $LogFile On Tue, 19 May 2020 at 07:06, Kris Springer <kspringer at innovateteam.com> wrote: > Hi, I've been looking into customizing the email alerts that get sent > from our xymon server. I've played with the SMS option and like the > minimal content of the body of the email, but I still want a customized > Subject and I want the alert URL included in the email body. I assume > the SCRIPT option will accomplish this. Does anyone have a simple > script that they can share? > Thanks. > > Kris Springer > > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

2 1

Is it possible to recreate rrd from hostdata?
by jeremy＠laidman.org 06 Jul '20

06 Jul '20

On Fri, 12 Jun 2020 at 01:07, Hansen, Rene H <rhansen21 at dxc.com> wrote: > Hi > > > > In one of my Xymon systems the rrd status and rrd data processes was > consuming 100% cpu and was crashing/restarting in a loop due to > misconfiguration. > Argh. I hate that. > This resulted in a gap in my rrd files and missing data when running > perfdata.cgi report. > My OCD-ish tendencies dislike gaps in the graphs. On the other hand, the graphs tell a story, just not about the target host. > Is there an easy way to run rrd manually on hostdata to fill out the gaps > in the rrd files? > Short answer: no. Long answer: not an easy way, and not a reliable way. The hostdata has the necessary information required to replicate only some RRD data points, and only for some tests. Tests like CPU and DISK are populated from data in the client data messages sent from the hosts, so there's a possibility of some useful data for those (you can tell which tests are created from client data messages because there's a "Client data available" link at the bottom of the page). However, hostdata is only saved for a host when a test changes to an alert state. (This is described in the man page for xymond_hostdata.) So, unless you had a new fault every 5 minutes, the hostdata snapshot files will be missing data. Let's assume you can find enough hostdata entries to be useful. You'd then need to get the data into the RRD file. This means either a) parsing the data yourself (eg in a python script) and sending the data to the RRD file using rrdtools, or b) sending the data to Xymon to parse. Problems with these approaches: a) using rrdtools: rrdupdate warns/ignores data points that are earlier than the most recent update, so you would need to do a dump/edit/restore cycle, or perhaps truncate the data in the RRD file up to the point you wanted to start, then add the parsed hostdata and then re-add the data points that were truncated. Parsing wouldn't be trivial, because Xymon has hundreds (probably thousands) of lines of code that know how to parse the data in the right way, and you'd have to re-implement this code yourself. b) using xymon: you can send a client data message to xymond, and it will parse it using all using the xymond_client worker module (you may be able to run this directly), but there's no guarantee that Xymon won't discard the data because it's too old, and even if it didn't, you'd still have to work around the rrd restriction as per a) above where data points are discarded if older than the most recent. I have two Xymon servers. It's rare that one goes down, but if it does, I can dump/splice/restore and re-create the missing RRD data on the server that went down using the RRD data on the server that didn't. DISCLAIMER: Although I've used this procedure to remove a massive spike caused by a processing artefact (thus rendering the graph useless due to the scale), I've not done this to fill in gaps. Cheers Jeremy

2 1