July 2013 - Xymon - Xymon mailman web

Windows Client
by Neil.Simmonds＠express-gifts.co.uk 07 Aug '13

07 Aug '13

I know this has probably come up before but does anyone know if there is an alternative Windows client to BBWin that actually works. I've got problems with both 0.12 and 0.13 versions of the client. 0.12 doesn't seem to work on Windows Server 2008 and 0.13 has a memory leak. This issue has been recently raised on the BBWin sourceforge big list and the reply was, 0.13 is mostly just a port from VS 2008 to VS2010. I don't have the time to spend on improving it and to be honest it's probably not worth spending the time. We really need a client developed on C# so that it can take advantage of .NET's capabilities of hooking into the OS much more cleanly. I appreciate that this is open source software and as such I don't expect people to jump on it and fix it, however it appears that BBWin may not be fit for purpose in the near future. I've looked at MrBig and WinPSClient but MrBig seems to have no one maintaining the code and WinPSClient hasn't been changed in 2 ¼ years. Is anyone aware of any other options or has anyone considered perhaps writing something? I'd look into it myself but I'm not a programmer so although my VBScript and Shell script abilities are reasonable I wouldn't really be comfortable attempting something like this even though I have started to look at learning C#. Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151. Express Gifts Limited is authorised and regulated by the Financial Services Authority -------------- NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT helpdesk on +44(0) 1254 303030

9 17

postgresql
by martin.flemming＠desy.de 02 Aug '13

02 Aug '13

Hi ! Got anybody an addon for monitoring for a postgresql-db ? I've find only theses two threads http://lists.xymon.com/oldarchive/2008/04/msg00163.html .. the server is not reachable anymore :-( http://lists.xymon.com/oldarchive/2008/04/msg00163.html .. not very helpful for me :-( thanks & cheers Martin

3 3

Memory Monitor Solaris 10 Client
by torsten.ogrissek＠pixelpark.com 02 Aug '13

02 Aug '13

Dear Xymon-Team, we have mentioned a problem with our memory monitors for solaris clients. the data shown on the page of every monitor for solaris are the mirrored like it is - let me explain. We have installed munin and xymon on a solaris 10 machine, so that we can compare the data from both tools. If munin and the system says the current memory used is 48% --> xymon shows 52%. If munin and the system shows that 15% are currently used - xymon shows 85%... and so on. We currently use Xymon server 4.3.10 and solaris client 4.3.7. Do you have any idea, what we can do, is it a bug - maybe fixed in newer client versions, or do we have to configure something for the correct data? Regards Torsten

3 3

Monitoring process with regex - fails with 4.3.12
by john.horne＠plymouth.ac.uk 31 Jul '13

31 Jul '13

Hello, I have just upgraded some client servers from Xymon 4.3.10 to 4.3.12. Two clients now continuously report that a specific process (clamd) is not running. (I have checked both servers and the process is running.) In the monitoring server analysis.cfg file I have (for both clients): PROC "% clamd$" TEXT=clamd This worked fine for 4.3.10, but now seems to fail. We have some other process strings containing 'clamd', so we had to use the above to ensure that we were just monitoring the main 'clamd' process. However, the 4.3.12 'Changes' file does mention: * Linux clients now align "ps" output so it is more readable. I'm not sure if that is relevant. I'll see if I can test things a bit further to see what is happening. John. -- John Horne, Plymouth University, UK Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001

2 2

[Xymon] XyMon 4.3.12 - what about HTTPS problems repoirted for 4.3.11 ?
by henrik＠hswn.dk 31 Jul '13

31 Jul '13

