May 2016 - Xymon - Xymon mailman web

xymonproxy crashing under the load
by jtrott＠dancrai.com 31 May '16

31 May '16

Hi. We have a large xymon setup that averages 25 messages/sec for xymond. I am in the process of migrating to a new xymon server and was planning on using a front end xymonproxy process on a third box to keep traffic going to both old and new boxes while I migrated across the old data (primarily the rrd data as that requires conversion from 32bit to 64bit). The xymonproxy is working fine under light load (20 or so client machines) but when I modify the firewall port forward to point the incoming port 1984 traffic to it it crashes after a few seconds. 2016-05-31 16:08:19.793720 xymonproxy version 4.3.27-1.el7.terabithia starting 2016-05-31 16:08:19.793791 Listening on 0.0.0.0:1984 2016-05-31 16:08:19.793796 Sending to 2 Xymon server(s): 172.16.100.103:1984 172.16.100.101:1984 2016-05-31 16:09:23.010861 conn 0: server 1 (172.16.100.101:1984) not responding, message lost 2016-05-31 16:09:23.011363 conn 0, socket -1: write shutdown failed: Bad file descriptor 2016-05-31 16:09:24.012798 conn 0: server 1 (172.16.100.101:1984) not responding, message lost 2016-05-31 16:09:25.014274 conn 0, socket -1: write shutdown failed: Bad file descriptor *** buffer overflow detected ***: xymonproxy terminated ======= Backtrace: ========= /lib64/libc.so.6(__fortify_fail+0x37)[0x7f234c396597] /lib64/libc.so.6(+0x10c750)[0x7f234c394750] /lib64/libc.so.6(+0x10e507)[0x7f234c396507] xymonproxy[0x403e11] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f234c2a9b15] xymonproxy[0x406579] ======= Memory map: ======== 00400000-0041d000 r-xp 00000000 fd:00 25459501 /usr/libexec/xymon/xymonproxy 0061d000-0061e000 r--p 0001d000 fd:00 25459501 /usr/libexec/xymon/xymonproxy 0061e000-0061f000 rw-p 0001e000 fd:00 25459501 /usr/libexec/xymon/xymonproxy 0061f000-00646000 rw-p 00000000 00:00 0 02472000-025f4000 rw-p 00000000 00:00 0 [heap] 7f234a874000-7f234a889000 r-xp 00000000 fd:00 18879360 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f234a889000-7f234aa88000 ---p 00015000 fd:00 18879360 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f234aa88000-7f234aa89000 r--p 00014000 fd:00 18879360 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f234aa89000-7f234aa8a000 rw-p 00015000 fd:00 18879360 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f234aa8a000-7f234aaae000 r-xp 00000000 fd:00 16856000 /usr/lib64/liblzma.so.5.0.99 7f234aaae000-7f234acad000 ---p 00024000 fd:00 16856000 /usr/lib64/liblzma.so.5.0.99 7f234acad000-7f234acae000 r--p 00023000 fd:00 16856000 /usr/lib64/liblzma.so.5.0.99 7f234acae000-7f234acaf000 rw-p 00024000 fd:00 16856000 /usr/lib64/liblzma.so.5.0.99 7f234acaf000-7f234acd0000 r-xp 00000000 fd:00 16915048 /usr/lib64/libselinux.so.1 7f234acd0000-7f234aed0000 ---p 00021000 fd:00 16915048 /usr/lib64/libselinux.so.1 7f234aed0000-7f234aed1000 r--p 00021000 fd:00 16915048 /usr/lib64/libselinux.so.1 7f234aed1000-7f234aed2000 rw-p 00022000 fd:00 16915048 /usr/lib64/libselinux.so.1 7f234aed2000-7f234aed4000 rw-p 00000000 00:00 0 7f234aed4000-7f234aeea000 r-xp 00000000 fd:00 16855963 /usr/lib64/libresolv-2.17.so 7f234aeea000-7f234b0ea000 ---p 00016000 fd:00 16855963 /usr/lib64/libresolv-2.17.so 7f234b0ea000-7f234b0eb000 r--p 00016000 fd:00 16855963 /usr/lib64/libresolv-2.17.so 7f234b0eb000-7f234b0ec000 rw-p 00017000 fd:00 16855963 /usr/lib64/libresolv-2.17.so 7f234b0ec000-7f234b0ee000 rw-p 00000000 00:00 0 7f234b0ee000-7f234b0f1000 r-xp 00000000 fd:00 17026913 /usr/lib64/libkeyutils.so.1.5 7f234b0f1000-7f234b2f0000 ---p 00003000 fd:00 17026913 /usr/lib64/libkeyutils.so.1.5 7f234b2f0000-7f234b2f1000 r--p 00002000 fd:00 17026913 /usr/lib64/libkeyutils.so.1.5 7f234b2f1000-7f234b2f2000 rw-p 00003000 fd:00 17026913 /usr/lib64/libkeyutils.so.1.5 7f234b2f2000-7f234b2ff000 r-xp 00000000 fd:00 18086631 /usr/lib64/libkrb5support.so.0.1 7f234b2ff000-7f234b4ff000 ---p 0000d000 fd:00 18086631 /usr/lib64/libkrb5support.so.0.1 7f234b4ff000-7f234b500000 r--p 0000d000 fd:00 18086631 /usr/lib64/libkrb5support.so.0.1 7f234b500000-7f234b501000 rw-p 0000e000 fd:00 18086631 /usr/lib64/libkrb5support.so.0.1 7f234b501000-7f234b517000 r-xp 00000000 fd:00 16855957 /usr/lib64/libpthread-2.17.so 7f234b517000-7f234b717000 ---p 00016000 fd:00 16855957 /usr/lib64/libpthread-2.17.so 7f234b717000-7f234b718000 r--p 00016000 fd:00 16855957 /usr/lib64/libpthread-2.17.so 7f234b718000-7f234b719000 rw-p 00017000 fd:00 16855957 /usr/lib64/libpthread-2.17.so 7f234b719000-7f234b71d000 rw-p 00000000 00:00 0 7f234b71d000-7f234b720000 r-xp 00000000 fd:00 17867018 /usr/lib64/libdl-2.17.so 7f234b720000-7f234b91f000 ---p 00003000 fd:00 17867018 /usr/lib64/libdl-2.17.so 7f234b91f000-7f234b920000 r--p 00002000 fd:00 17867018 /usr/lib64/libdl-2.17.so 7f234b920000-7f234b921000 rw-p 00003000 fd:00 17867018 /usr/lib64/libdl-2.17.so 7f234b921000-7f234b950000 r-xp 00000000 fd:00 17149883 /usr/lib64/libk5crypto.so.3.1 7f234b950000-7f234bb4f000 ---p 0002f000 fd:00 17149883 /usr/lib64/libk5crypto.so.3.1 7f234bb4f000-7f234bb51000 r--p 0002e000 fd:00 17149883 /usr/lib64/libk5crypto.so.3.1 7f234bb51000-7f234bb52000 rw-p 00030000 fd:00 17149883 /usr/lib64/libk5crypto.so.3.1 7f234bb52000-7f234bb53000 rw-p 00000000 00:00 0 7f234bb53000-7f234bb56000 r-xp 00000000 fd:00 16915067 /usr/lib64/libcom_err.so.2.1 7f234bb56000-7f234bd55000 ---p 00003000 fd:00 16915067 /usr/lib64/libcom_err.so.2.1 7f234bd55000-7f234bd56000 r--p 00002000 fd:00 16915067 /usr/lib64/libcom_err.so.2.1 7f234bd56000-7f234bd57000 rw-p 00003000 fd:00 16915067 /usr/lib64/libcom_err.so.2.1 7f234bd57000-7f234be2c000 r-xp 00000000 fd:00 17166500 /usr/lib64/libkrb5.so.3.3 7f234be2c000-7f234c02c000 ---p 000d5000 fd:00 17166500 /usr/lib64/libkrb5.so.3.3 7f234c02c000-7f234c039000 r--p 000d5000 fd:00 17166500 /usr/lib64/libkrb5.so.3.3 7f234c039000-7f234c03c000 rw-p 000e2000 fd:00 17166500 /usr/lib64/libkrb5.so.3.3 7f234c03c000-7f234c085000 r-xp 00000000 fd:00 17177116 /usr/lib64/libgssapi_krb5.so.2.2 7f234c085000-7f234c285000 ---p 00049000 fd:00 17177116 /usr/lib64/libgssapi_krb5.so.2.2 7f234c285000-7f234c286000 r--p 00049000 fd:00 17177116 /usr/lib64/libgssapi_krb5.so.2.2 7f234c286000-7f234c288000 rw-p 0004a000 fd:00 17177116 /usr/lib64/libgssapi_krb5.so.2.2 7f234c288000-7f234c43f000 r-xp 00000000 fd:00 16855941 /usr/lib64/libc-2.17.so 7f234c43f000-7f234c63f000 ---p 001b7000 fd:00 16855941 /usr/lib64/libc-2.17.so 7f234c63f000-7f234c643000 r--p 001b7000 fd:00 16855941 /usr/lib64/libc-2.17.so 7f234c643000-7f234c645000 rw-p 001bb000 fd:00 16855941 /usr/lib64/libc-2.17.so 7f234c645000-7f234c64a000 rw-p 00000000 00:00 0 7f234c64a000-7f234c6aa000 r-xp 00000000 fd:00 18095822 /usr/lib64/libpcre.so.1.2.0 7f234c6aa000-7f234c8a9000 ---p 00060000 fd:00 18095822 /usr/lib64/libpcre.so.1.2.0 7f234c8a9000-7f234c8aa000 r--p 0005f000 fd:00 18095822 /usr/lib64/libpcre.so.1.2.0 7f234c8aa000-7f234c8ab000 rw-p 00060000 fd:00 18095822 /usr/lib64/libpcre.so.1.2.0 7f234c8ab000-7f234ca69000 r-xp 00000000 fd:00 17026905 /usr/lib64/libcrypto.so.1.0.1e 7f234ca69000-7f234cc69000 ---p 001be000 fd:00 17026905 /usr/lib64/libcrypto.so.1.0.1e 7f234cc69000-7f234cc83000 r--p 001be000 fd:00 17026905 /usr/lib64/libcrypto.so.1.0.1e 7f234cc83000-7f234cc8f000 rw-p 001d8000 fd:00 17026905 /usr/lib64/libcrypto.so.1.0.1e 7f234cc8f000-7f234cc93000 rw-p 00000000 00:00 0 7f234cc93000-7f234ccf6000 r-xp 00000000 fd:00 18093381 /usr/lib64/libssl.so.1.0.1e 7f234ccf6000-7f234cef5000 ---p 00063000 fd:00 18093381 /usr/lib64/libssl.so.1.0.1e 7f234cef5000-7f234cef9000 r--p 00062000 fd:00 18093381 /usr/lib64/libssl.so.1.0.1e 7f234cef9000-7f234cf00000 rw-p 00066000 fd:00 18093381 /usr/lib64/libssl.so.1.0.1e 7f234cf00000-7f234cf0b000 r-xp 00000000 fd:00 17867002 /usr/lib64/liblz4.so.1.7.1 7f234cf0b000-7f234d10a000 ---p 0000b000 fd:00 17867002 /usr/lib64/liblz4.so.1.7.1 7f234d10a000-7f234d10b000 r--p 0000a000 fd:00 17867002 /usr/lib64/liblz4.so.1.7.1 7f234d10b000-7f234d10c000 rw-p 00000000 00:00 0 7f234d10c000-7f234d121000 r-xp 00000000 fd:00 16915045 /usr/lib64/libz.so.1.2.7 7f234d121000-7f234d320000 ---p 00015000 fd:00 16915045 /usr/lib64/libz.so.1.2.7 7f234d320000-7f234d321000 r--p 00014000 fd:00 16915045 /usr/lib64/libz.so.1.2.7 7f234d321000-7f234d322000 rw-p 00015000 fd:00 16915045 /usr/lib64/libz.so.1.2.7 7f234d322000-7f234d343000 r-xp 00000000 fd:00 18043068 /usr/lib64/ld-2.17.so 7f234d52e000-7f234d538000 rw-p 00000000 00:00 0 7f234d540000-7f234d543000 rw-p 00000000 00:00 0 7f234d543000-7f234d544000 r--p 00021000 fd:00 18043068 /usr/lib64/ld-2.17.so 7f234d544000-7f234d545000 rw-p 00022000 fd:00 18043068 /usr/lib64/ld-2.17.so 7f234d545000-7f234d546000 rw-p 00000000 00:00 0 7ffdfcb9d000-7ffdfcbbf000 rw-p 00000000 00:00 0 [stack] 7ffdfcbdb000-7ffdfcbdd000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] 2016-05-31 16:09:25.092174 xymonproxy version 4.3.27-1.el7.terabithia starting 2016-05-31 16:09:25.092364 Listening on 0.0.0.0:1984 2016-05-31 16:09:25.092379 Sending to 2 Xymon server(s): 172.16.100.103:1984 172.16.100.101:1984 Xymonproxy is running on CentOS 7 with all the latest patches installed. 172.16.100.103 is xymon 4.3.16 on CentOS 5, 172.16.100.101 is xymon 4.3.27-1.el7.terabithia on CentOS 7. Any ideas on how to troubleshoot this further? Thanks, JT

