- Xymon - Xymon mailman web

Can custom client-side tests leverage the server-side value in analysis.cfg?
by conor＠conormccarthy.ie 13 Oct '23

13 Oct '23

> Date: Thu, 12 Oct 2023 19:23:17 -0500 > From: Grant Taylor <gtaylor at tnetconsulting.net> > To: Xymon <xymon at xymon.com> > Subject: Can custom client-side tests leverage the server-side value > in analysis.cfg? > > Hi, > > I'm relatively new to Xymon -- working with it for three months at a new > job -- and am wondering about how to have a custom client-side test > leverage the value of the server-side analysis.cfg. Yes, a simple way is to use the "config" command, this lets you download any .cfg (or arbitrary files, if ALLOWALLCONFIGFILES="TRUE" but don't do that :) files from the server's etc/ directory. client/bin/xymon $XYMONSERVER "config analysis.cfg" > tmp/analysis.cfg If you use "include" or "directory" directives in the .cfg files Xymon will send you the "flattened" expanded contents. You will need to parse that file to do anything useful though. Alternatively, fetching the hosts.cfg and using xymongrep client/bin/xymon $XYMONSERVER "config hosts.cfg" > tmp/hosts.cfg HOSTSCFG=tmp/hosts.cfg client/bin/xymongrep mytag:* might be simpler for simple configuration data that you can put in a "tag:" for each host. xymongrep is normally used server-side to loop over multiple hosts, you will likely need to match just one client name from its output for a client script. Alternatively, instead of using analysis.cfg the client-local.cfg file is logically cleaner (and automatically shipped to clients, see client/tmp/logfetch.HOSTNAME.cfg). This specifies the client-side part of log and file checks, although it's not documented, you can add arbitrary lines to this file, e.g. [myhostname] x-my-specialvarA one x-my-specialvarB two log:/var/log/message:16384 ignore MARK Each client will pick this up and store its own "personal" stanza from the global client-local.cfg, this is automatically refreshed each client run cycle. Any non-documented parameters are explicitly ignored, but best placed above any of the documented ones to make sure. > Do I /have/ /to/ declare a color in a `status` or `data` message to Xymon? status: yes (though "clear" might be an option), data: no. There's also a "modify" message you can use after the fact to change a status/colour (though take care not to trigger flapping). https://xymon.sourceforge.io/xymon/help/manpages/man1/xymon.1.html > Is there a way to have the color be determined by a value in the > server-side analysis.cfg file? > > E.g. I'd like to write a custom test to monitor /var/spool/mqueue on > multiple MTAs and I'd like to have different values for the green / > yellow / red levels on different servers. Seems like fetching the hosts.cfg and using xymongrep should work for that without too much trouble, at least as an exercise, and is reasonably self-evident. hosts.cfg: 10.1.2.3 mailhost1 # ssh smtps MAILQ:qwarn=200,qcrit=500 Then in a bash script (light on error checking) for example: client/bin/xymon $XYMONSERVER "fetch hosts.cfg" > tmp/hosts.cfg HOSTSCFG=tmp/hosts.cfg client/bin/xymongrep "MAILQ:*" | while read hostip hostname hostcfg; do if [[ "$hostname" == ${MACHINEDOTS} ]]; then mailcfg="" [[ "$hostcfg" =~ MAILQ:(.*) ]] && mailcfg="${BASH_REMATCH[1]}" for var in qwarn qcrit; do [[ "$mailcfg" =~ "($var)=([^,;]+) ]] && declare "cfg_${BASH_REMATCH[1]}"="${BASH_REMATCH[2]}" done # declare -p ${!cfg_*} ##DEBUG## # mailq logic using $cfg_qwarn $cfg_qcrit goes here # xymon status submit goes here fi done You could dispense with the outer while loop by using read hostip hostname hostcfg < <(xymongrep MAILQ:* | grep "$MACHINEDOTS") There is no xymongrep equivalent for client-local.cfg, you could adapt the above to parse the client cached copy (tmp/logfetch.HOSTNAME.cfg) - simple enough since the server does not provide the entire client-local config, just the client-specific matching stanza. I know there were some old, old mailq client scripts, there's still some RRD related residue for parsing their output in Xymon. I've never used it, but likely this was one: https://web.archive.org/web/20080718210020/http://www.deadcat.net/viewfile.… The bf/nmailq-bf.sh script therein simply barfs out a bit of sendmail's "mailq" output. The point being if you have the data in an RRD then you can also use "DS" in analysis.cfg to alert based on a GAUGE type metric. There's more than one way to skin a (dead)cat :) To scale up the configuration complexity or number of discrete service checks it would be better to dispense with xymongrep and distribute your own easy-to-parse configuration file(s), or use the client-local.cfg approach (my preference). C. > Ideally I'd like the custom client-side test that I put in > ${XYMONHOME}/ext/ to be identical across all clients and the only > difference being the value each system has in the analysis.cfg file on > the server. > > Am I /required/ to send a color; green, yellow, red, and then have > something override / update that color server side? Or can I omit the > color and let something server side set it using values for the given > client? > > I'm thinking about things like DISK / LOAD / etc. where I can set warn > and critical levels, or even ignore. > > Or am I looking at a custom server-side xymond_channel receiver that > will receive `data` (?) from the client and alter things? -- Even that > `data` is likely going to require a color. > > Would someone with more experience with Xymon than me give me a pointer > in a direction that I can go research? > > Please and thank you. > > > > -- > Grant. . . . > unix || die > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > > > ------------------------------ > > End of Xymon Digest, Vol 151, Issue 10 > **************************************