Hi, all indications are that this is an OpenSSL library problem (present in OpenSSL 1.x, but not in the older 0.9.x versions). Debian has this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702635 SuSE has this: http://lists.opensuse.org/opensuse-bugs/2013-05/msg01048.html It appears that the problem only shows up when testing sites with specific SSL implementations; e.g. I've seen it when connecting to some IIS versions. Apparently, a work-around is to force the use of SSLv3 instead of TLSv1; you can do that by changing the URL in hosts.cfg so it has "https3" instead of just "https". Regards, Henrik Den 25.07.2013 07:54, Andrey Chervonets skrev: > Good day! > > I still not received any reply for my previous messages about https > tests problems in 4.3.11 or due openssl-1.0.nnnn. > Does 4.3.12 have fixes for that? > > Or what should be the steps to find root cause and fix? > Just tell me in which direction should I go, I am not going to tale > much of Your time. > > P.S. Really, I am surprised nobody else reported similar problems. I > fill I have done something wrong. :( > > Best regards, > > Andrey Chervonets > ---------------------- > SIA CoMinder > http://www.cominder.eu/ > > From: Andrey Chervonets/Cominder/LV > To: henrik at hswn.dk, > Date: 19.06.2013 09:41 > Subject: Re: Fw: [Xymon] HTTPS problems in 4.3.11 > > ------------------------- > > Good day, Henrik! > > Do You have any idea why we have such problems and how it can be > fixed? > I can send "make" and "make install" logs if this can help. > > Best regards, > > Andrey Chervonets > ---------------------- > SIA CoMinder > http://www.cominder.eu/ > mobile: +371 26517848 > > From: Andrey Chervonets/Cominder/LV > To: henrik at hswn.dk, > Date: 13.06.2013 09:04 > Subject: Fw: [Xymon] HTTPS problems in 4.3.11 > > ------------------------- > > just for information: > > XyMon 4.3.4 where everything is OK: > -bash-3.2$ ./xymonnet --version > xymonnet version 4.3.4 > SSL library : OpenSSL 0.9.8e-rhel5 01 Jul 2008 > LDAP library: OpenLDAP 20343 > > -bash-3.2$ rpm -q openssl openssl-devel > openssl-0.9.8e-12.el5_5.7 > openssl-0.9.8e-12.el5_5.7 > openssl-devel-0.9.8e-12.el5_5.7 > openssl-devel-0.9.8e-12.el5_5.7 > -bash-3.2$ cat /etc/issue > CentOS release 5.6 (Final) > ------------- > > Hosts where NOK: > > XyMon 4.3.11 on SuSE: > # rpm -q openssl libopenssl-devel > openssl-1.0.1e-1.1.1.i586 > libopenssl-devel-1.0.1e-1.1.1.i586 > > # cat /etc/issue > Welcome to openSUSE 12.3 "Dartmouth" > > ---------- > XyMonx 4.3.11 on CentOS: > $ rpm -q openssl openssl-devel > openssl-1.0.0-27.el6_4.2.x86_64 > openssl-devel-1.0.0-27.el6_4.2.x86_64 > > $ cat /etc/issue > CentOS release 6.4 (Final) > > ----- Forwarded by Andrey Chervonets/Cominder/LV on 13.06.2013 09:01 > ----- > > From: Andrey Chervonets/Cominder/LV > To: xymon at xymon.com, > Date: 13.06.2013 08:45 > Subject: Re: [Xymon] HTTPS problems in 4.3.11 > > ------------------------- > >> ------------------------------ > > > > Message: 13 > > Date: Wed, 12 Jun 2013 08:00:28 +0200 > > From: Henrik St?rner <henrik at hswn.dk> > > To: xymon at xymon.com > > Subject: Re: [Xymon] HTTPS problems in 4.3.11 > > Message-ID: <51B80E7C.7030106 at hswn.dk> > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > Den 12-06-2013 07:19, Andrey Chervonets skrev: > > > I had found 2 problems that are reproducable only on 4.3.11 > XyMon > > > server (CentOS release 6.4 (Final)), > > > on 4.3.4 (CentOS release 5.6 (Final)) works fine. > > > > > > Problem 1) Some https resources reported with red (http) and > white > > > (content), while really it can be accessed > > > > Going from CentOS 5->6 also means upgrading the OpenSSL libraries > to > > version 1.0 (from 0.9.8e). I assume you compiled 4.3.11 on the new > server ? > > > > Check that SSL support is enabled in xymon: Run "xymonnet > --version" and > > check that there is a line with "SSL library: OpenSSL...." > xymonnet --version just returns > xymonnet version 4.3.11 > > RPMs are OK > $ rpm -q openssl openssl-devel > openssl-1.0.0-27.el6_4.2.x86_64 > openssl-devel-1.0.0-27.el6_4.2.x86_64 > > But I am was sure I had replied Y for SSL tests during installation. > To be double sure - I had renamed Makefile and run ./configure again > today > it was like: > .. > Checking for OpenSSL ... > Compiling with SSL library works OK > Linking with SSL library works OK > Checking if your SSL library has SSLv2 enabled > Will support SSLv2 when testing SSL-enabled network services > > Xymon can use the OpenSSL library to test SSL-enabled services > like https-encrypted websites, POP3S, IMAPS, NNTPS and TELNETS. > If you have the OpenSSL library installed, I recommend that you > enable > this. > > Do you want to be able to test SSL-enabled services (y) ? > Y > ... > > And resulting Makefile is the same as old. diff Makefile Makefile.old > returns nothing. > part of Makefile for SSL: > # > # OpenSSL settings > # > # OpenLDAP settings > LDAPFLAGS = > # > But... 4.3.4 has the same on machine where SSL is working > and ./xymonnet --version returns: > xymonnet version 4.3.4 > SSL library : OpenSSL 0.9.8e-rhel5 01 Jul 2008 > LDAP library: OpenLDAP 20343 > > I had checked on another one machine I had installed XyMon 4.3.11 > recently - OpenSUSE 12.3 > xymonnet --version returns the same output: xymonnet version 4.3.11 > and nothing more. > > Any ideas where could be the problem? > > Best regards, > > Andrey Chervonets > ---------------------- > SIA CoMinder > http://www.cominder.eu/

