October 2020 - Xymon - Xymon mailman web

Capture and send data To Elasticsearch and Kibana
by francois.outteryck＠soprasteria.com 27 Sep '22

27 Sep '22

Hi Peter, Examples of task.cfg configuration with status and stachg events : [capture_status] ENVFILE /home/xymon/server/etc/xymonserver.cfg NEED xymond CMD xymond_channel --channel=status /home/xymon/server/ext/capture.sh --log=$XYMONSERVERLOGS/xymond_task_capture.log LOGFILE /var/log/xymon/lunch_capture.log [capture_stachg] ENVFILE /home/xymon/server/etc/xymonserver.cfg NEED xymond CMD xymond_channel --channel=stachg /home/xymon/server/ext/capture.sh --log=$XYMONSERVERLOGS/xymond_task_capture_stachg.log LOGFILE /var/log/xymon/lunch_capture_stachg.log Capture.sh script simple made to call a php script : #!/bin/sh /usr/bin/php /var/www/kibana/capture.php $@ </dev/stdin >>/var/log/xymon/xymond_capture_php.log 2>&1 And capture.php make all job : <?php date_default_timezone_set('Europe/Paris'); $TODO=FALSE; $ARRAY_COLLECTOR=array(); $COLLECTOR=null; while (FALSE !== ($line = fgets(STDIN))) if ($line!='') { $tab=reduce_array($line); if (sizeof($tab)==0) continue; if ($line=="@@\n") { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } } else if (substr($tab[0],0,8)=='@@stachg') { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } /* 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 /* @@stachg#seq|timestamp|sender|origin|hostname|testname|expiretime|color|prevcolor|changetime|disabletime|disablemsg|downtimeactive|clienttstamp|modifiers */ $COLLECTOR='stachg'; $metadata=explode('|',$tab[0]); $sender=$metadata[2]; $hostname=$metadata[3]; $metadata=array( 'Collector'=>$COLLECTOR, 'Sender'=>$metadata[2], 'ServerName'=>$metadata[4], 'Type'=>$metadata[5], 'Status'=>$metadata[7], 'PrevStatus'=>$metadata[8], 'LogTime'=>$metadata[1], 'ValidTime'=>$metadata[6], 'LastChange'=>$metadata[9], 'DisableTime'=>$metadata[10], 'DisableMSg'=>$metadata[11], 'Message'=>'' ); $id=$metadata['ServerName'].'_'.$metadata['Type'].'_'.$meta['LastChange']; $ARRAY_COLLECTOR=null; $ARRAY_COLLECTOR=array(); $TODO=TRUE; } else if (substr($tab[0],0,8)=='@@status') { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } /* 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 /* @@status|timestamp|sender|origin|hostname|testname|expiretime|color|testflags|prevcolor|changetime|ackexpiretime|ackmessage|disableexpiretime|disablemessage|clientmsgtstamp|flapping */ $COLLECTOR='status'; $metadata=explode('|',$tab[0]); $sender=$metadata[2]; $hostname=$metadata[3]; $metadata=array( 'Collector'=>$COLLECTOR, 'Sender'=>$metadata[2], 'ServerName'=>$metadata[4], 'Type'=>$metadata[5], 'Status'=>$metadata[7], 'LogTime'=>$metadata[1], 'ValidTime'=>$metadata[6], 'LastChange'=>$metadata[10], 'DisableTime'=>$metadata[13], 'AckTime'=>$metadata[11], 'DisableMSg'=>$metadata[14], 'Message'=>'' ); $id=$metadata['ServerName'].'.'.$metadata['Type']; $ARRAY_COLLECTOR=null; $ARRAY_COLLECTOR=array(); $TODO=TRUE; } else { if (substr($tab[0],0,2)=='@@') { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } } if ($TODO) $ARRAY_COLLECTOR[]=$line; } } function CallAPI($method, $url, $data = false) { $curl = curl_init(); switch ($method) { case "POST": curl_setopt($curl, CURLOPT_POST, 1); if ($data) curl_setopt($curl, CURLOPT_POSTFIELDS, $data); break; case "PUT": curl_setopt($curl, CURLOPT_PUT, 1); break; default: if ($data) $url = sprintf("%s?%s", $url, http_build_query($data)); } curl_setopt($curl, CURLOPT_URL, $url); curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1); $result = curl_exec($curl); curl_close($curl); return $result; } function reduce_array($line) { $tab=explode(' ',$line); $nr=array(); for ($i=0;$i<sizeof($tab);$i++) if (trim($tab[$i])!='') $nr[]=trim($tab[$i]); return $nr; } function SendData($id,$cc,$COLLECTOR=null) { if ($COLLECTOR==null) return; $d=new DateTime(); if ($cc['LastChange']!='') {$d->setTimestamp($cc['LastChange']);$cc['LastChange']=$d->format('c');} else {$cc['LastChange']='NaN';} if ($cc['LogTime']!='') {$d->setTimestamp($cc['LogTime']);$cc['LogTime']=$d->format('c');} else {$cc['LogTime']='NaN';} if ($cc['ValidTime']!='') {$d->setTimestamp($cc['ValidTime']);$cc['ValidTime']=$d->format('c');} else {$cc['ValidTime']='NaN';} if (isset($cc['AckTime'])) { if ($cc['AckTime']!='') {$d->setTimestamp($cc['AckTime']);$cc['AckTime']=$d->format('c');} else {$cc['AckTime']='NaN';} } if ($cc['DisableTime']!='') {$d->setTimestamp($cc['DisableTime']);$cc['DisableTime']=$d->format('c'); } else {$cc['DisableTime']='NaN';} $data = json_encode($cc); $data=str_replace('"NaN"','null',$data); echo $id.'=>'.$data."\n"; $url="http://127.0.0.1:9200/xymon/".$COLLECTOR."/".$id; $res=CallAPI("POST",$url,$data); } ?> De : Peter Welter [mailto:peter.welter at gmail.com] Envoyé : vendredi 23 décembre 2016 14:45 À : OUTTERYCK Francois Cc : xymon at xymon.com Objet : Re: [Xymon] Capture and send data To Elasticsearch and Kibana Hi Francois, Looks good, your sample. I am very interested in your integration efforts. How do you select what is going to be inserted in the ELK stack? All status messages that Xymon receives? And could you provide an example of the xymond_channel block in you task.cfg and the capture.sh? Tasks.cfg probably is something like: [es] ... CMD xymond_channel --channel=status /home/xymon/server/ext/capture.sh ... And the capture.sh contains some curl script to the ELK stack? Regards, Peter 2016-12-14 18:15 GMT+01:00 OUTTERYCK Francois <francois.outteryck at soprasteria.com<mailto:francois.outteryck at soprasteria.com>>: Hello, I just do a small work with Xymon in order to send status data to Elasticsearch. And with Kibana reporting is easy. How it work ? Simple : With capture of status message (xymond_channel --channel=status /home/xymon/server/ext/capture.sh ) script encode status message in json and send as document in elasticSearch. Example of Mapping document status in elasticsearch : "status"=> array( "properties"=>array( "ServerName"=> array("type"=> "string"), "Type"=> array("type"=> "string"), "Status"=> array("type"=> "string"), "LastChange"=> array("type"=> "date","format"=> "strict_date_optional_time"), "LogTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "ValidTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "AckTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "DisableTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "Sender"=> array("type"=> "string"), "DisableMSg"=> array("type"=> "string"), "Message"=> array("type"=> "string") ) ) All is done with a 130 lines script. So simple to integrate in existing environment and so powerfull usage of Xymon/elasticsearch/Kibana For those who don’t know kibana : https://www.elastic.co/products/kibana [cid:image001.png at 01D25EA3.F74489F0] _______________________________________________ Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon

2 1

4.3.30 RPMs released
by cleaver＠terabithia.org 23 May '22

23 May '22

Hello all, After a weekend in /testing/, the xymon 4.3.30-1 Terabithia RPMs have been moved to the production repositories at https://repo.terabithia.org/rpms/xymon/ Regards, -jc

2 1

Terabithia or compile
by ralphmitchell＠gmail.com 16 Mar '22

16 Mar '22

I downloaded the source rpm and installed it. The spec file for building the RPMs contains this: %if %{without trunk} %if 0%{?rhel} <= 7 Requires: ntp %endif %endif So, yeah, it builds into the binary RPMs the requirement to pull in ntp. I'm not sure if that can be made into a conditional, to require ntp OR chrony. Ralph Mitchell On Thu, Jun 18, 2020 at 5:05 PM Root, Paul T via Xymon <xymon at xymon.com> wrote: > > > > ---------- Forwarded message ---------- > From: "Root, Paul T" <Paul.Root at centurylink.com> > To: "'John Thurston'" <john.thurston at alaska.gov>, "xymon at xymon.com" < > xymon at xymon.com> > Cc: > Bcc: > Date: Thu, 18 Jun 2020 21:04:50 +0000 > Subject: RE: [Xymon] Terabithia or compile > That's odd. I did not do that to me. > > -----Original Message----- > From: Xymon <xymon-bounces at xymon.com> On Behalf Of John Thurston > Sent: Thursday, June 18, 2020 2:24 PM > To: xymon at xymon.com > Subject: Re: [Xymon] Terabithia or compile > > On 6/17/2020 4:38 PM, John Horne wrote: > > I used to build from source, but for our CentOS 7 and 8 servers I have > been > > using the Terabithia RPMs with no problems. The downside is that, like > Malcolm > > Hunter mentioned, I have subsequently applied some local patches - sent > to the > > list - so that meant rebuilding the RPMs. > > I'm now looking at the Terabithia package for the first time in years. > My first reaction is, wth? > > Installing the xymon package on my server has disabled chronyd and > installed (but not started) ntpd. why?! If I hadn't read through the > list of packages it was going to grab, and understand the significance > of this one, I'd be going blindly forward with an un-synchronized system > clock. > > Now I wonder how many other of my services it has disabled or replaced. > I feel like I've just walked into a mine field :( > > > -- > Do things because you should, not just because you can. > > John Thurston 907-465-8591 > John.Thurston at alaska.gov > Department of Administration > State of Alaska > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > > https://imss91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f… > This communication is the property of CenturyLink and may contain > confidential or privileged information. Unauthorized use of this > communication is strictly prohibited and may be unlawful. If you have > received this communication in error, please immediately notify the sender > by reply e-mail and destroy all copies of the communication and any > attachments. > > > > ---------- Forwarded message ---------- > From: "Root, Paul T via Xymon" <xymon at xymon.com> > To: "'John Thurston'" <john.thurston at alaska.gov>, "xymon at xymon.com" < > xymon at xymon.com> > Cc: > Bcc: > Date: Thu, 18 Jun 2020 21:04:50 +0000 > Subject: Re: [Xymon] Terabithia or compile > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

5 5

random errors with imaps/pop3s servers offering TLS 1.3
by lolo＠troll.free.org 10 Aug '21

10 Aug '21

Hi, I have found an issue when trying to monitor imaps and pop3s server offering TLS1.3 . My xymon server configuration: # freebsd-version -u 12.0-RELEASE-p5 # openssl version OpenSSL 1.1.1a-freebsd 20 Nov 2018 standard freebsd xymon-server pkg : # pkg info xymon-server-4.3.28 xymon-server-4.3.28 Name : xymon-server Version : 4.3.28 Installed on : Fri Feb 22 14:19:11 2019 CET Origin : net-mgmt/xymon-server Architecture : FreeBSD:12:amd64 Prefix : /usr/local Categories : net-mgmt www Licenses : GPLv2 Maintainer : feld at FreeBSD.org WWW : http://xymon.sourceforge.net/ Comment : System for monitoring servers and networks Options : DEBUG : off LDAP : off NETSNMP : off Shared Libs required: libcares.so.2 libpng16.so.16 libpcre.so.1 librrd.so.8 Annotations : FreeBSD_version: 1200086 cpe : cpe:2.3:a:xymon:xymon:4.3.28:::::freebsd12:x64 repo_type : binary repository : FreeBSD Flat size : 26.5MiB ... # ldd /usr/local/www/xymon/server/bin/xymonnet /usr/local/www/xymon/server/bin/xymonnet: libcares.so.2 => /usr/local/lib/libcares.so.2 (0x80027c000) libssl.so.111 => /usr/lib/libssl.so.111 (0x800297000) libcrypto.so.111 => /lib/libcrypto.so.111 (0x80032c000) libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x800619000) libc.so.7 => /lib/libc.so.7 (0x8006bd000) libthr.so.3 => /lib/libthr.so.3 (0x800ab0000) When trying to monitor a pop3s or imaps server offering tls 1.3, I got random errors: WARNING: Flapping status Service imaps on xxx is not OK : Unexpected service response If I monitor the same services on an other server not offering tls 1.3, all is fine. Both servers where running dovecot. I wrote an extension in perl using IO::Socket::SSL (and the same local openssl) to monitor the server offerng tls 1.3 and all is fine with it. For some strange reason, I can monitor a https web servers (running nginx or apache) offering TLS 1.3 without this issue but not imaps/pop3s. It looks like the https test is different from other ssl/tls tests and does not have the TLS 1.3 issue Regards, -- Laurent Frigault | Free.org - BookMyName.com - ONLINE SAS - Registar ID 74

2 1

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 damien＠makelofine.org 14 Oct '20

14 Oct '20

Le 29/09/2020 ? 16:24, Oliver R. a ?crit?: > 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 > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon Ok Oliver, I understand your point now: you want to use wildcard related to the dataset name. Hence, we have to validate this is possible... I could not find anything pointing to wildcard usage in define the dataset name, in this documentation: https://xymon.sourceforge.io/xymon/help/howtograph.html I'm not a C guy, hence I'll consider documentation only: if there is no mention, it does not exist. You could try to handle manually (awful answer I know) the serial number of your NVMe's ? Or better: contribute to the code (answer from someone lazy who won't)

2 1