- Xymon - Xymon mailman web

VPAT for Xymon?
by Kristopher.Mallory＠fda.hhs.gov 23 Aug '17

23 Aug '17

Hello I'm curious if anyone might know if Xymon has an Voluntary Product Accessibility Template (VPAT). We are looking to get it approved for use, ,however this document may be needed. https://www.section508.gov/content/sell/vpat Thank you, Kristopher Mallory

2 1

[SOLVED...] Fwd: Problem/Bug? in xymon.cgi with FNPATTERN and dynamic ds-name (Again)
by herber75＠gmail.com 17 Aug '17

17 Aug '17

Hi Everyone, i can fix my problem, but i don´t understand how In showgraph.c, I changed the line below sprintf(resultstr, "%-*s", paramlen, val); For this sprintf(resultstr, "%-*s", strlen(val), val); Only for information I downloaded and complied the rrdtool-1.2.30 version. Bye ---------- Forwarded message ---------- From: Hernán Berman <herber75 at gmail.com> Date: Tue, May 23, 2017 at 1:21 PM Subject: Problem/Bug? in xymon.cgi with FNPATTERN and dynamic ds-name (Again) To: "xymon at xymon.com" <xymon at xymon.com> Hi Everyone I run a new installation of xymon 4.3.28 on a RHEL6.9 and I have problems whit custom graphs. The error is: Cannot parse DS in 'DEF:p0=mytest.subline.rrd:subline :AVERAGE' I fixed in an older installation following this old post http://lists.xymon.com/oldarchive/2008/07/msg00379.html But in this version the code it has fixed. In practice I send 2 values from my custom script, the rdd files are created fine, but showgraph can’t parse the second value. I try with this to debug or understand the problem: I have deleted the rrd file for one of values and the result was the graph was shown, whit one line, the expected. I have deleted the second rrd file and recreate the first with the another value and the result was the same. In my opinion there are a problem wiht the "p" value, because is staying in "0" for the second value. Any Idea, or how to fix that? Thanks Hernán

1 0

Setup new View in Xymon
by zain1723＠gmail.com 16 Aug '17

16 Aug '17

Hello, Could anyone assist me or share procedure in setting up a new view on xymon webpage ? Thanks

2 1

bbtest-net sporadic crash on xymon 4.3.27
by alisci＠avantune.com 10 Aug '17

10 Aug '17