1 1

Bug in client data handling in 4.3.27
by jtrott＠dancrai.com 31 May '16

31 May '16

Hi. We are in the process of migrating xymon from a CentOS 5 server running 4.3.16 to a CentOS 7 server running 4.3.27-1 (terabithia-xymon) and have run into a bug while testing the new install. I have setup a third box with a xymonproxy to allow delivery to both servers at the same time to reduce downtime for the migration of the 200GB or so of historical data. Both servers have identically setup hosts.cfg with almost all clients listed in include and dspinclude (for layout reasons) files. This was working fine in 4.3.16 but on 4.3.27 it works fine for bbwin clients, but not for xymon-client or hobbit-client clients on linux. For the linux clients I get the new clientlog green diamond showing up (once I modified the include file to end in .cfg and added ALLOWALLCONFIGFILES="TRUE" to xymonserver.cfg) but all the other client tests stay purple. If I move one of the linux clients from an include file into the main hosts.cfg file it starts behaving normally. Any ideas? Thanks, JT

1 1

xymondboard / nongreen page
by cami187＠gmail.com 31 May '16

31 May '16

Hi All, Can someone perhaps direct me on how it's possible to use the command line to generate / display all the hosts currently listed on the non-green page? Using the xymondboard with color=yellow or xymondboard=red seems to display considerably more than what is on the nongreen.html page. I'm looking to create a "dashboard" (outside of xymon) that monitors the nongreen.html page and lists how many hosts are listed there that do not have acknowledgements. Regards, Cami

