- Xymon - Xymon mailman web

Support for TLS v1.1 and 1.2?
by ian.burrowes＠gmail.com 06 Jun '16

06 Jun '16

Hi David, This might not help at all, but when I had problems with xymon HTTPS and SSL checks on my Win2012 R2 ADFS server recently, it was actually the target website requiring Server Name Indication (SNI) support, rather than a TLS 1.1 / 1.2 issue. I was able to fix the problem by adding 'sni' on the end of the host entry in hosts.cfg. Please disregard this advice if not relevant, but perhaps it will help others :) Kind Regards, Ian On 7 June 2016 at 08:31, Gore, David W (David) via Xymon <xymon at xymon.com> wrote: > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > > > ---------- Forwarded message ---------- > From: "Gore, David W (David)" <david.gore at verizon.com> > To: "xymon at xymon.com" <xymon at xymon.com> > Cc: > Date: Mon, 6 Jun 2016 18:20:12 -0400 > Subject: [Xymon] Support for TLS v1.1 and 1.2? > > Mark Felder, > > > > Mentioned last year around April 17th, 2015 where Xymon support for TLS > v1.1 and v1.2 may be lacking. Perhaps the issue is more my naiveté but > does anyone know how I can get the sslcert and http tests to work correctly > with Apache and Xymon. > > > > [image: red] https://xymon1.domain.com/ - SSL error > > > > The sslcert test goes purple. > > > > Os: Red Hat Enterprise Linux Server release 7.2 (Maipo) > > Openssl: OpenSSL 1.0.1e-fips 11 Feb 2013 > > Xymon: 4.3.26 > > > > > > David W Gore > > > >

1 0

How to override testip?
by feld＠feld.me 03 Jun '16

03 Jun '16

How do you override testip for a single host? Looking at the code there's a flag for xymonnet called "dodns" that's not documented in hosts.cfg man page. It feels to me like the xymonnet code should be slightly altered to allow you to specify "dodns" on a per-host basis to override a "testip" setting that may be default. -- Mark Felder feld at feld.me

2 2

xymon for AIX
by wonderfoo2＠gmail.com 02 Jun '16

02 Jun '16

Hi Stef, Your last tip was helpful to get through with the hump on getting the AIX client compiled and initial install. I noticed the monitoring page (cpu,disk, memory) for the said client is not populated aside from the standard monitors coming off the server (conn,info,ssh,trends). the client log is throwing "Whoops ! Failed to send message (timeout)". I send in a debug for test to the server from the client, which is also timing out. Please advise. /xymon/logs # tail -10 xymonclient.log 2016-05-18 15:51:47.497327 -> Recipient '172.31.2.131', timeout 15 2016-05-18 15:51:47.497375 -> 1st line: 'client aixadm.aix aix' 2016-05-18 15:56:51.683098 Whoops ! Failed to send message (timeout) 2016-05-18 15:56:51.683283 -> 2016-05-18 15:56:51.683308 -> Recipient '172.31.2.131', timeout 15 2016-05-18 15:56:51.683352 -> 1st line: 'client aixadm.aix aix' 2016-05-18 16:01:56.124743 Whoops ! Failed to send message (timeout) 2016-05-18 16:01:56.127297 -> 2016-05-18 16:01:56.127323 -> Recipient '172.31.2.131', timeout 15 2016-05-18 16:01:56.127371 -> 1st line: 'client aixadm.aix aix' /xymon/bin # ./xymon --debug 172.31.2.131 test 9568302 2016-05-18 15:58:27.133743 Transport setup is: 9568302 2016-05-18 15:58:27.133913 xymondportnumber = 1984 9568302 2016-05-18 15:58:27.133926 xymonproxyhost = NONE 9568302 2016-05-18 15:58:27.133940 xymonproxyport = 0 9568302 2016-05-18 15:58:27.133953 Recipient listed as '172.31.2.131' 9568302 2016-05-18 15:58:27.133967 Standard protocol on port 1984 9568302 2016-05-18 15:58:27.133995 Will connect to address 172.31.2.131 port 1984 9568302 2016-05-18 15:58:42.134223 Timeout while talking to Xymon daemon at 172.31.2.131:1984 - retrying 9568302 2016-05-18 15:58:43.134348 Will connect to address 172.31.2.131 port 1984 9568302 2016-05-18 15:58:58.134561 Timeout while talking to Xymon daemon at 172.31.2.131:1984 - retrying 9568302 2016-05-18 15:58:59.134657 Will connect to address 172.31.2.131 port 1984 9568302 2016-05-18 15:59:14.134814 Closing connection 2016-05-18 15:59:14.134870 Whoops ! Failed to send message (timeout) 2016-05-18 15:59:14.135049 -> 2016-05-18 15:59:14.135099 -> Recipient '172.31.2.131', timeout 15 2016-05-18 15:59:14.135185 -> 1st line: 'test' Thank you.

9 21

question
by m.pingel＠ndr.de 02 Jun '16

02 Jun '16

Hi, is it possible to configure a maximum level of memory from a process? Thanks Mit freundlichen Grüßen Matthias Pingel

3 2

Xymon all red page minor bug question and patch
by spah＠syntec.co.uk 02 Jun '16

02 Jun '16

Hi, I found the Xymon all red page (red.html) added in 4.3.11 (r7180) with a bit of Googling, but (a) it is not in xymonmenu.cfg so it is not visible by default (trvial patch to config attached to fix this), (b) (the minor bug) it displays 'Current non-green Systems' at the top of the page instead of e.g. 'Current red Systems', and (c) is there any way it can display the most recent events, like the actual nongreen.html page does? I did look at the diffs from the commit that added this feature, but I couldn't see anything there to customize the header of the page (or any reason why it would be suppressing the most recent events view). Kind regards, Sebastian Auriol

1 0

acknowledge alert
by Jurgen.Claessens＠cegeka.be 02 Jun '16

02 Jun '16

Hello all, Currently we are still running xymon 4.3.17 on our servers, but are looking to update them to the latest version. We acknowledge alerts thru a custom webpage layout that sends it to our 2 servers. In 4.3.17 this worked like a charm, but on the newer versions this does no longer work. I know from 4.3.18 things have been made more secure in part of the acknowledge.sh and stuff, but is there still a way to acknowledge thru http? Best regards, Jurgen Claessens This e-mail and all files transmitted as attachment(s) thereto are confidential and solely intended for the individual to whom or the organization to which they are addressed. If you received this e-mail by mistake, please notify Cegeka's Service Desk at cegeka.support at cegeka.be or call +32 (0)11 240 363. We thank you in advance. Cegeka hereby confirms that this message has been swept by Sophos for the presence of viruses.

1 0

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