Sporadic crashes by bbtest-net was reported on our xymon 4.3.27 server here the occurrences: -rw------- 1 xymon xymon 7372800 Aug 6 18:24 core.28430 -rw------- 1 xymon xymon 7368704 Aug 6 18:29 core.10460 -rw------- 1 xymon xymon 7368704 Aug 6 20:25 core.12861 -rw------- 1 xymon xymon 7368704 Aug 6 20:30 core.27236 -rw------- 1 xymon xymon 7368704 Aug 6 20:35 core.9305 -rw------- 1 xymon xymon 7368704 Aug 7 07:28 core.24208 -rw------- 1 xymon xymon 7368704 Aug 9 03:00 core.27039 -rw------- 1 xymon xymon 7368704 Aug 9 03:05 core.9120 -rw------- 1 xymon xymon 7368704 Aug 9 03:10 core.23484 -rw------- 1 xymon xymon 7368704 Aug 9 11:04 core.19788 here follow the stack trace of the last one. All of them was caused by bbtest-net and seems due to the same cause: gdb bin/bbtest-net tmp/core.19788 GNU gdb Fedora (6.8-27.el5) Copyright (C) 2008 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"... Reading symbols from /usr/lib64/libldap-2.3.so.0...done. Loaded symbols for /usr/lib64/libldap-2.3.so.0 Reading symbols from /lib64/librt.so.1...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libssl.so.6...done. Loaded symbols for /lib64/libssl.so.6 Reading symbols from /lib64/libcrypto.so.6...done. Loaded symbols for /lib64/libcrypto.so.6 Reading symbols from /lib64/libpcre.so.0...done. Loaded symbols for /lib64/libpcre.so.0 Reading symbols from /lib64/libc.so.6...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /usr/lib64/liblber-2.3.so.0...done. Loaded symbols for /usr/lib64/liblber-2.3.so.0 Reading symbols from /lib64/libresolv.so.2...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /usr/lib64/libsasl2.so.2...done. Loaded symbols for /usr/lib64/libsasl2.so.2 Reading symbols from /lib64/libpthread.so.0...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /usr/lib64/libgssapi_krb5.so.2...done. Loaded symbols for /usr/lib64/libgssapi_krb5.so.2 Reading symbols from /usr/lib64/libkrb5.so.3...done. Loaded symbols for /usr/lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /usr/lib64/libk5crypto.so.3...done. Loaded symbols for /usr/lib64/libk5crypto.so.3 Reading symbols from /lib64/libdl.so.2...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /usr/lib64/libz.so.1...done. Loaded symbols for /usr/lib64/libz.so.1 Reading symbols from /lib64/libcrypt.so.1...done. Loaded symbols for /lib64/libcrypt.so.1 Reading symbols from /usr/lib64/libkrb5support.so.0...done. Loaded symbols for /usr/lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libselinux.so.1...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /lib64/libsepol.so.1...done. Loaded symbols for /lib64/libsepol.so.1 Reading symbols from /lib64/libnss_files.so.2...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `bbtest-net --report --ping --concurrency=50 --checkresponse --dnslog=/var/log/x'. Program terminated with signal 6, Aborted. [New process 19788] #0 0x000000351be30215 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x000000351be30215 in raise () from /lib64/libc.so.6 #1 0x000000351be31cc0 in abort () from /lib64/libc.so.6 #2 0x0000000000427643 in sigsegv_handler (signum=<value optimized out>) at sig.c:57 #3 <signal handler called> #4 dns_simple_callback (arg=0x16d835f0, status=0, timeout=<value optimized out>, hent=0x16dc18f0) at dns.c:120 #5 0x0000000000414021 in end_hquery () #6 0x00000000004144e1 in host_callback () #7 0x0000000000419907 in end_squery () #8 0x0000000000419a0c in search_callback () #9 0x0000000000419709 in qcallback () #10 0x0000000000418140 in end_query () #11 0x0000000000418e73 in process_answer () #12 0x00000000004193ff in processfds () #13 0x00000000004119d6 in dns_ares_queue_run (channel=0x16869af0) at dns.c:172 #14 0x0000000000409c5b in main (argc=6, argv=0x7fff2de6f648) at xymonnet.c:2323 Before printing, think about the environment Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

1 0

3 vmstat procs and other issues
by earle＠isolar.DynDNS.ORG 05 Aug '17

05 Aug '17

Way back on 6 Jan 2017, at 3:00, Japeth Cleaver <cleaver at terabithia.org> wrote: > On 1/5/2017 3:18 PM, Galen Johnson wrote: > >> Ok...looking more closely at the xymonclient-linux.sh script, it >> appears that tmpfs was intentionally not included in the exclude >> list. At the very least, you may want to consider adding /run to the >> default excludes in analysis.cfg. I was also noticing in my df >> output >> that other virtual filesystems were showing (and being tracked) as >> well, such as /dev/shm and /sys. I'm not sure why you would want >> those tracked either. For example, here's a list of tmpfs "disks" I >> see on one of my systems: >> >> tmpfs 2033585 9 2033576 1% /dev/shm >> tmpfs 2033585 598 2032987 1% /run >> tmpfs 2033585 13 2033572 1% /sys/fs/cgroup >> tmpfs 2033585 29 2033556 1% /tmp >> tmpfs 2033585 1 2033584 1% /run/user/1984 > > Oy. > > I'd forgotten about the newer per-user /run/ environments that were > coming in now in EL7. Definitely worth adding specific excludes for > those. > > /dev/shm/ is occasionally used as dedicated scratch space for some > purposes. In fact, it's the default write location for the temporary > message in the xymon-client RPM for a while now (this way you can > actually get a report when /tmp/ fills to 100%). With the > proliferation > of spurious tmpfs mounts now, it might be a good idea to take another > look. Sorry to dredge up an old thread from January, but as I just ran into this ... I agree with Japeth that getting reports about "/tmp" being 100% full is a Good Thing™. But I'm seeing some strange instances on a couple of our RHEL 7.3 systems where for some strange reason, during boot "/dev/shm" is getting mysteriously chmod'ed from mode 1777 to 1755. No idea why/where. Xymon starts up OK but of course it can't write its temp files in there so everything goes Purple and "stopped reporting". Took me a while to suss that one out. (This mystery chmod'ing also affects "gdm" as "pulseaudio" can't write its tmp files in there either.) Not sure what the best solution is (I assume if you put them in "/var/tmp" or "/var/run/xymon" then if "/var" is part of "/", you wouldn't get 100% full alerts for "/" - which would be a Bad Thing™), but thought I should mention this scenario. I might try changing XYMONTMP in "xymonclient.cfg" on this latest system where it happened just to test it out, but it's a VM with little chance of "/" filling up. BTW, I just noticed there's a "/run/xymon" (in the RHEL 7.3 RPM, anyway). Why not use that for XYMONTMP on RHEL 7/CentOS 7/Fedora? Or would it be too much of a pain to maintain two different "xymonclient.cfg" files with two different XYMONTMP settings? - Greg P.S. Need Fedora 26 RPMs for 4.3.28 please :)

