October 2020 - Xymon - Xymon mailman web

MSGS Alert question
by ralphmitchell＠gmail.com 13 Oct '20

13 Oct '20

Simplest method would be to use the SCRIPT option. A variety of environment variables are loaded with the message, the color, and other info, then the script is invoked. You can make the script as smart as you need it to be. For example, I have a disk alert script that sends email to the DBAs for some filesystems and to SysAdmins for others, depending which one causes the alert. Ralph Mitchell On Tue, Oct 13, 2020 at 1:12 PM Neal, Jonathan W via Xymon <xymon at xymon.com> wrote: > > > > ---------- Forwarded message ---------- > From: "Neal, Jonathan W" <wes.neal at verizon.com> > To: xymon at xymon.com > Cc: > Bcc: > Date: Tue, 13 Oct 2020 12:57:09 -0400 > Subject: MSGS Alert question > Is there a way to send an alert for some MSGS problems you receive, but > not all? Meaning I receive Messages A, B and C in Xymon as issues and I > email on all three, but I want to send a different email alert on C as well. > > Thanks! > > > > ---------- Forwarded message ---------- > From: "Neal, Jonathan W via Xymon" <xymon at xymon.com> > To: xymon at xymon.com > Cc: > Bcc: > Date: Tue, 13 Oct 2020 12:57:09 -0400 > Subject: [Xymon] MSGS Alert question > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

1 0

MSGS Alert question
by wes.neal＠verizon.com 13 Oct '20

13 Oct '20

Is there a way to send an alert for some MSGS problems you receive, but not all? Meaning I receive Messages A, B and C in Xymon as issues and I email on all three, but I want to send a different email alert on C as well. Thanks!

1 0

Too much data for svcstatus.sh?
by mburger＠bubbanfriends.org 12 Oct '20

12 Oct '20

Good morning. Running Xymon 4.3.30, compiled from source tarball, on a RHEL 6.10 server. This morning, I encountered an interesting issue. I have a monitored system that has 197 discrete filesystems/mounts. When I attempt to enter this server's "Trends" section, I receive an internal server error (500). My httpd error log shows this when I attempt to access the trends link for the server in question: [Thu May 21 11:29:41 2020] [error] [client 10.40.24.55] Premature end of script headers: svcstatus.sh, referer: http://sysmon.fhmc.local/xymon/edmprod/edmprod.html [Thu May 21 11:29:59 2020] [error] [client 10.40.24.55] *** glibc detected *** /apps/xymon/server/bin/svcstatus.cgi: realloc(): invalid next size: 0x0000000000de7dd0 ***, referer: http://sysmon.fhmc.local/xymon/edmprod/edmprod.html [Thu May 21 11:29:59 2020] [error] [client 10.40.24.55] /apps/xymon/server/bin/svcstatus.cgi[0x408a4f], referer: http://sysmon.fhmc.local/xymon/edmprod/edmprod.html [Thu May 21 11:29:59 2020] [error] [client 10.40.24.55] /apps/xymon/server/bin/svcstatus.cgi[0x403453], referer: http://sysmon.fhmc.local/xymon/edmprod/edmprod.html [Thu May 21 11:29:59 2020] [error] [client 10.40.24.55] /apps/xymon/server/bin/svcstatus.cgi[0x404bb7], referer: http://sysmon.fhmc.local/xymon/edmprod/edmprod.html [Thu May 21 11:29:59 2020] [error] [client 10.40.24.55] /apps/xymon/server/bin/svcstatus.cgi[0x4022c9], referer: http://sysmon.fhmc.local/xymon/edmprod/edmprod.html [Thu May 21 11:29:59 2020] [error] [client 10.40.24.55] 00400000-0043c000 r-xp 00000000 fd:08 24906 /apps/xymon/server/bin/svcstatus.cgi, referer: http://sysmon.fhmc.local/xymon/edmprod/edmprod.html [Thu May 21 11:29:59 2020] [error] [client 10.40.24.55] 0063c000-0063e000 rw-p 0003c000 fd:08 24906 /apps/xymon/server/bin/svcstatus.cgi, referer: http://sysmon.fhmc.local/xymon/edmprod/edmprod.html This does not happen for any other monitored system in my environment. This system is one of the more critical servers in my environment, so I'd like to figure out what's going on and remediate it if possible. -- Mike Burger http://www.bubbanfriends.org "It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1

4 4

"noconn" configuration feature oddity ...
by jeremy＠laidman.org 06 Oct '20

06 Oct '20