2 2

Devmon tests clear but snmpwalk works
by colin.coe＠gmail.com 30 May '16

30 May '16

Hi all I know this is the Xymon list not Devmon but I think I'll have most luck on this list so apologies in advance. I have a few of Cisco switches that I've just started monitoring at a couple of remote sites. snmpwalk works from the Xymon server but the Devmon tests are all clear (Devmon runs on the Xymon server). When I look at the devmon.log I just see lots of --- [16-05-26 at 20:19:09] No SNMP data found for ifName on swi02 [16-05-26 at 20:19:09] No SNMP data found for ifOutPktsSec on swi02 [16-05-26 at 20:19:09] No SNMP data found for ifOutCollisions on swi02 --- Any ideas on tracking this down? We have many if these switches at other sites and they display correctly in Xymon. Thanks CC

5 12

disk graph page limits total file systems
by EDSchminke＠Hormel.com 29 May '16

29 May '16

Another update for this topic: I added 100 file systems to a couple systems to see what would happen with the graphs. The target systems were different from the one that spawned this topic. When I added 100 file systems to a Linux (RHEL 6.6) system, all file systems were reported/graphed on the disk page. When I added 100 file systems to an AIX (v7.1) system, file systems were truncated; although at a different point. 120 of 132 file systems were represented.. I don't understand why they're so different. Comparing the df portions of the messages from each of the systems do not reveal any obvious differences. I'd really appreciate some suggestions for debugging. What commands I can run manually that the disk page is running internally. I've looked at the code, but haven't quite figured out what's going on in there; my C skills are rubbish. 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