2 1

Can custom client-side tests leverage the server-side value in analysis.cfg?
by gtaylor＠tnetconsulting.net 13 Oct '23

13 Oct '23

Hi, I'm relatively new to Xymon -- working with it for three months at a new job -- and am wondering about how to have a custom client-side test leverage the value of the server-side analysis.cfg. Do I /have/ /to/ declare a color in a `status` or `data` message to Xymon? Is there a way to have the color be determined by a value in the server-side analysis.cfg file? E.g. I'd like to write a custom test to monitor /var/spool/mqueue on multiple MTAs and I'd like to have different values for the green / yellow / red levels on different servers. Ideally I'd like the custom client-side test that I put in ${XYMONHOME}/ext/ to be identical across all clients and the only difference being the value each system has in the analysis.cfg file on the server. Am I /required/ to send a color; green, yellow, red, and then have something override / update that color server side? Or can I omit the color and let something server side set it using values for the given client? I'm thinking about things like DISK / LOAD / etc. where I can set warn and critical levels, or even ignore. Or am I looking at a custom server-side xymond_channel receiver that will receive `data` (?) from the client and alter things? -- Even that `data` is likely going to require a color. Would someone with more experience with Xymon than me give me a pointer in a direction that I can go research? Please and thank you. -- Grant. . . . unix || die

1 0

Could not determine size of directory
by kspringer＠innovateteam.com 05 Oct '23

05 Oct '23

Anyone have a clue why the following folder size can't be determined when I add it to analysis.cfg and client-local.cfg ? "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS" Could not determine size of directory "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS" These other folders are working fine. C:\inetpub\logs C:\Windows\Temp C:\Windows\Logs\CBS C:\ProgramData\Microsoft\Windows\WER The only difference I see is spaces in the path.? I've put "" around it, but that doesn't seem to fix it. Does someone have a working example that includes spaces in the path? -- Kris Springer

4 6

Xymon social media presences
by cleaver＠terabithia.org 05 Oct '23

05 Oct '23

Along the lines of the previous update, I've reactivated a Facebook page that I'd set up for the project a long while back (which FB had hidden over time), as well as created handle accounts on various social media services: https://facebook.com/XymonMonitor New accounts have been created here, primarily for #hashtag and @account reference purposes at the moment: https://twitter.com/XymonMonitor https://instagram.com/XymonMonitor https://reddit.com/u/XymonMonitor In addition, there are a few resource groups out there, including: https://www.linkedin.com/groups/2776122/ - XymonAdmins (unlisted) https://www.xymon.jp/ - Japanese Xymon User Group - https://www.facebook.com/groups/126643144159684/ - Using hashtag #xymonjp on Twitter One thing I've noticed is that Xymon looks to be a rather common name in some countries, which does make direct searching a little difficult. "Xymon Monitor" seems to be something a bit more trackable (with the full name "Xymon Systems and Network Monitor" as entitled on our SF page), but we might have to see in the future what references become useful more organically. Nevertheless, hopefully this is a start. Feel free to like/comment/tag/subscribe/share/etc these in the future. Regards, -jc

3 4

Bug in Mailman version 2.1.29: We're sorry, we hit a bug!
by bruno.manzoni＠ubi-network.ch 04 Oct '23

04 Oct '23

Hi Henrik, JC, I did try to confirm that thers is a problem or not with the mailing list: So I try to subscribe to the mailing list and I receive this message: ------------------------ Bug in Mailman version 2.1.29 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs or the web server logs. ------------------------ *This seems to confirm that, people are currently unable to subscribe* And maybe also as Liang, Ye-Fee wrote: "and now find myself *unable to email to the mailing list*" (29.9.2023) Norbert wrote "*It is not possible to sign up for the Xymon user group anymore *(we are long time users and can comment, but no new users are allowed). If someone can take over this mail service this would be more important then code updates imho, to show that the project is still alive. (14.8.2023) I am pretty sure this is not normal and would propose you my help (if you need it) to resolve this problem Let me know what I can do. I will also contact mailman3.com? a make you a summary. Bruno