Ian An interesting discovery indeed. Although I'm not greatly surprised. A host that has no tests and has never had any test results, is not a particularly interesting one, and is rather like a tree falling in an uninhabited forest, where nobody knows - or even cares - about the state of the tree. I'd attribute this phenomenon to the type of "undefined behaviour" that can occur when any process is asked to do something it wasn't designed to do and which, in essence, makes no sense. Unless I'm missing something. Cheers Jeremy On Mon, 5 Oct 2020 at 23:33, Ian Diddams via Xymon <xymon at xymon.com> wrote: > > > > ---------- Forwarded message ---------- > From: Ian Diddams <didds3 at yahoo.co.uk> > To: "xymon at xymon.com" <xymon at xymon.com> > Cc: > Bcc: > Date: Mon, 5 Oct 2020 11:53:01 +0000 (UTC) > Subject: "noconn" configuration feature oddity ... > A colleague and I noticed a feature of xymon last week, and tested it > across a few version from 4.3.12 to 4.3.17 [ upgrading etc etc is not a > trivial matter in these environments so its meaningless to just suggest > "upgrade asap" - although see [1] for general feedback etc ]. > > If a new host is added to hosts.cfg with a noconn configuration in a new > group or page configuratiopn > > eg > > > page test Test > group-compress <H3>Test</H3> > 4.5.6.7 test # noconn > > that server NEVER appears in the webpage as expected, although the new > group does appear albeit then empty > > If it is introduced without that noconn parementer then it does as > expected appear. Then adding noconn to it subsequently does indeed drop > the conn column and reproting then continues as normal. > > > We have also found that specifying noping instead of noconn does include > the server in the webpage with a white face in the conn column - ie it does > get included, so is maybe a work round at least) > > However... > > adding > > 4.5.6.7 test # noconn > > to an already existing group/page - that server DOES get listed but with > no subsequent tests against it - the line remains empty > > This would appear to be a feature of xymon Ive not come accrioss in 9+ > years of using it. > > [1] Anybody found any other "fixes" to be ablwe to sepcify noconn from the > outset? > > I've googled but nothing appears to match that - though that could just be > my rubbish googling skills... > > > UPDATE: deeper wierdness... if i add a eg ssh test to that hosts.cfg > line ... then the server DOES get added... > > cheers > > ian > > > > > > > > ---------- Forwarded message ---------- > From: Ian Diddams via Xymon <xymon at xymon.com> > To: "xymon at xymon.com" <xymon at xymon.com> > Cc: > Bcc: > Date: Mon, 5 Oct 2020 11:53:01 +0000 (UTC) > Subject: [Xymon] "noconn" configuration feature oddity ... > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

3 2

"noconn" configuration feature oddity ...
by didds3＠yahoo.co.uk 05 Oct '20

05 Oct '20

A colleague and I noticed a feature of xymon last week, and tested it across a few version from 4.3.12 to 4.3.17?? [ upgrading etc etc is not a trivial matter in these environments so its meaningless to just suggest "upgrade asap" - although see [1] for general feedback etc ]. If a new host is added to hosts.cfg with a noconn configuration in a new group or page configuratiopn eg page test Test group-compress <H3>Test</H3> 4.5.6.7 test #? noconn that server NEVER appears in the webpage as expected, although the new group does appear albeit then empty If it is introduced without that noconn parementer then it does as expected appear.? Then adding noconn to it subsequently does indeed drop the conn column and reproting then continues as normal. We have also found that specifying noping instead of noconn does include the server in the webpage with a white face in the conn column - ie it does get included, so is maybe a work round? at least) However... adding 4.5.6.7 test #? noconn to an already existing group/page - that server DOES get listed but with no subsequent tests against it - the line remains empty This would appear to be a feature of xymon Ive not come accrioss in 9+ years of using it.? [1] Anybody found any other "fixes" to be ablwe to sepcify noconn from the outset? I've googled but nothing appears to match that - though that could just be my rubbish googling skills... UPDATE:? deeper wierdness...? if i add a eg ssh test to that hosts.cfg line ...? then the server DOES get added...? cheers ian

1 0

xymond_rrd Fatal signal caught!
by wwheeler＠fedex.com 02 Oct '20

02 Oct '20