1 0

Preferred linux flavor for a server
by john.thurston＠alaska.gov 04 Aug '17

04 Aug '17

I run a couple of instances of Xymon on Solaris. I ran another instance on CentOS 6. For various reasons, I need to create another instance on linux. I lean towards CentOS 7 but could almost as easily choose something else. I thought I should ask: Is there a linux distribution on which I should expect the installation of Xymon to be particularly difficult or simple? -- 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

yet another purple paging problem
by EDSchminke＠Hormel.com 04 Aug '17

04 Aug '17

So, not to point out the obvious, but you are executing the xymon 127.0.0.1 "drop hostname testname" command on the actual xymon server, correct? Next, check the hosts.cfg file. The drop command syntax is "drop hostname testname". Make sure the hostname portion matches what is on the line in your hosts file where the unwelcome purple test exists. So if your hosts line is: 0.0.0.0 myserver # foo bar etc Make sure you're using: xymon 127.0.0.1 "drop myserver bbd" Not: xymon 127.0.0.1 "drop myserver.example.com bbd" Something else you might try, if your host is actually listed as its FQDN.. If your hosts.cfg file is 0.0.0.0 myserver.example.com # foo bar etc Try: xymon 127.0.0.1 "drop myserver,example,com bbd" Also, there would also be data for a bbd test in the following additional locations: - data/histlogs/myserver_example_com/bbd/ - data/rrd/myserver.example.com/ (look for something "tcp.bbd.rrd") Hopefully by manually deleting the data already, you haven't shot yourself in the foot in terms of this command working successfully. i.e., it sees the first location was empty, so it assumes everything has already been done and stops early Erik D. Schminke | Associate Systems Programmer Hormel Foods Corporation | One Hormel Place | Austin, MN 55912 Phone: (507) 434-6817 edschminke at hormel.com | www.hormelfoods.com

1 0

yet another purple paging problem
by laurent.henry＠ehess.fr 04 Aug '17

04 Aug '17

Hello, Sorry in advance but i can't get rid of purple paging and purple notification on xymon webpage. By mistrake, i created bad tests in my host.cfg. As example, a bbd (database) test to a unrelevant host. Which created as expected a red alert. I then removed the test from host.cfg. Since then, i am warned about purple event i can't remove I tried these: - delete data/hist/myserver.bbd - remove bbd line in data/hist/myserver file - restart xymond - tried xymon 127.0.0.1 "drop host.example.com test" procedure i found on google I still see a purple square icon in the bbd column of that host on my webpage and receive paging mails I tried to remove anything about this test too in histlogs. I still notice tracks of this test in server/tmp/alert.chk and xymond.chk too . Trying to remove there does not change anything. I don't know what to try else. As an old bb user i was used to just remove logs files about purple events Could anyone help ?

2 1

Critical System Page -- HTTP 500 Error
by EDSchminke＠Hormel.com 04 Aug '17

04 Aug '17