2 4

IT'S ALIVE!!!! Now for the fun questions......
by bigbandjohn＠gmail.com 29 May '16

29 May '16

Hi. Thanks to everyone yesterday. The quick response got my graphing up and running. I would be happy to document the CentOS 7.x install session when I do the official build and provide it for the wiki if anyone is interested. There are some minor differences with firewall commands and using services instead of the old initd vs. CentOS 6.x. Now I have 2 new questions - in the more general vein: 1) is there a bundle for the xymon client such that you don't have to build on every server you install on? The reason I ask is that most of our servers are barebones in production (only what is absolutely required). Mix of RHEL and AIX. Worst case I would bundle the directory which I made the client in between servers and do a "make install", but only as a last resort. 2) There are a couple administration add-ons for xymon. Would like advice if any are worth installing in your opinions. look forward to the feedback. John Lahngbein

3 2

New to Xymon - having an issue
by bigbandjohn＠gmail.com 23 May '16

23 May '16

Greetings. I was a Big Brother user many moons ago and contributed many modules including for a database, a "multi module" and hot plug-in modules. In recent years I have moved away from the monitoring role, but recently have been thrust back into it. I am looking at many packages, and I am leaning towards Xymon as I like the "at a glance" dashboard for many of the people who may look at it. I am using CentOS 7.1 for my OS, and fairly quickly got it working at a basic level. The issue I am having is with data. I was going to deploy OpenNMS, but I noticed Xymon has graphing capabilities. One tool would be awesome. However, I am running into issues. I have tried installing all prerequisite RPM's, and even tried installing the packages via configure/make, but I just can't get xymon to find the graphing include files or libraries. I have done quite a few searches and nothing is really working for my case. I even used the --rddinclude DIR and -rrdlib DIR flags as it suggested with appropriate substitutions and pointing straight at it hasn't worked. I would really appreciate some help here. Perhaps I installed the wrong base configuration (webserver, no GUI). I am pointing to YUM and can download any packages needed. If I can download via YUM that would be preferred, but if compiling myself works better I have no fear or issue doing that. Once I get past this I am sure they will be happy with the tool and I can move forward installing agents, but my question concerning that can wait for another day. Thanks. John Langbein