I have installed xymon 4.3.30 on 3 servers. I am getting core dumps fo xymond_rrd on 1 on of the servers running Xymon 4.3.30. I have search and googled this issue and all bugs I have seen so far are patched in this version. I had seen a reference possible corrupt data causing the issue, but I am unable to figure out how to track down the source. Oct 2 16:32:40 abrt-server: Executable '/opt/xymon/server/bin/xymond_rrd' doesn't belong to any package and ProcessUnpackaged is set to 'no' Oct 2 16:32:40 abrt-server: 'post-create' on '/var/spool/abrt/ccpp-2020-10-02-16:32:40-24653' exited with 1 Oct 2 16:32:40 abrt-server: Deleting problem directory '/var/spool/abrt/ccpp-2020-10-02-16:32:40-24653' Oct 2 16:33:38 abrt-hook-ccpp: Process 24963 (xymond_rrd) of user 20610 killed by SIGABRT - dumping core -bash-4.2$ gdb /opt/xymon/server/bin/xymond_rrd core.27659 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-115.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /opt/xymon/server/bin/xymond_rrd...done. [New LWP 27659] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `xymond_rrd --rrddir=/opt/xymon/data/rrd'. Program terminated with signal 6, Aborted. #0 0x00007fdcdf354377 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-13.el7.x86_64 cairo-1.15.12-4.el7.x86_64 expat-2.1.0-10.el7_3.x86_64 fontconfig-2.13.0-4.3.el7.x86_64 freetype-2.8-14.el7.x86_64 fribidi-1.0.2-1.el7_7.1.x86_64 glib2-2.56.1-5.el7.x86_64 glibc-2.17-292.el7.x86_64 graphite2-1.3.10-1.el7_3.x86_64 harfbuzz-1.7.5-2.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-37.el7_7.2.x86_64 libX11-1.6.7-2.el7.x86_64 libXau-1.0.8-2.1.el7.x86_64 libXext-1.3.3-3.el7.x86_64 libXrender-0.9.10-1.el7.x86_64 libcom_err-1.42.9-16.el7.x86_64 libffi-3.0.13-18.el7.x86_64 libgcc-4.8.5-39.el7.x86_64 libglvnd-1.0.1-0.8.git5baa1e5.el7.x86_64 libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64 libglvnd-glx-1.0.1-0.8.git5baa1e5.el7.x86_64 libpng-1.5.13-7.el7_2.x86_64 libselinux-2.5-14.1.el7.x86_64 libthai-0.1.14-9.el7.x86_64 libtirpc-0.2.4-0.16.el7.x86_64 libuuid-2.23.2-61.el7_7.1.x86_64 libxcb-1.13-1.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 pango-1.42.4-4.el7_7.x86_64 pcre-8.32-17.el7.x86_64 pixman-0.34.0-1.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-18.el7.x86_64 (gdb)

1 0

SPLITNCV with wildcard because of multiple graphs from one test
by r.oliver＠web.de 01 Oct '20

01 Oct '20

