- Xymon - Xymon mailman web

Xymon 4.3.29 ack/enadis issues
by john.r.rothlisberger＠accenture.com 09 Sep '19

09 Sep '19

Is anyone else having problems with acknowledge.sh & enadis.sh working from the web page? Ubuntu 16.04LTS I can disable via command line but not via the web interface - no errors in apache logs and no entries in acknowledge.log. Thanks, John Upcoming PTO: _____________________________________________________________________ John Rothlisberger IT Strategy, Infrastructure & Security - Technology Growth Platform TGP for Business Process Outsourcing Accenture 312.693.3136 office _____________________________________________________________________ ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com

1 0

Monitoring ESXi 6.x cpu, disk, memory, procs?
by patterson＠nullamatix.com 07 Sep '19

07 Sep '19

Does anyone have a simple example of how to monitor the usual client stuff on an ESXi host? I was thinking it should be possible for the Xymon server to reach out via SSH, run some commands (esxcli?) and return the output. If the response is null or ssh connection failed, report red. Another thought, /bin/python3.5 is available on ESXi - so perhaps there's a way to run and report the tests with python on the ESXi host itself as a cronjob? My coding skills are still a work in progress so any examples of how to accomplish something like this would be helpful. The list archives reference a lot of old scripts and code for ESXi 4/5 which don't seem to work for ESXi 6.5+ Thanks, Guy

2 1

Errors after upgrade to 4.3.29
by john.r.rothlisberger＠accenture.com 06 Sep '19

06 Sep '19

Ubuntu 16.04LTS Hosts.cfg entry: directory /home/xymon/server/etc/include_ssl/a/ File /home/Xymon/server/etc/include_ssl/a/abcdef.acc.com contains: 0.0.0.0 abcdef.acc.com # noconn NOPROPYELLOW:* NOPROPPURPLE:* NOCOLUMNS:http,info,trends ssldays=30:15 https://abcdef.acc.com 0.0.1.0 I am seeing these errors in my alert.log - these particular clients (URL's actually as they are for sslcert tests reside in an include directory): Checking criteria for host 'abcdef.acc.com', which is not yet defined; some alerts may not immediately fire The errors are popping for every file that is in the include_directory. These errors were not present in 4.3.21 - 4.3.28. Ideas? Thanks, John Upcoming PTO: _____________________________________________________________________ John Rothlisberger IT Strategy, Infrastructure & Security - Technology Growth Platform TGP for Business Process Outsourcing Accenture 312.693.3136 office _____________________________________________________________________ ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com

2 4

Xymon and Lighttpd 500 Internal Error
by patterson＠nullamatix.com 05 Sep '19

05 Sep '19

Hello, The Xymon index page is loading; however, when I attempt to drill down into an individual service check (invoking svcstatus.sh), lighttpd returns a 500 internal server error. OS: Devuan Ascii 2.0 Kernel: Linux pihole 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux Lighttpd: Version: 1.4.45-1 Xymon: Version: 4.3.28-2 Xymon and lighttpd were both installed from the official Devuan repos using apt-get. Here's my lighttpd config: https://clbin.com/F2LzF Here's an strace: https://clbin.com/EuesM Thanks, Guy

3 10

Double combo - display &unknown - xymon 4.3.28
by dominique.delporte＠gmail.com 03 Sep '19

03 Sep '19

I have the same problem as in the thread https://lists.xymon.com/archive/2011-September/032469.html Where a patch was suggested here : https://lists.xymon.com/archive/2011-September/032481.html But in fact the problem is always present with combo of combo. I found the solution : update color value in function getstatus So I propose this patch, just adding one line to update color : *color = (walk->result ? COL_GREEN : COL_RED); --- combostatus.c.orig 2019-09-03 14:46:39.221984375 +0200 +++ combostatus.c 2019-09-03 14:50:42.412165047 +0200 @@ -251,6 +251,7 @@ for (walk = testhead; (walk && ( (strcmp(walk->reshostname, hostname) != 0) || (strcmp(walk->restestname, testname) != 0) ) ); walk = walk->next); if (walk != NULL) { /* It is a combo test they want the result of. */ + *color = (walk->result ? COL_GREEN : COL_RED); return walk->result; } dominique DELPORTE

2 1

Trying to install Xymon Client on Fedora Minimum
by ralphmitchell＠gmail.com 03 Sep '19

03 Sep '19