I think I can point to a specific cause for this issue. It seems to be a combination of the "uptime" test being in an alert condition and the same test failing during an exclusion window on the Critical Systems Page. I have a number of Windows systems monitored for uptime. In analysis.cfg: UP 10m 37d yellow In critical.cfg: CTX_Template|uptime|||*:0400:2400|1|EPD|System has rebooted|rchicks 2017-08-04 07:58:11 I also set Xymon to send me alerts for ALL systems between 2:30AM and 3:30AM; the average time window for the Critical Systems Page going down In alerts.cfg: HOST=%.* MAIL edschminke at hormel.com FORMAT=text REPEAT=1h TIME=*:0230:0330 FORMAT=text MAIL edschminke at hormel.com FORMAT=text TIME=*:0230:0330 FORMAT=text RECOVERED Last night, around 2:45, 4 of these systems were rebooted. As soon as the first email was sent that a system went yellow for uptime, I got the alert that http went red for the Critical Systems Page. When the last email was sent that uptime recovered, I got the alert that http recovered. This morning, I rebooted a different Windows host. I watched the test go yellow, but the Critical Systems Page was fine. In this case, the condition was within the "Monitoring Time" window. I then went into the Critical Systems Editor and modified the "Monitoring Time" and put it outside the window (e.g. current time 8AM, window: 12PM-12AM). As soon as I refresh the Critical Systems Page, it crashes. Change the "Monitoring Time" so that the condition is back inside the window (e.g. 4AM), refresh, it loads fine. I tested the same process with a few tests; disk, memory, cpu. I could not duplicate the problem with those tests. I think the problem is limited to uptime, but it very well could be others. It also does not seem to matter whether it is the actual host config, or a "cloned" host config. The crash happens with both. If it matters, here's my environment.. I'm currently running Xymon v4.3.27. The OS is Red Hat Enterprise Linux v6.8. Kernel is 2.6.32-431.el6. Architecture is x86_64. glibc version is 2.12-1.192.el6; for what it's worth, but i686 and x86_64 packages are installed. A gdb backtrace shows that crash occurs in a "strncmp" function in lib/loadcriticalconf.c on line 249 (gdb) backtrace #0 0x0000003603729420 in __strncmp_sse42 () from /lib64/libc.so.6 #1 0x000000000040fa40 in get_critconfig (key=<value optimized out>, flags=<value optimized out>, resultkey=<value optimized out>) at loadcriticalconf.c:249 #2 0x00000000004030eb in loadstatus (maxprio=3, maxage=31536000, mincolor=3, wantacked=0) at criticalview.c:115 #3 0x00000000004036f0 in main (argc=<value optimized out>, argv=<value optimized out>) at criticalview.c:513 (gdb) frame 1 #1 0x000000000040fa40 in get_critconfig (key=<value optimized out>, flags=<value optimized out>, resultkey=<value optimized out>) at loadcriticalconf.c:249 249 if (strncmp(realkey, rec->key, strlen (realkey)) != 0) handle=xtreeEnd(rbconf); (gdb) print realkey $1 = 0x1c20c80 "CTX_Template|uptime" (gdb) print *rec $2 = {key = 0x435f6c65746e6957 <Address 0x435f6c65746e6957 out of bounds>, priority = 1769236850, starttime = 7310575213499737428, endtime = 0, crittime = 0x1c1d8e0 "Wintel_Critical_Template", ttgroup = 0x21 <Address 0x21 out of bounds>, ttextra = 0x6364727673737763 <Address 0x6364727673737763 out of bounds>, updinfo = 0x3603003d31 <Address 0x3603003d31 out of bounds>} All of the crash details are still in my GitHub repo at https://github.com/edschminke/xymon ...including the coredump file. I suspect better C developers than myself can put that to a lot better use. Thanks! Erik D. Schminke | Associate Systems Programmer Hormel Foods Corporation | One Hormel Place | Austin, MN 55912 Phone: (507) 434-6817 edschminke at hormel.com | www.hormelfoods.com

1 0

purple pages
by ve2cii＠canasoft.net 03 Aug '17

03 Aug '17

Hi Everyone, I have a feature request or possibly a bug. If I make a change to the hosts.cfg, for example deleting a client the data remains and if I don't remove it the client turns purple and then pages. Is there something that can be done, automated process to compare what is in the data files against the hosts file and then remove any inconsistencies. Something like this perhaps? -- sysadm cronomagic.com/gemstelecom.com e-mail ve2cii at canasoft.net POWERED BY LINUX

3 4