- Xymon - Xymon mailman web

Status changing white to green in a loop
by mariusz.walczak＠deutsche-boerse.com 12 Jul '18

12 Jul '18

The below email is classified: Internal Hello, I have an issue where msgs column is changing from white to green all the time. It is filling Xymon server disk space. LXDBSP05 is running Xymon client + Xymon server. Any idea what is going on ? [cid:image001.png at 01D418FF.5341DF20] [cid:image002.png at 01D418FF.5341DF20] [cid:image003.png at 01D418FF.5341DF20] Regards, Mariusz ----------------------------------------- Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. Legally required information for business correspondence/ Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz: http://deutsche-boerse.com/letterhead

5 7

stale PROC checks not going away
by martin.wojak＠ecodev.vic.gov.au 11 Jul '18

11 Jul '18

I'm having an issue with old PROC checks not being removed. I had a CLASS called "linux2" with 3 PROC checks. A Host was using the linux2 class. I then changed the Host to use the "linux" class. Now the Host is checking for both linux and linux2 PROCs! Hosts.cfg extract: Was 10.0.0.13 MGTserver01 # CLASS:linux2 Now 10.0.0.13 MGTserver01 # CLASS:linux How do I get rid of the old PROCs that aren't required anymore? Tue Jul 10 14:56:28 AEST 2018 - Processes NOT ok green sshd (found 3, req. 1 or more) green proc1 (found 1, req. 1 or more) green proc2 (found 1, req. 1 or more) green proc3 (found 1, req. 1 or more) green rsyslogd (found 1, req. 1 or more) red proc4 (found 0, req. 1 or more) red proc5 (found 0, req. 1 or more) red proc6 (found 0, req. 1 or more) Xymon server version: Xymon 4.3.28-1.el7.terabithia Xymon client version: xymon-client-local.x86_64 - 4.3.28-1.el7 Thanks, Martin. ******************************************************************************** Department of Economic Development, Jobs, Transport and Resources, Government of Victoria, Victoria, Australia. This email, and any attachments, may contain privileged and confidential information. If you are not the intended recipient, you may not distribute or reproduce this e-mail or the attachments. If you have received this message in error, please notify us by return email. ********************************************************************************

3 3

Xymon - procs purple and red
by atalla＠zetaglobal.com 11 Jul '18

11 Jul '18

Hi Team, I'm intermittently getting purple and red for PROCS column for some of the hosts in Xymon. Could you please let me know the solution for this? Thanks, Ajay

6 10

False positives for hobbit-plugins libs test
by jwinius＠umrk.nl 10 Jul '18

10 Jul '18

Hi folks, In my environment we use the following: * Debian stretch with xymon 4.3.28-2 * Debian stretch with xymon-client 4.3.28-2 and hobbit-plugins 20170219 * Debian wheezy with xymon-client 4.3.0~beta2.dfsg-9.1+deb7u1 and hobbit-plugins 20120532 It all works fine, except that hobbit-plugins often gives false positives in the 'libs' column, indicating that certain "processes have libs linked that were upgraded". However, in those cases it makes no difference whether the processes are restarted, or even if the machine is rebooted: the processes continue to be flagged falsely. Examples include libvirt-qemu and mysql. It's the same on both of the platforms indicated above. Is there a fix or a reasonable workaround for this problem? Thanks, Jaap

2 6

Debian buster: Task libs terminated, status 2
by jwinius＠umrk.nl 10 Jul '18

10 Jul '18

Hi folks, This is really a bug report and a fix related to the current hobbit-plugins package for Debian buster. Most of my Xymon servers and clients are all running v4.3.28-2 on Debian stretch, but I do have one Debian buster client system running the same Xymon client software version and it had a problem. The libs test for this client failed constantly and had status purple. The clientlaunch.log was full of entries like this: 2018-07-09 10:22:00.240038 Task libs terminated, status 2 More tellingly, the xymonclient.log kept reporting: Mon Jul 9 06:56:35 2018 /usr/lib/xymon/client/ext/libs hobbit.pm.uninitialized: Can't locate File/Slurp.pm in @INC (you may need to install the File::Slurp module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/lib/xymon/client/ext/libs line 33. Mon Jul 9 06:56:35 2018 /usr/lib/xymon/client/ext/libs hobbit.pm.uninitialized: Hobbit::max_color(): No colors given as argument at /usr/share/perl5/Hobbit.pm line 126. BEGIN failed--compilation aborted at /usr/lib/xymon/client/ext/libs line 33. Hobbit::max_color(): No colors given as argument at /usr/share/perl5/Hobbit.pm line 126. So, this problem was easily fixed by installing an additional Debian package: ~# apt install libfile-slurp-perl In other words, this package needs to be listed as a dependency for hobbit-plugins. Cheers, Jaap