When you're building source, you need the -devel packages too: libtirpc-devel Ralph Mitchell On Tue, Sep 3, 2019 at 8:51 AM Jason Chambers via Xymon <xymon at xymon.com> wrote: > > > > ---------- Forwarded message ---------- > From: Jason Chambers <Jason.Chambers at geosoft.com> > To: "xymon at xymon.com" <xymon at xymon.com> > Cc: > Bcc: > Date: Tue, 3 Sep 2019 12:36:18 +0000 > Subject: Trying to install Xymon Client on Fedora Minimum > > Hey All, > > > > I?m attempting to install the Xymon Client on a Fedora minimum install. > Obviously this means I have to install the dependencies myself since they > would not be installed natively. But I?m currently stuck as to why I cannot > compile. > > > > gcc -g -O2 -Wall -Wno-unused -I/usr/include/tirpc -Wno-pointer-sign > -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX > -I/home/seequent/xymon-4.3.29/include -DCLIENTONLY=1 -c -o xymon.o xymon.c > > gcc -g -O2 -Wall -Wno-unused -I/usr/include/tirpc -Wno-pointer-sign > -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX > -I/home/seequent/xymon-4.3.29/include -DCLIENTONLY=1 -o ../client/xymon > xymon.o ../lib/libxymonclientcomm.a -ltirpc ../lib/libxymonclient.a > > /usr/bin/ld: cannot find -ltirpc > > collect2: error: ld returned 1 exit status > > make[1]: *** [Makefile:46: ../client/xymon] Error 1 > > make[1]: Leaving directory '/home/seequent/xymon-4.3.29/common' > > make: *** [build/Makefile.rules:96: common-client] Error 2 > > > > > > Funny thing is libtirpc is already installed, it doesn?t make sense why it > cannot find it. > > > > dnf install libtirpc > > Fedora Modular 30 - > x86_64 > 48 > kB/s | 16 kB 00:00 > > Fedora Modular 30 - x86_64 - > Updates > 47 > kB/s | 16 kB 00:00 > > Fedora 30 - x86_64 - Updates > 159 > kB/s | 16 kB 00:00 > > Fedora 30 - > x86_64 > 54 kB/s | 16 kB 00:00 > > Package libtirpc-1.1.4-2.rc2.fc30.1.x86_64 is already installed. > > Dependencies resolved. > > Nothing to do. > > Complete! > > > > Is there a different package that I need to install? > > > > > > Thanks, > > JC > > > > ---------- Forwarded message ---------- > From: Jason Chambers via Xymon <xymon at xymon.com> > To: "xymon at xymon.com" <xymon at xymon.com> > Cc: > Bcc: > Date: Tue, 3 Sep 2019 12:36:18 +0000 > Subject: [Xymon] Trying to install Xymon Client on Fedora Minimum > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

2 1

Trying to install Xymon Client on Fedora Minimum
by Jason.Chambers＠geosoft.com 03 Sep '19

03 Sep '19

Hey All, I'm attempting to install the Xymon Client on a Fedora minimum install. Obviously this means I have to install the dependencies myself since they would not be installed natively. But I'm currently stuck as to why I cannot compile. gcc -g -O2 -Wall -Wno-unused -I/usr/include/tirpc -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/home/seequent/xymon-4.3.29/include -DCLIENTONLY=1 -c -o xymon.o xymon.c gcc -g -O2 -Wall -Wno-unused -I/usr/include/tirpc -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/home/seequent/xymon-4.3.29/include -DCLIENTONLY=1 -o ../client/xymon xymon.o ../lib/libxymonclientcomm.a -ltirpc ../lib/libxymonclient.a /usr/bin/ld: cannot find -ltirpc collect2: error: ld returned 1 exit status make[1]: *** [Makefile:46: ../client/xymon] Error 1 make[1]: Leaving directory '/home/seequent/xymon-4.3.29/common' make: *** [build/Makefile.rules:96: common-client] Error 2 Funny thing is libtirpc is already installed, it doesn't make sense why it cannot find it. dnf install libtirpc Fedora Modular 30 - x86_64 48 kB/s | 16 kB 00:00 Fedora Modular 30 - x86_64 - Updates 47 kB/s | 16 kB 00:00 Fedora 30 - x86_64 - Updates 159 kB/s | 16 kB 00:00 Fedora 30 - x86_64 54 kB/s | 16 kB 00:00 Package libtirpc-1.1.4-2.rc2.fc30.1.x86_64 is already installed. Dependencies resolved. Nothing to do. Complete! Is there a different package that I need to install? Thanks, JC

1 0

bbdisplay missing default client columns
by tarik.mecci＠sharewire.net 29 Aug '19

29 Aug '19

Hi, on Xymon server 4.3.28 (Ubuntu 18.04) I've been battling with 2 issues which I suspect may be related... #1 The xymon clients are successfully sending data to the server, i.e. I see my custom clientlaunch extension script names received in the histlogs dir and as columns on the bbdisplay. However all the standard client checks (cpu, disk, procs etc) are missing from both histlogs and the bbdisplay. I know the Xymon clients are correctly sending everything because these clients (v4.3.28) were previously connected to an earlier version of bbd where everything worked. It's the same situation with the local xymon client running on the xymon server - no cpu, disk, procs etc but my custom client script columns are displaying. I do see clientlog data showing in the bbdisplay. Is the xymon server is supposed to receive clientlog data and parse this into these individual items (cpu, disk, procs..)? Could I be missing the task which is responsible for this? #2 I have been successfully using criticalview.cgi in a previous xymon version to produce custom alert pages. Despite providing a suitable --config= file which should result in some host alerts showing in the output, I continually receive "All Monitored Systems OK". On my previous Xymon version this works as expected. Adding --debug flag has not helped me. I'm fairly confident it's not my --config= file format cos that works perfectly on the previous ver, and it matches the format of the generated critical.cfg. My question... could these both be caused by the same issue, e.g. a missing env/config variable which I need to set? Thanks! Tarik

