- Xymon - Xymon mailman web

snapshot.sh and report.sh problem
by heiko.wuest＠gmail.com 08 Nov '20

08 Nov '20

Hi, i did a fresh instal of xymon on Centos8 with the rpm's provided (Xymon 4.3.30-1.el8.terabithia) it looks like evrything is working as expected but two reports doesn't run if i click on Snapshot or Availability Report the the browser downloads a file called snapshot.sh or report.sh which has some content in: xymonrep-3128-1604871819 Content-type: text/html <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html"> <TITLE>Xymon - Snapshot Report</TITLE> ........ any idea? Propably some stupid thing i miss? -- Heiko

1 0

NCV parse bug
by stef.coene＠docum.org 03 Nov '20

03 Nov '20

Hi, Yesterday, I upgraded our xymon monitoring servers to 4.3.30. We have approximately 70 instances running and on 4 of them, the xymond_rrd that's monitoring the status channel module crashes. When running in debug mode, I noticed that it crashes on messages with garbled NCV messages. This includes devmon messages, but also the Synology client message. Example of a bad devmon message that crashes xymon_rrd: Free memory= bytes (Regex mismatch%) xymon_rrd debug output: 18326 2020-11-02 23:06:33.529013 xymond_rrd: Got message 156827 @@status#156827/axidrnsw5|1604354793.510204|127.0.0.1||axidrnsw5|memory|1604356593|green||green|1600168997|0||0||1600078261||Network-LAN|0| 18326 2020-11-02 23:06:33.529018 startpos 41059, fillpos 54529, endpos 41610 2020-11-02 23:06:33.936070 Peer at 0.0.0.0:0 failed: Broken pipe 2020-11-02 23:06:33.936133 Child process 18326 died: Signal 6 We didn't experienced it on previous versions. We ran a mix of 4.3.21 and 4.3.28. Stef

1 0

xymonpsclient (application) logfile monitoring
by christian.becker＠rhein-zeitung.net 21 Oct '20

21 Oct '20

Hello to the list, i need help in setting up logfile monitoring with xymonpsclient. My setup is a Windows 10 client pc, running xymonpsclient v2.42, reporting to a xymon server running xymon 4.3.30. In the client-local.cfg i have configured the logfile that i want to monitor, and an amount of time later, the logfile shows up in the msgs column. After that i configured analysis.cfg to look for a specific pattern in this logfile, it seems to me that only the appearance of this pattern is displayed in the msgs column, but nothing else from this logfile. In addition tot hat, the msgs column didn't change to red state. Here's the part of my client-local.cfg: [win10client1] log:C:\Program Files\PATH-TO-LOGFILE\filename.log:153600 And here the part of my analysis.cfg: HOST=win10client1 LOG C:\Program Files\PATH-TO-LOGFILE\filename.log Unable.to.cancel.connection.to COLOR=RED With this setup it seems to me that only lines containing this pattern Unable.to.cancel.connection.to are displayed in the msgs column of win10client1. Any idea what i'm doing wrong? Or do i understand any basics the wrong way? Regards Christian

4 8

problem with cgi
by ruslan133＠yandex.ru 20 Oct '20

20 Oct '20

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20201020/429fcbad/attach…>

1 0

Problem to compile on AIX 7.1
by linuxmasterjedi＠free.fr 20 Oct '20

20 Oct '20

Hello, I'm trying to compile Xymon client on AIX 7.1. I installed a couple of RPM files such as : make_64-4.1-1.aix5.3.ppc.rpm pcre-7.4-2.aix5.1.ppc.rpm pcre-devel-7.4-2.aix5.1.ppc.rpm gcc-8.3.0-2.aix7.1.ppc.rpm gcc-cpp-8.3.0-2.aix7.1.ppc.rpm libgcc-8.3.0-2.aix7.1.ppc.rpm libstdc++7-7.2.0-1.aix7.1.ppc.rpm I unpacked the xymon in /tmp/xymon-4.3.30 and I try to compile and here is the error : /tmp/xymon-4.3.30 > gmake CC="cc" CFLAGS="-g -O3 -D_REENTRANT -DAIX -I`pwd`/include -DCLIENTONLY=1" LDFLAGS="" OSDEF="-DAIX" RPATHOPT="" PCREINCDIR="" ZLIBINCDIR="" SSLFLAGS="" SSLINCDIR="" SSLLIBS="" NETLIBS="" LIBRTDEF="" XYMONTOPDIR="/opt/xymon-monitor" XYMONHOME="/opt/xymon-monitor" XYMONCLIENTHOME=/opt/xymon-monitor XYMONLOGDIR="" XYMONHOSTNAME="" XYMONHOSTIP="10.10.7.25" XYMONHOSTOS="" LOCALCLIENT="no" gmake -C lib client gmake[1]: Entering directory '/tmp/xymon-4.3.30/lib' cc -g -O3 -D_REENTRANT -DAIX -I/tmp/xymon-4.3.30/include -DCLIENTONLY=1 -I../include -o test-endianness test-endianness.c cc: error trying to exec 'cc1': execvp: No such file or directory Makefile:35: recipe for target 'test-endianness' failed gmake[1]: *** [test-endianness] Error 1 gmake[1]: Leaving directory '/tmp/xymon-4.3.30/lib' build/Makefile.rules:90: recipe for target 'lib-client' failed gmake: *** [lib-client] Error 2 Can you help to fix the compilation error or maybe can you share a static AIX client compiled? Thanks !

2 1

Xymon Digest, Vol 117, Issue 7
by herald.ten.dam＠icu-it.nl 16 Oct '20