2 2

apache trying to execute cgi man pages
by bferrell＠baywinds.org 19 May '16

19 May '16

I'm getting some errors that are making me nuts when I access the man pages for the cgi programs The apache log shows this: Options ExecCGI is off in this directory: /home/xymon/server/www/help/manpages/man1/ackinfo.cgi.1.html, referer: http://server.org/xymon/help/manpages/man1/ And of course, when I add ExecCGI I get: Premature end of script headers: ackinfo.cgi.1.html The server is scientific linux 6 Suggestions?

2 5

Client test script fails when run by xymon, works when run manually - SOLVED
by moregrey＠gmail.com 19 May '16

19 May '16

Thanks for the suggestions. The "su xymon" was the clincher; it turns out this was indeed a permissions problem rather than an environment problem. bbcmd wasn't helping because I wasn't changing the user running the script. I modified the user permissions of the xymon user and things worked fine. Thanks all! On Wed, May 18, 2016 at 9:49 PM, J.C. Cleaver <cleaver at terabithia.org> wrote: > Another possibility here is that there's a distinction between the client > and server environments that's causing it to not properly report in "to > itself." > > When running bbcmd, can you use bbcmd --env=/path/to/hobbitserver.cfg and > --env=/path/to/hobbitclient.cfg and see if there's a difference? > > > -jc > > > On Wed, May 18, 2016 2:19 pm, Jeremy Laidman wrote: > > A few ideas: > > > > Su to the xymon user first, then run bbcmd. > > > > Run the command "env > /to/env" in the script and compare the file > between > > xymon running and you running. > > > > Add "set -x" before the vboxmanage command and "set +x" after. > > > > Cheers > > Jeremy > > > > On Wed, 18 May 2016, 14:31 More Grey <moregrey at gmail.com> wrote: > > > >> Hello-- > >> > >> I have a xymon client test script that runs fine, as scheduled, > >> returning > >> the appropriate results. I added an additional test to the script that > >> fails when the script is run on schedule, but which succeeds when the > >> script is run manually. The new test is a call to VirtualBox's > >> VBoxManage > >> command, to list the existing VMs. When run by xymon, it appears that > >> the > >> call to VBoxManage is not being sent all the parameters. If I change the > >> command to just "VBoxManage", the command returns the help message for > >> VBoxManage. If I change the command to "VBoxManage list", the command > >> returns the help message for the "list" command. But the command > >> "VBoxManage list vms" returns nothing. When the script is run manually > >> or > >> within bbcmd, the call to "VBoxManage list vms" works as expected. > >> > >> Below is a version of the script with just my new test (plus plenty of > >> debugging info): > >> > >> #!/bin/sh > >> # wrapper for firing off the client tests > >> > >> echo $(date) "!!! testing VBoxManage" > >> echo $(date) "!!! HOBBITCLIENTHOME=$HOBBITCLIENTHOME" > >> echo $(date) "!!! BBHOME=$BBHOME" > >> echo $(date) "!!! calling VBoxManage:" > >> /usr/lib/virtualbox/VBoxManage list vms > >> echo $(date) "!!! return code = $?" > >> echo $(date) "!!! after VBoxManage" > >> > >> When this script runs as part of normal xymon operation (every 5 > >> minutes, > >> in this case), I get the following output in my log file: > >> > >> Tue May 17 23:04:48 UTC 2016 !!! testing VBoxManage > >> Tue May 17 23:04:48 UTC 2016 !!! HOBBITCLIENTHOME=/opt/mon/hobbit/client > >> Tue May 17 23:04:48 UTC 2016 !!! BBHOME=/opt/mon/hobbit/client > >> Tue May 17 23:04:48 UTC 2016 !!! calling VBoxManage: > >> Tue May 17 23:04:48 UTC 2016 !!! return code = 0 > >> Tue May 17 23:04:48 UTC 2016 !!! after VBoxManage > >> > >> But when I run the script directly from the tests.d directory, or when I > >> run it using bbcmd, I get the following output: > >> > >> 2016-05-17 23:08:46 Using default environment file > >> /opt/mon/hobbit/client/etc/hobbitclient.cfg > >> Tue May 17 23:08:46 UTC 2016 !!! testing VBoxManage > >> Tue May 17 23:08:46 UTC 2016 !!! HOBBITCLIENTHOME=/opt/mon/hobbit/client > >> Tue May 17 23:08:46 UTC 2016 !!! BBHOME=/opt/mon/hobbit/client > >> Tue May 17 23:08:46 UTC 2016 !!! calling VBoxManage: > >> "VM-00" {f428809a-e08e-2164-a52a-34405d323b18} > >> "VM-01" {8d9d188f-3f80-4fe4-99b2-7b740b3bd841} > >> [ output omitted ] > >> "VM-11" {77145415-2130-4280-84da-1b06e78a110f} > >> "VM-12" {b91ae190-74a9-a4e7-9643-142fab9b29a9} > >> Tue May 17 23:08:47 UTC 2016 !!! return code = 0 > >> Tue May 17 23:08:47 UTC 2016 !!! after VBoxManage > >> > >> I tried moving the VBoxManage command to a separate script and calling > >> the > >> script instead of the command; same behavior. I tried running the > >> VBoxManage command in a subshell within the script; same behavior. > >> Relying > >> on the environment PATH or specifying the full path of the VBoxManage > >> executable made no difference. If this were a permission problem, why > >> would > >> VBoxManage run at all (in the cases where it returns a help message)? > >> What am I missing here? > >> Thanks for any suggestions! > >> > >> _______________________________________________ > >> Xymon mailing list > >> Xymon at xymon.com > >> http://lists.xymon.com/mailman/listinfo/xymon > >> > > _______________________________________________ > > Xymon mailing list > > Xymon at xymon.com > > http://lists.xymon.com/mailman/listinfo/xymon > > > > >