2 1

status of IPv6 support?
by herzog＠phys.ethz.ch 31 Jul '13

31 Jul '13

Dear Henrik, we run a moderately large xymon installation (> 8500 tests on > 850 hosts) and are lucky to also employ Axel Beckert, one of Debian's xymon package maintainers. This year we can (and have to) finally make our first steps into IPv6 territory and we decided early on that a working monitoring system is very high on the list. We are pretty happy with xymon and have repeatedly contributed to its well-being in the past. Hence we would very much like to stick with xymon also for our IPv6 monitoring. Reading the mailing lists, we got the impression that the upcoming 4.4/5.0 will be v6-ready and has progressed nicely. So we installed trunk [1] on a test server, and after writing a small patch to lib/loadhosts_file.c [2] we tried it in our IPv6 test net. Unfortunately we hit several road blocks (one of them being xymonnet2 intermittently crashing and not returning any output), which is just fair considering we're using unreleased trunk code. However, it leads us to the following questions: - do you have any indication when v5 will be ready for prime time (other than "Version 5 is currently (August 2012) under development, and is expected to be released later in 2012)"? - if you're in need of a) testers, b) code contributions or even c) financial incentives, we might be able to help out We are now at a crossroads where we have to decide whether to stay with (v6-ready) xymon or to switch to some other monitoring system. As already said: we'd like to stick around, but we do need v6 support at some point in the not-too-distant future. Thank you very much and kind regards, -Christian [1] http://sourceforge.net/p/xymon/code/7197/tree/trunk/ [2] 320c320,322 < sprintf(newitem->ip, "%d.%d.%d.%d", ip1, ip2, ip3, ip4); --- > char ipaddr[16]; > sprintf(ipaddr, "%d.%d.%d.%d", ip1, ip2, ip3, ip4); > newitem->ip = ipaddr; -- Dr. Christian Herzog <herzog at phys.ethz.ch> support: +41 44 633 26 68 IT Services Group, HPT H 8 voice: +41 44 633 39 50 Department of Physics, ETH Zurich 8093 Zurich, Switzerland http://nic.phys.ethz.ch/

3 8

Test update - ldom
by everett.vernon＠gmail.com 31 Jul '13

31 Jul '13

Hi all Some time back I wrote a "test" to provide visibility of resources allocated to LDOMs. >From the description, "This script was born from a need to give people visibility of the LDoms and available resources, but without giving them access to the control domain to gather this information" Some time since then, we were doing some capacity planning, Oracle license management, reallocation of resources, and planning a hardware refresh. It seemed like a good idea to graph the VCPU utilisation, just to get a better "view" of how much of the allocated resources we were using, and see if there were utilisation load spikes at certain times. So there it is. A simple information only script, now with graphs. https://wiki.xymonton.org/doku.php/monitors:ldom Regards Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton

1 0

patches
by henrik＠hswn.dk 30 Jul '13

30 Jul '13

Hi Tom, I am looking through your patches and I'll apply some of them but not others. Let me explain: > ./web/showgraph.c > Convert underscore to space to unmangle temperature and lic > param > names Not really sure about this. "temperature" has always been a bit step-motherly handled in Xymon because there is no standard tool for it, but I'm always afraid of changing filenames since other users may rely on them being the way they are. The "lic" status is a local add-on, it is not a standard Xymon test/status. I think a better way to create these RRD files the way you want them is to send in a "trends" data message where you can choose exactly how the RRD files are named, what data goes into them etc. That way you eliminate the need for xymond_rrd and showgraph tweaking. > ./xymond/etcfiles/columndoc.csv > Add help for lic, lpd, netbios-ssn, snpp and temperature columns I'll take the ones for the standard net protocols. > ./xymond/etcfiles/graphs.cfg > Change disk1 to autoscale disk usage instead of huge KB numbers > (another reason to store bytes instead of KB in RRDs) > Add total I/O to ifstat > Add lic graph for License Managers like FlexLM Changing the disk1 RRD to store bytes instead of kilobytes breaks compatibility with existing Xymon RRD files - I am not going to do that. Besides, I really cannot see the benefit of storing disk usage down to the byte-level. I've added the ifstat total. The lic graph remains one of your personal additions. > ./xymond/rrd/do_disk.c > Handle NetApp aggregates (diskaggr[0-9]*.rrd files) > Store bytes instead of kilobytes to be compatible with BB RRDs > (also for graphs.cfg disk1 patch above) What generates the "diskaggr" data ? I don't see anything in the NetAPP tester that I know (from Francesco Duranti) that collects data for this. Disk in bytes vs kB - no, as above. > ./xymond/rrd/do_temperature.c > Strip leading bold and italic HTML tags from sensor names (seen > on > yellow and red alerts from BB tests) OK, applied. > ./xymonnet/protocols.cfg > Improve smtp and smtps > Add lpd, netbios-ssn and snpp netbios-ssn, lpd and snpp added. smtp/smtps - no matter how you change them, some SMTP implementation is going to complain. I won't break it anymore for version 4; version 5 will fix this completely since it will implement the real protocol. Regards, Henrik

2 1

Xymon 4.3.12 released
by henrik＠hswn.dk 30 Jul '13

30 Jul '13

Hi, I have released version 4.3.12 of Xymon on Sourceforge, and it is available from http://sourceforge.net/projects/xymon/files/Xymon/4.3.12/ . Due to a security bugfix, I strongly recommend upgrading to this version. Regards, Henrik NOTE: This release includes a bugfix for a security issue in the xymond_history and xymond_rrd modules. A "drophost" command sent to the xymond port (default: 1984) from an IP listed in the --admin-senders access control list can be used to delete files owned by the user running the xymond daemon. This is allowed by default, so it is highly recommended List of changes: * rev 7211 * Security fix: Guard against directory traversal via hostname in "drophost" commands * Fix crash in xymongen introduced in 4.3.11 * SCO client: Fix overflow in memory calculation when >2 GB memory * Fix so "include" and "directory" definitions in configuration files now handle <tab> after the keyword * Fix for the Xymon webpage menu on iPad's and Android (touch devices) * Fix "drophost" handling so the host data directory is also cleared * xymond_rrd now processes data from "clear" status messages * Xymon clients now report the version number in the client data * Linux clients now align "ps" output so it is more readable. * New "generic" client message handler allows log/file monitoring from systems that are not known to Xymon. * The Xymon client now works if invoked with a relative path to the runclient.sh script * Other minor / internal bugfixes

7 13

http timeout
by Galen.Johnson＠sas.com 29 Jul '13

29 Jul '13

Hey, I'm sure I'm just missing something...where can you change the thresholds for the built-in http(s) tests? I'd like to set it to be a bit longer... =G=

2 4