16 Oct '20

I had this issue also and not being a c programmer (and not having a lot of time to figure out) I adjusted the file "svcstatus-trends.c" on line 291: Original: SBUF_MALLOC(allrrdlinks,16384) New: SBUF_MALLOC(allrrdlinks,163840) So the buffer value times 10. After this I got rid of the 500 error. So I think the buffer is to little for some environments. Met vriendelijke groet, Herald ten Dam Database Specialist Oracle, Medior z/VM ICU IT Services BV Transistorstraat 55b I 1322 CK ALMERE M 06 ? 28 891 653 I E herald.ten.dam at icu-it.nl<mailto:herald.ten.dam at icu-it.nl> T 088 ? 5 234 123 I www.icu-it.nl<http://www.icu-it.nl> I KvK 32135776 ________________________________ Van: Xymon <xymon-bounces at xymon.com> namens xymon-request at xymon.com <xymon-request at xymon.com> Verzonden: dinsdag 13 oktober 2020 12:00 Aan: xymon at xymon.com <xymon at xymon.com> Onderwerp: Xymon Digest, Vol 117, Issue 7 Send Xymon mailing list submissions to xymon at xymon.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.xymon.com/mailman/listinfo/xymon or, via email, send a message with subject or body 'help' to xymon-request at xymon.com You can reach the person managing the list at xymon-owner at xymon.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Xymon digest..." Today's Topics: 1. Re: Too much data for svcstatus.sh? (Henrik St?rner) ---------------------------------------------------------------------- Message: 1 Date: Mon, 12 Oct 2020 16:01:09 +0200 From: Henrik St?rner <henrik at hswn.dk> To: xymon at xymon.com Subject: Re: [Xymon] Too much data for svcstatus.sh? Message-ID: <46a50f10-4fe1-4990-fa37-4062e8da7921 at hswn.dk> Content-Type: text/plain; charset=utf-8 Hi, the best way to debug this is to get a proper stack trace of when the program crashes. For this, you first need to make sure you have a binary of svcstatus.cgi which includes debug information - if you look at the Xymon sources, the build/Makefile.Linux file has a commented-out line setting the CFLAGS variable for debugging: # Compile flags for debugging # CFLAGS = -g -DDEBUG -Wall -D_REENTRANT $(LFSDEF) $(OSDEF) Uncomment the last line, run "make clean; make" and then use the web/svcstatus.cgi binary from that. To run the program in the gdb debugger, I would bypass the web server CGI and run it by hand like this: $ export SCRIPT_NAME="svcstatus.sh" $ export REQUEST_METHOD="GET" $ export QUERY_STRING="HOST=claudio.hswn.dk&SERVICE=disk" $ gdb ./web/svcstatus.cgi (gdb) run The value for the QUERY_STRING should be taken from the URL for your status-page - the part after the '?' sign. The example here is from the xymon.com site, but you really just need to modify the hostname to that of your own. Note that you must run it on the Xymon server, because it reads the file stored there. Regards, Henrik Den 21.05.2020 kl. 17.47 skrev Mike Burger: > 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. > ------------------------------ Subject: Digest Footer _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon ------------------------------ End of Xymon Digest, Vol 117, Issue 7 *************************************

2 1

Different conn Testresults after Migration to a new xymon server
by sysadmin＠wvs-basa.de 15 Oct '20

15 Oct '20

Hello, I've migrated my xymon Monitor to another host in the same network due to an old linux version on the old one. The old server was Ubuntu Server 14.04 and the new one is version 20.04 LTS. I have copied all the configuration files from the old to the new one. Now I am really surprised, that I get different conn-test results on the two xymon server running parallel at the moment for some hosts. On the old server the host is green (alive) on the new one the host is red (not ok), but if I run a fping or ping on both servers the tested hosts are ok and alive. Therefore I added the trace option on the new xymon to the conn test. Thu Oct 15 07:34:39 2020 conn NOT ok Service conn on XXXX is not OK : Host does not respond to ping System unreachable for 229 poll periods (67968 seconds) [red] XXXXXX is unreachable Traceroute results: traceroute to XXXXXX , 30 hops max, 60 byte packets 1 router one 0.134 ms 0.093 ms 0.118 ms 2 XXXX.dip0.t-ipconnect.de (XXX.XXX.XXX.XXX) 1.593 ms 1.806 ms * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * XXXX.dip0.t-ipconnect.de (XXX) 64.015 ms * I run the traceroute command on ssh-console on the new xymon for the same host at the same time traceroute XXX traceroute to XXX (XXX), 30 hops max, 60 byte packets 1 XXX (XXX) 0.186 ms 0.126 ms 0.122 ms 2 XXX.dip0.t-ipconnect.de (80.153.230.205) 1.154 ms 1.331 ms * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * XXX.dip0.t-ipconnect.de (80.153.230.205) 59.814 ms 64.467 ms And a ping ping XXX PING XXX (XXXX) 56(84) bytes of data. 64 bytes from XXX: icmp_seq=1 ttl=56 time=55.7 ms 64 bytes from XXX: icmp_seq=2 ttl=56 time=55.3 ms 64 bytes from XXX: icmp_seq=3 ttl=56 time=55.0 ms 64 bytes from XXX: icmp_seq=4 ttl=56 time=55.2 ms Even fping -Ae on console reports the host to be alive. Why are the results so different? What is the problem and how to fix it? Sincerley Steffen -- Diese E-Mail wurde vom Sophos Security Gateway auf gef?hrliche Inhalte gepr?ft! http://www.sophos.com

2 1

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

14 Oct '20

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 5

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