1 0

dialup setting disables all alerts
by kspringer＠innovateteam.com 29 Aug '19

29 Aug '19

Hi all.? I've got numerous hosts with the 'dialup' setting configured in my hosts.cfg file.? I was under the impression that this setting was for hosts that routinely go online/offline.? But it's totally turning off all alerts for those hosts even if they have the xymonclient installed and functioning.? Is this expected behavior?? I don't want to disable all alerts for those hosts.? I just don't care if they go purple.? What should I be doing instead of using the 'dialup' setting? Kris Springer

2 1

xymongen crashes in 4.3.29
by matt1299＠gmail.com 28 Aug '19

28 Aug '19

Hi all, Every day since we updated our Xymon server to 4.3.29 (from 4.3.28), I've gotten an e-mail alert due to xymond turning red that reads: red xymongen program crashed Fatal signal caught! The strange thing is that this has happened at 1:04 AM every day...like clockwork. I have xymongen set to run every 1 minute and it has no problems running any other time of the day. We are using the Terabithia RPMs and the Xymon server is running RHEL 7. I've scoured the system to find anything that is set to run at/around that time via cron, etc. and haven't found anything. The system logs don't show anything is happening around that time either. I turned on debug logging for xymond and xymongen and haven't been able to find anything unusual in either logs around that time. But it is dumping core files for xymongen every time it crashes. I used gdb to get the backtrace on all of the core files (so far) and I've found that they all show the same thing. It shows the same host in the backtrace too (although I'm farily confident it isn't specific or isolated to that host but just the first one it runs into that it has issues with when processing). I've included an example gdb output below (the most recent one) [1]. Is anyone else running into this by chance? Or any idea what might be the cause? Thanks! [1] # gdb -q /usr/libexec/xymon/xymongen core.16327 Reading symbols from /usr/libexec/xymon/xymongen...Reading symbols from /usr/lib/debug/usr/libexec/xymon/xymongen.debug...done. done. [New LWP 16327] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/xymon/xymongen --reportopts=1566187200:1566273599:0:nongr --recent'. Program terminated with signal 6, Aborted. #0 0x00007f4657c49377 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55 55 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); (gdb) bt #0 0x00007f4657c49377 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55 #1 0x00007f4657c4aa68 in __GI_abort () at abort.c:90 #2 0x00005589375dd455 in sigsegv_handler (signum=<optimized out>) at sig.c:57 #3 <signal handler called> #4 strchrnul () at ../sysdeps/x86_64/strchrnul.S:33 #5 0x00007f4657c5b681 in __find_specmb (format=0xfce <Address 0xfce out of bounds>) at printf-parse.h:109 #6 _IO_vfprintf_internal (s=s at entry=0x7ffd5dabcc00, format=format at entry=0xfce <Address 0xfce out of bounds>, ap=ap at entry=0x7ffd5dabcd38) at vfprintf.c:1308 #7 0x00007f4657d28c78 in ___vsprintf_chk (s=0x7ffd5dabcf82 "", flags=1, slen=18446744073709551615, format=0xfce <Address 0xfce out of bounds>, args=args at entry=0x7ffd5dabcd38) at vsprintf_chk.c:83 #8 0x00007f4657d28bcd in ___sprintf_chk (s=<optimized out>, flags=flags at entry=1, slen=slen at entry=18446744073709551615, format=<optimized out>) at sprintf_chk.c:32 #9 0x00005589375ce8ca in sprintf (__fmt=<optimized out>, __s=<optimized out>) at /usr/include/bits/stdio2.h:33 #10 parse_histlogfile (starttime=1566187200, timespec=0x558937840f50 <timespec.7157> "Wed_Sep_2_19:34:55_2015", servicename=0x5589383b6d70 "procs", hostname=0x558938a335d0 "<client hostname>") at availability.c:174 #11 parse_historyfile (fd=fd at entry=0x558938a3aea0, repinfo=<optimized out>, hostname=0x558938a335d0 "<client hostname>", servicename=0x5589383b6d70 "procs", fromtime=<optimized out>, totime=1566273599, for_history=for_history at entry=0, warnlevel=97, greenlevel=99.995000000000005, warnstops=-1, reporttime=0x0) at availability.c:475 #12 0x00005589375c38cc in init_state (filename=<optimized out>, filename at entry=0x7ffd5dacf210 "<client hostname>.procs", log=log at entry =0x7ffd5dacf120) at loaddata.c:275 #13 0x00005589375c45ee in load_state (sumhead=sumhead at entry=0x558937809d48 <dispsums>) at loaddata.c:626 #14 0x00005589375be6f4 in main (argc=5, argv=0x7ffd5dad4418) at xymongen.c:599 -- Matt Vander Werf

3 7