1 0

disk graph page limits total file systems
by EDSchminke＠Hormel.com 19 May '16

19 May '16

Ron, Thanks for your reply... I find that unlikely for a number of reasons: 1) I'm seeing nothing in the xymon logs about messages being truncated 2) I can see the entire message on the xymon server, and the file systems I'm expecting to see graphed are in the message but are not being graphed... on the disk page 3) The file systems ARE graphed, but the graphs don't appear on the disk page... all filesystems are appearing on the trends page. JC (or anyone else)---- Could you suggest to me a way to run the portion that actually generates that page in a debug mode so I can see whats happening? As a command on a terminal, for example? Additional suggestions and questions are welcome! Thanks, Erik 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 From: Ron Cohen <rcohen55 at gmail.com> To: EDSchminke at hormel.com Date: 05/18/2016 03:59 PM Subject: Re: [Xymon] disk graph page limits total file systems Maybe it's to do with the sending msg size? On 18 May 2016 21:13, <EDSchminke at hormel.com> wrote: update: i upgraded v4.3.24 to v4.3.27. this had no effect on my problem. 85 filesystem "limit" still exists. 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 From: "J.C. Cleaver" <cleaver at terabithia.org> To: EDSchminke at Hormel.com Cc: "Xymon Mailing List" <xymon at xymon.com> Date: 05/17/2016 04:53 PM Subject: Re: [Xymon] disk graph page limits total file systems On Tue, May 17, 2016 11:26 am, EDSchminke at Hormel.com wrote: > > I'm having some trouble with the disk graph pages for hosts that have > numerous file systems reporting in. The limit seems to be 85. There are > 5 > file systems displayed on each graph and there are 17 graphs max on this > page. If I view the trends page for those host, all of the missing > filesystems are graphed. 85 seems pretty arbitrary. > > I've gone through and cleaned up the RRD files from $XYMON/data/rrd/$HOST > that are "stale". Cleaning some of these out, which would otherwise not > be > listed, permit the filesystems that were trimmed to then be listed on the > graph page. Still, not all of the filesystems make it on the graphs. > > I searched the mail archive, and didn't find a solutions. I found a > discussion of changing the [disk] section to [disk::10] for 10 filesystems > per graph... that prevented the graphs from being generated at all. My > thinking was, perhaps if i increase the number of filesystems per graph, > 17 > graphs would be enough for this particular system. > > In any event, I'm wondering if this is a bug or a configurable. It > actually works fine in a previous version of xymon. (v4.2.2 works, > v.4.3.24). 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 > Erik, 85 isn't an intentional hard limit here. I've been scanning through the showgraph code and it seems like the reallocation should be able to continue as needed (whether not having a hard limit at all is a good idea is a separate question...). There's a reference to 16 arguments to rrd_graph, however that's a per-graph value and I don't believe it would affect the number here. A couple of next steps: - Can you increase to disk::6 or 7 and see if there's a point where the parsing of that number breaks? - Does it constantly die at the same partition being graphed? - Are there any errors coming out in /logs/ or the httpd error log, or core files left? - Are there any unusual file conditions in that directory? I'd definitely suggest upgrading to a new version for security purposes, but I don't think any fixes addressing this area specifically are present. There were a lot of changes between 4.2.2 and 4.3.x, so it's hard to say exactly what might be contributing there. HTH, -jc _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

1 0