2 1

svcstatus.cgi
by Christoph.Mueller＠dwd.de 29 Sep '23

29 Sep '23

Dear all, I hope you can give a hint. Xymonserver (4.30-3.el9) is installed on an alma Linux Server an running fine. There is an output in /var/log/messages every 5 minutes which looks like this: "kernel: traps: svcstatus.cgi[3519701] general protection fault ip:411288 sp:7ffcbdd46878 error:0 in svcstatus.cgi[402000+23000]" Any ideas where to start my investigations? Thanks a lot. Best regards Christoph Christoph M?ller DWD Offenbach /Germany

2 1

Terabithia - Certificate expired
by john.horne＠plymouth.ac.uk 27 Sep '23

27 Sep '23

Hi, Seeing a few of these: Curl error $60$: SSL peer certificate or SSH remote key was not OK for https://repo.terabithia.org/rpms/xymon/el9/x86_64/repodata/repomd.xml [SSL certificate problem: certificate has expired] John. -- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [https://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

2 1

Case sensitivity in host+svc names
by cleaver＠terabithia.org 25 Sep '23

25 Sep '23

Curious if anyone out there has run into issues resulting from case sensitivity in hostnames (either self-report from the clientlog, or in hosts.cfg) or test names. Although I imagine this is fairly uncommon in the Linux/BSD world, I've seen AIX and Solaris systems with mixed-case hostnames, and I imagine users of BBWin can run into this a lot. Have you had issues with graphs not displaying, or any mismatch from filesystem assets (like static-generated status HTML pages or notes) that become unavailable after a name change? Or analysis.cfg or custom xymondboard queries failing? Looking at the PCRE->PCRE2 transition, there are a few places where case options are called out differently. If xymon were to canonically store/convert to lowercase internally that would help keep things cleaner, and also allow a lot of strcasecmp's in xtree lookups to become strcmp's. Regards, -jc

2 1

Monitoring SQL certs
by driley＠malone.edu 18 Sep '23

18 Sep '23

Hello, We are using Xymon to monitor our web server, and of course the https test works well watching those certs. We are moving toward using certs in MS SQL for encryption. Does anybody have a way to monitor those within xymon? Thanks. Dennis Riley IT Systems Administrator Malone University 2600 Cleveland Ave. NW Canton, Ohio 44709

2 3

/snap/core/* Filesystems NOT ok
by metron6＠gmail.com 11 Sep '23

11 Sep '23

hello all, i have the known problem with /snap/* Mon Sep 4 14:33:50 EEST 2023 - Filesystems NOT ok [image: red] /snap/core/15511 (100% used) has reached the PANIC level (95%)[image: red] /snap/core20/1974 (100% used) has reached the PANIC level (95%)[image: red] /snap/certbot/3024 (100% used) has reached the PANIC level (95%)[image: red] /snap/certbot/2913 (100% used) has reached the PANIC level (95%)[image: red] /snap/core20/2015 (100% used) has reached the PANIC level (95%)[image: red] /snap/core/15925 (100% used) has reached the PANIC level (95%) Filesystem 1024-blocks Used Available Capacity Mounted on /dev/sda1 98497780 25367880 68080352 28% / tmpfs 5120 4 5116 1% /run/lock /dev/loop1 121088 121088 0 100% /snap/core/15511 /dev/loop0 65024 65024 0 100% /snap/core20/1974 /dev/loop2 45440 45440 0 100% /snap/certbot/3024 /dev/loop3 45696 45696 0 100% /snap/certbot/2913 /dev/loop6 65024 65024 0 100% /snap/core20/2015 /dev/loop4 108416 108416 0 100% /snap/core/15925 I added this to my analysis.cfg no good... HOST=* DISK %^/snap IGNORE INODE %^/snap/.+ IGNORE this is my default analysis.cfg CLASS=linux # Ignore some usually uninteresting tmpfs mounts. DISK /dev IGNORE DISK /snap IGNORE DISK /lib/init/rw IGNORE DISK /sys/fs/cgroup IGNORE DISK %^/run/user/\d+$ IGNORE INODE /dev IGNORE INODE /snap IGNORE INODE /lib/init/rw IGNORE INODE /sys/fs/cgroup IGNORE INODE %^/run/user/\d+$ IGNORE DEFAULT # Ignore some usually uninteresting tmpfs mounts. DISK /dev IGNORE DISK /dev/shm IGNORE DISK /lib/init/rw IGNORE DISK /run IGNORE # These are the built-in defaults. You should only modify these # lines, not add new ones (no PROC, DISK, LOG ... lines). UP 1h LOAD 5.0 10.0 DISK * 90 95 INODE * 70 90 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97 -- regards, George Michalopoulos born & raise @ Metron 6 (six) Metron6 at gmail.com

5 4