May 2016 - Xymon - Xymon mailman web

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

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

19 May '16

John, Xymon graphs the reported data, but not all the graphs show up on the disk page for a host that goes over 85 filesystems. The graphs appear on the "trends" page. Just not the disk page. I'm currently at version 4.3.27. I would need someone familiar with the code to review the relevant sections to see what differences exist between these versions. 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: John Palys <johnpalys at schoolpathways.com> To: EDSchminke at hormel.com Date: 05/18/2016 05:17 PM Subject: Re: [Xymon] disk graph page limits total file systems Ed, We use xymon version 4.3.7 and have 1051 filesystems which graph just fine. N o changes from base system other than the changes at the tail end of ../etc/xymonserver.cfg MAXMSG_STATUS="3145728" MAXMSG_CLIENT="3145728" MAXMSG_DATA="3145728" [root at sagan ~]# df |wc -l 1051 [root at sagan ~]# On Tue, May 17, 2016 at 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 _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon -- John Palys Systems Administrator School Pathways, Inc. 866-200-6936 #2010 Office

1 0

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

19 May '16

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!

3 2

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

18 May '16

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

2 3

routing between xymons
by rcohen55＠gmail.com 16 May '16

16 May '16

Hello there... we have here a pretty big production environments, and even bigger non-production. I've configured xymon for both, but the guys that do the actual monitoring objected to have alerts coming from non-production servers, since those are mostly non-crucial - they don't want to see any of those reds on their screens. I played for some time with the alert propagating, but it won't do, so sadly I disabled all the non-prod clients. The obvious solution (unless there's a simpler one) is to start another xymon on different port and different URL. the problem is that it requires a firewall setting, which is a major headache to make. what i thought of, is to do routing at the bb port, so incoming clients will be routed according to the IP origin to the prod and non-prod xymond (say ports 1985 & 1986). It is not difficult to implement, but before pythonizing it, i wonder if there is an existing solution within xymon which i missed, or anyone else already done it? many thanks _rony

4 5

Method to report/list all configured clients and their info.
by thomas.eckert＠IT-Eckert.de 15 May '16

15 May '16

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20160515/86812010/attach…>

1 0

xymon for AIX
by wonderfoo2＠gmail.com 14 May '16

14 May '16

Thanks for your feedback, Stef. Follow up on xymon for AIX. Here's what I have gotten on the client host running AIX7.1 1. xymon-4.3.27 2. pcre 8.32-1 C R Perl-compatible regular 3. make-4.0-1 lrwxrwxrwx 1 root system 27 Jul 24 2014 /usr/bin/gmake@ ../../opt/freeware/bin/make* Here's the output with configure.client: # MAKE=gmake ./configure.client Configuration script for Xymon client This script asks a few questions and builds a Makefile to compile Xymon Checking your make-utility Xymon normally keeps all of the client configuration files on the Xymon server. If you prefer, it is possible to use a local client configuration file instead - if so, answer 'client' to the next question. NB: Local configuration requires the PCRE libs on each host. Server side client configuration, or client side [server] ? client Checking for the PCRE libraries Checking for PCRE ... gmake: cc: Command not found Makefile.test-pcre:4: recipe for target 'test-compile' failed gmake: *** [test-compile] Error 127 ERROR: Cannot compile using PCRE library. gmake: cc: Command not found Makefile.test-pcre:7: recipe for target 'test-link' failed gmake: *** [test-link] Error 127 ERROR: Cannot link with PCRE library. Missing PCRE include- or library-files. These are REQUIRED for xymond PCRE can be found at http://www.pcre.org/ If you have PCRE installed, use the "--pcreinclude DIR" and "--pcrelib DIR" options to configure to specify where they are. Wonder if anything else I missed? Is pcre-devel also a pre-req for xymon client? Thanks!

2 1

Method to report/list all configured clients and their info.
by mburger＠bubbanfriends.org 13 May '16

13 May '16

Good morning, all. I've got a request from my security and monitoring team for a way to export a list of all configured clients along with their IP addresses and either descriptions or page/subpage locations. Other than providing them with a copy of hosts.cfg on a regular basis, I've been unsuccessful in locating a way to do so (either in the documentation/man pages, mailing list archives or just good old Google). Is there a method to do so from the Xymon interface? Maybe a plugin that I'm not, yet, aware of? -- Mike Burger http://www.bubbanfriends.org "It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1

5 5

Xymon Memory Monitoring enhancement
by soumitra.mishra005＠gmail.com 13 May '16

13 May '16

> > Hi Team, > > Is there any way to include the ballooned memory in the memory utilization > graph. >

2 2