I've tested even more combinations trying to escape the asterisk with no success: SPLITNCV_nvme="temperature:GAUGE" SPLITNCV_nvme="*temperature:GAUGE" SPLITNCV_nvme="*temperature*:GAUGE" SPLITNCV_nvme="\*temperature:GAUGE" SPLITNCV_nvme="@RRDIDX at _temperature:GAUGE" SPLITNCV_nvme="p at RRDIDX@_temperature:GAUGE" SPLITNCV_nvme=".*temperature:GAUGE" SPLITNCV_nvme="%.*temperature:GAUGE" SPLITNCV_nvme="(.*)temperature:GAUGE" SPLITNCV_nvme="\.\*temperature:GAUGE" SPLITNCV_nvme="\\*temperature:GAUGE" SPLITNCV_nvme="\\\*temperature:GAUGE" SPLITNCV_nvme="\\\\*temperature:GAUGE" SPLITNCV_nvme="\\\\\*temperature:GAUGE" SPLITNCV_nvme="\\\\\\*temperature:GAUGE" SPLITNCV_nvme="\\\\\\\\*temperature:GAUGE" SPLITNCV_nvme="\\.\\*temperature:GAUGE" On the xymon side I think this information above is processed in "do_ncv.c", but I still could not find, where the string above gets parsed. Any help is appreciated. Regards Oliver Am 29.09.20 um 16:24 schrieb Oliver R.: > Dear All, > > I have a custom test that reports data from nvme disks from the command: > > nvme smart-log /dev/nvme2n1 -o json > > The output is processed so that the client reports the following to the > server: > > S3ESNX0J951626N-critical_warning : 0 > S3ESNX0J951626N-temperature : 318 > S3ESNX0J951626N-avail_spare : 100 > S3ESNX0J951626N-spare_thresh : 10 > S3ESNX0J951626N-percent_used : 92 > S3ESNX0J951626N-data_units_read : 27832088 > S3ESNX0J951626N-data_units_written : 93877408 > S3ESNX0J951626N-host_read_commands : 180442558 > S3ESNX0J951626N-host_write_commands : 916278700 > S3ESNX0J951626N-controller_busy_time : 4028 > S3ESNX0J951626N-power_cycles : 218 > S3ESNX0J951626N-power_on_hours : 2995 > S3ESNX0J951626N-unsafe_shutdowns : 86 > S3ESNX0J951626N-media_errors : 0 > S3ESNX0J951626N-num_err_log_entries : 0 > S3ESNX0J951626N-warning_temp_time : 0 > S3ESNX0J951626N-critical_comp_time : 0 > S3ESNX0J951626N-temperature_sensor_1 : 318 > S3ESNX0J951626N-temperature_sensor_2 : 323 > S3ESNX0J951626N-thm_temp1_trans_count : 0 > S3ESNX0J951626N-thm_temp2_trans_count : 0 > S3ESNX0J951626N-thm_temp1_total_time : 0 > S3ESNX0J951626N-thm_temp2_total_time : 0 > 2J4520102682-critical_warning : 0 > 2J4520102682-temperature : 314 > 2J4520102682-avail_spare : 100 > 2J4520102682-spare_thresh : 32 > 2J4520102682-percent_used : 2 > 2J4520102682-data_units_read : 9450966 > 2J4520102682-data_units_written : 24105094 > 2J4520102682-host_read_commands : 137338588 > 2J4520102682-host_write_commands : 284702582 > 2J4520102682-controller_busy_time : 0 > 2J4520102682-power_cycles : 46 > 2J4520102682-power_on_hours : 1107 > 2J4520102682-unsafe_shutdowns : 10 > 2J4520102682-media_errors : 0 > 2J4520102682-num_err_log_entries : 0 > 2J4520102682-warning_temp_time : 0 > 2J4520102682-critical_comp_time : 0 > 2J4520102682-thm_temp1_trans_count : 0 > 2J4520102682-thm_temp2_trans_count : 0 > 2J4520102682-thm_temp1_total_time : 0 > 2J4520102682-thm_temp2_total_time : 0 > S3ESNX0J951635M-critical_warning : 0 > S3ESNX0J951635M-temperature : 310 > S3ESNX0J951635M-avail_spare : 100 > S3ESNX0J951635M-spare_thresh : 10 > S3ESNX0J951635M-percent_used : 92 > S3ESNX0J951635M-data_units_read : 32693378 > S3ESNX0J951635M-data_units_written : 95742837 > S3ESNX0J951635M-host_read_commands : 213266959 > S3ESNX0J951635M-host_write_commands : 918085461 > S3ESNX0J951635M-controller_busy_time : 4280 > S3ESNX0J951635M-power_cycles : 218 > S3ESNX0J951635M-power_on_hours : 3072 > S3ESNX0J951635M-unsafe_shutdowns : 86 > S3ESNX0J951635M-media_errors : 0 > S3ESNX0J951635M-num_err_log_entries : 1 > S3ESNX0J951635M-warning_temp_time : 0 > S3ESNX0J951635M-critical_comp_time : 0 > S3ESNX0J951635M-temperature_sensor_1 : 310 > S3ESNX0J951635M-temperature_sensor_2 : 320 > S3ESNX0J951635M-thm_temp1_trans_count : 0 > S3ESNX0J951635M-thm_temp2_trans_count : 0 > S3ESNX0J951635M-thm_temp1_total_time : 0 > S3ESNX0J951635M-thm_temp2_total_time : 0 > > As you can see, there are three disks, that have the same metrics with > different values. Now I started with a xymonserver.d/nvme.cfg looking > like this: > > TEST2RRD="$TEST2RRD,nvme=ncv" > SPLITNCV_nvme="*:GAUGE" > GRAPHS_nvme="nvmecriticalwarning,nvmetemperature,nvmeavailspare,nvmesparethresh,nvmepercentused,nvmedataunitsread,nvmedataunitswritten,nvmehostreadcommands,nvmehostwritecommands,nvmecontrollerbusytime,nvmepowercycles,nvmepoweronhours,nvmeunsafeshutdowns,nvmemediaerrors,nvmenumerrlogentries,nvmewarningtemptime,nvmecriticalcomptime,nvmetemperaturesensor1,nvmetemperaturesensor2,nvmethmtemp1transcount,nvmethmtemp2transcount,nvmethmtemp1totaltime,nvmethmtemp2totaltime" > > > This causes all rrd files beeing created correctly like this: > > $ ls -1 /var/lib/xymon/rrd/wsrbreb/nvme*temperature.rrd > /var/lib/xymon/rrd/wsrbreb/nvme,2J4520102682_temperature.rrd > /var/lib/xymon/rrd/wsrbreb/nvme,S3ESNX0J951626N_temperature.rrd > /var/lib/xymon/rrd/wsrbreb/nvme,S3ESNX0J951635M_temperature.rrd > > Unfortunately all datasets are now saved as datatype "GAUGE", but most > need to have "DERIVE", but I cannot figure out how to do this. Here is > what I've tried: > > SPLITNCV_nvme="temperture:GAUGE" > SPLITNCV_nvme="*temperture:GAUGE" > SPLITNCV_nvme=".*temperture:GAUGE" > SPLITNCV_nvme="%.*temperture:GAUGE" > > > One thing that does work is the following: > > SPLITNCV_nvme="S3ESNX0J951626N_temperature:GAUGE" > > But as you can see it requieres the name of the SSD, which cancels out > all dynamics. > > How can I work with wildcards in SPLITNCV scenarios? > > Thank you for your help! > > Regards

2 2