2 1

cross compilation and endianness detection
by herzog＠phys.ethz.ch 03 Jul '18

03 Jul '18

Hi Damien, I just checked and test-endianness is compiled from test-endianness.c - for some reason the one you have doesn't seem to work for you. Can you just do gcc -o test-endianness test-endianness.c and see if that works better? best, -Christian

2 2

xymonping overinflated response time
by terry.hurcombe＠brightsolid.com 03 Jul '18

03 Jul '18

Hello list. I've noted that since moving some systems from xymon 4.3.17 to 4.3.28 that ping times seem hugely inflated and do not match the response times I see from the command line utilities. 4.3.28 reports 40.2ms vs 0.92ms from 4.3.17. Is this a known issue? Regards, Terry. ________________________________ This message is confidential and may contain privileged information. You should not disclose its contents to any other person. If you are not the intended recipient, please notify the sender named above immediately. It is expressly declared that this e-mail does not constitute nor form part of a contract or unilateral obligation. Opinions, conclusions and other information in this message that do not relate to the official business of brightsolid shall be understood as neither given nor endorsed by it. ________________________________ __________________________________________________________________________ This email has been checked for virus and other malicious content prior to leaving our network. __________________________________________________________________________

3 2

cross compilation and endianness detection
by damien＠makelofine.org 01 Jul '18

01 Jul '18

Hi, I'm trying to compile xymon client for several OpenWRT devices (www.openwrt.org) Most targets are MIPS-based. When trying to compile, I encounter the following error: xymon-4.3.28$ make CC=mips-openwrt-linux-musl-gcc LD=mips-openwrt-linux-musl-ld CC="mips-openwrt-linux-musl-gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1" LDFLAGS="" OSDEF="-DLINUX" RPATHOPT="-Wl,--rpath," PCREINCDIR="" ZLIBINCDIR="" SSLFLAGS="" SSLINCDIR="" SSLLIBS="" NETLIBS="" LIBRTDEF="" XYMONTOPDIR="/var/lib/xymon" XYMONHOME="/var/lib/xymon" XYMONCLIENTHOME=/var/lib/xymon XYMONLOGDIR="" XYMONHOSTNAME="" XYMONHOSTIP="A.B.C.D" XYMONHOSTOS="" LOCALCLIENT="no" make -C lib client make[1] : entering « /home/src/xymon-4.3.28/lib » mips-openwrt-linux-musl-gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/home/src/xymon-4.3.28/include -DCLIENTONLY=1 -I../include `./test-endianness` -c -o sha1.o sha1.c /bin/sh: 1: ./test-endianness: Exec format error sha1.c:38:2: error: #error "Endianness is UNDEFINED" This part is far beyond my computers skills, so I'm requesting some help :)

1 0

Interval for the combostatus task
by john.thurston＠alaska.gov 29 Jun '18

29 Jun '18

I use some combo-tests, and the delay in their reaction is sometimes a hassle. I just looked in the tasks.cfg and see I have my combostatus task set to run every 5 mins. 5 mins is the frequency of my xymonnet task, but many of my combo tests don't rely on xymonnet. I'm thinking I should shorten the interval on combostatus to 2 minutes, and thereby reduce the latency of those test results. Can anyone relate to me horror stories or good reasons I should not shorten this interval? -- 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

2 1

xymondXboard syntax limitation - XMH tags?
by john.thurston＠alaska.gov 27 Jun '18

27 Jun '18

The xymondboard message type is shown in the docs with the following syntax: > xymondboard [CRITERIA] [fields=FIELDLIST] The xymondXboard message type is shown in the docs with the following: > Retrieves an XML string with the summary of all status logs as for the "xymondboard" command. but it looks to me like Xboard does not support the 'fields=' capabilities of board. I always get the same fields in my XML, regardless of how I craft my message. My quick look in source-code makes me think the values returned by Xboard are limited and hard-coded. I'd like to use Xboard, but I'd also like to have it return some XMH tags (like XMH_DGNAME, XMH_DISPLAYNAME). Can anyone suggest a way to do this? -- 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

1 0