July 2017 - Xymon - Xymon mailman web

Wormly & Xymon
by christopherrowson＠gmail.com 26 Jul '17

26 Jul '17

Just a quick one. Does anybody know whether or not the Wormly service www.wormly.com uses Xymon? I've noticed that Wormly uses BBWin as a monitoring agent: https://www.google.co.uk/search?q=bbwin+wormly Cheers, Chris

1 0

Strange Alerts
by john＠executech.com 25 Jul '17

25 Jul '17

I'm getting an extremely strange behavior with alerts. Several recipients are complaining that they are getting alerts for servers that they don't manage and aren't assigned. There are about 200 lines in my alerts.cfg file. I've verified that the alert rules are accurate and running the test alert script (./bin/xymoncmd xymond_alert --test sever.name cpu) shows the correct, assigned user and the info page for the servers show the right user's email. Anyone know what I'm missing? The same problems happened with my old Hobbit server as well so it could be a config file issue but I've looked thoroughly and haven't been able to track it down yet. John Tullis 801.857.4572 Cell 801.253.4541 Office 1314 W. 11400 S. Suite 200 South Jordan, UT 84095

3 2

Alerts not monitored on host
by zain1723＠gmail.com 24 Jul '17

24 Jul '17

Hello, I have setup a host to be monitored by xymon and i see that only conn and ssh are being monitored. I have other host for which all the services are being monitored but not for this. Both host have same kernel version they are using same xymon version. Please advice Thanks Zain

2 1

xymon with tls1.2
by ve2cii＠canasoft.net 24 Jul '17

24 Jul '17

Hi, Finally, I have succeeded at building the xymon against an updated opessl. root at dns8:~# openssl version OpenSSL 1.0.2h 3 May 2016 root at dns8:/home/xymon_test/server/bin# ./xymonnet --version xymonnet version 4.3.27 SSL library : OpenSSL 1.0.2h 3 May 2016 The way I did it was to replace the system openssl with openssl-1.0.2h. I used the system tools to repackage a slackware-14.2 package to slackware-12.1 package. Then I completely deleted the xymon build and untarred it fresh. Then I got proper results. Thank you all for the help, and I am testing. -- sysadm cronomagic.com/gemstelecom.com e-mail ve2cii at canasoft.net POWERED BY LINUX

2 2

xymon with tls1.2
by josh＠imaginenetworksllc.com 21 Jul '17

21 Jul '17

FYI the package over at Terabithia works with TLS 1.2 out of the box. I have an httpd that is TLS 1.2 only. http://terabithia.org/rpms/xymon/ Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Fri, Jul 21, 2017 at 10:41 AM, Henrik Størner via Xymon <xymon at xymon.com> wrote: > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > > > ---------- Forwarded message ---------- > From: "Henrik Størner" <henrik at hswn.dk> > To: Xymon mailinglist <xymon at xymon.com> > Cc: > Bcc: > Date: Fri, 21 Jul 2017 16:41:50 +0200 > Subject: Re: [Xymon] xymon with tls1.2 > Hi Frank, > > what happens if you leave out the --ssllib and --sslinclude parameters? It > is an unusual location for OpenSSL to be installed, so I guess you compiled > it yourself? > > It also ought to pull in libdl.so automatically, but that probably > requires some magic when compiling OpenSSL. > > Anyway, I believe you can work around it by setting NETLIBS in > xymon-4.3.27/build/Makefile.Linux like > > NETLIBS="-ldl" > > > Regards, > > Henrik > > > On 21-07-2017 16:26, Frank wrote: > >> I am re-sending this from my member account. >> >> Hi everyone, >> >> We are changing all our SSL web sites on windows over to tls1.2. So I >> have upgraded the >> openssl on the xymon server. >> >> I have run into an ssl issue compiling xymon-4.3.27 and xymon-4.3.28 >> >> openssl is in /usr/share/openssl-1.0.21 >> >> ./configure.server --ssllib /usr/share/openssl-1.0.21/lib --sslinclude >> /usr/share/openssl-1.0.21/include >> >> This is my error: >> >> Checking for OpenSSL ... >> Compiling with SSL library works OK >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function >> `dlfcn_globallookup': >> dso_dlfcn.c:(.text+0x1a): undefined reference to `dlopen' >> dso_dlfcn.c:(.text+0x31): undefined reference to `dlsym' >> dso_dlfcn.c:(.text+0x3b): undefined reference to `dlclose' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function >> `dlfcn_pathbyaddr': >> dso_dlfcn.c:(.text+0x81): undefined reference to `dladdr' >> dso_dlfcn.c:(.text+0xf8): undefined reference to `dlerror' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function >> `dlfcn_bind_func': >> dso_dlfcn.c:(.text+0x3fe): undefined reference to `dlsym' >> dso_dlfcn.c:(.text+0x46f): undefined reference to `dlerror' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function >> `dlfcn_bind_var': >> dso_dlfcn.c:(.text+0x4ee): undefined reference to `dlsym' >> dso_dlfcn.c:(.text+0x571): undefined reference to `dlerror' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function >> `dlfcn_unload': >> dso_dlfcn.c:(.text+0x5d7): undefined reference to `dlclose' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function >> `dlfcn_load': >> dso_dlfcn.c:(.text+0x697): undefined reference to `dlopen' >> dso_dlfcn.c:(.text+0x6f5): undefined reference to `dlclose' >> dso_dlfcn.c:(.text+0x72c): undefined reference to `dlerror' >> collect2: ld returned 1 exit status >> make: *** [test-link] Error 1 >> Warning: Cannot link with SSL library >> OpenSSL include- or library-files not found. >> >> >> > >

3 3

xymon with tls1.2
by ve2cii＠canasoft.net 21 Jul '17

21 Jul '17

Good thinking. Ok I have converted it to a tgz file and installed it. I am now working on copying the config (hosts etc) from the running version to this one. On 7/21/17 11:12, Galen Johnson wrote: > > From the days I worked with Slackware, I'm fairly certain there is a > conversion utility. It may even have and RPM package by now. > > > =G= > > ------------------------------------------------------------------------ > *From:* Xymon <xymon-bounces at xymon.com> on behalf of Frank > <ve2cii at canasoft.net> > *Sent:* Friday, July 21, 2017 11:01 AM > *To:* xymon at xymon.com > *Subject:* Re: [Xymon] xymon with tls1.2 > > */EXTERNAL/* > > Thanks, I just had a look at your link. We are running > slackware-12.1.0 32 bit. Which is > why I am compiling everything. Not sure if something for centos or > fedora will work. > > On 7/21/17 10:56, Josh Luthman wrote: >> FYI the package over at Terabithia works with TLS 1.2 out of the >> box. I have an httpd that is TLS 1.2 only. >> >> http://terabithia.org/rpms/xymon/ >> >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> On Fri, Jul 21, 2017 at 10:41 AM, Henrik Størner via Xymon >> <xymon at xymon.com <mailto:xymon at xymon.com>> wrote: >> >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com <mailto:Xymon at xymon.com> >> http://lists.xymon.com/mailman/listinfo/xymon >> <http://lists.xymon.com/mailman/listinfo/xymon> >> >> >> ---------- Forwarded message ---------- >> From: "Henrik Størner" <henrik at hswn.dk <mailto:henrik at hswn.dk>> >> To: Xymon mailinglist <xymon at xymon.com <mailto:xymon at xymon.com>> >> Cc: >> Bcc: >> Date: Fri, 21 Jul 2017 16:41:50 +0200 >> Subject: Re: [Xymon] xymon with tls1.2 >> Hi Frank, >> >> what happens if you leave out the --ssllib and --sslinclude >> parameters? It is an unusual location for OpenSSL to be >> installed, so I guess you compiled it yourself? >> >> It also ought to pull in libdl.so automatically, but that >> probably requires some magic when compiling OpenSSL. >> >> Anyway, I believe you can work around it by setting NETLIBS in >> xymon-4.3.27/build/Makefile.Linux like >> >> NETLIBS="-ldl" >> >> >> Regards, >> >> Henrik >> >> >> On 21-07-2017 16 <tel:21-07-2017%2016>:26, Frank wrote: >> >> I am re-sending this from my member account. >> >> Hi everyone, >> >> We are changing all our SSL web sites on windows over to >> tls1.2. So I have upgraded the >> openssl on the xymon server. >> >> I have run into an ssl issue compiling xymon-4.3.27 and >> xymon-4.3.28 >> >> openssl is in /usr/share/openssl-1.0.21 >> >> ./configure.server --ssllib /usr/share/openssl-1.0.21/lib >> --sslinclude /usr/share/openssl-1.0.21/include >> >> This is my error: >> >> Checking for OpenSSL ... >> Compiling with SSL library works OK >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In >> function `dlfcn_globallookup': >> dso_dlfcn.c:(.text+0x1a): undefined reference to `dlopen' >> dso_dlfcn.c:(.text+0x31): undefined reference to `dlsym' >> dso_dlfcn.c:(.text+0x3b): undefined reference to `dlclose' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In >> function `dlfcn_pathbyaddr': >> dso_dlfcn.c:(.text+0x81): undefined reference to `dladdr' >> dso_dlfcn.c:(.text+0xf8): undefined reference to `dlerror' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In >> function `dlfcn_bind_func': >> dso_dlfcn.c:(.text+0x3fe): undefined reference to `dlsym' >> dso_dlfcn.c:(.text+0x46f): undefined reference to `dlerror' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In >> function `dlfcn_bind_var': >> dso_dlfcn.c:(.text+0x4ee): undefined reference to `dlsym' >> dso_dlfcn.c:(.text+0x571): undefined reference to `dlerror' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In >> function `dlfcn_unload': >> dso_dlfcn.c:(.text+0x5d7): undefined reference to `dlclose' >> /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In >> function `dlfcn_load': >> dso_dlfcn.c:(.text+0x697): undefined reference to `dlopen' >> dso_dlfcn.c:(.text+0x6f5): undefined reference to `dlclose' >> dso_dlfcn.c:(.text+0x72c): undefined reference to `dlerror' >> collect2: ld returned 1 exit status >> make: *** [test-link] Error 1 >> Warning: Cannot link with SSL library >> OpenSSL include- or library-files not found. >> >> >> >> >> >> >> >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com >> http://lists.xymon.com/mailman/listinfo/xymon > > -- > > sysadm cronomagic.com/gemstelecom.com > e-mailve2cii at canasoft.net > > POWERED BY LINUX -- sysadm cronomagic.com/gemstelecom.com e-mail ve2cii at canasoft.net POWERED BY LINUX

1 0

xymon with tls1.2
by ve2cii＠canasoft.net 21 Jul '17

21 Jul '17

Hi, This did not work. It still uses the default system openssl. Hi Frank, what happens if you leave out the --ssllib and --sslinclude parameters? It is an unusual location for OpenSSL to be installed, so I guess you compiled it yourself? It also ought to pull in libdl.so automatically, but that probably requires some magic when compiling OpenSSL. Anyway, I believe you can work around it by setting NETLIBS in xymon-4.3.27/build/Makefile.Linux like NETLIBS="-ldl" On 7/21/17 10:41, Henrik Størner via Xymon wrote: > Hi Frank, > > what happens if you leave out the --ssllib and --sslinclude > parameters? It is an unusual location for OpenSSL to be installed, so > I guess you compiled it yourself? > > It also ought to pull in libdl.so automatically, but that probably > requires some magic when compiling OpenSSL. > > Anyway, I believe you can work around it by setting NETLIBS in > xymon-4.3.27/build/Makefile.Linux like > > NETLIBS="-ldl" -- sysadm cronomagic.com/gemstelecom.com e-mail ve2cii at canasoft.net POWERED BY LINUX

1 0

xymon with tls1.2
by ve2cii＠canasoft.net 21 Jul '17

21 Jul '17

Hi, I have removed the openssl that goes with the linux. That broke a bunch of stuff. So I had to put it back for now till I compile apache etc against the new ssl libraries. For now I am concentrating on xymon. The way it is xymon is "insisting" on using the old default ssl libraries. Hi Frank, what happens if you leave out the --ssllib and --sslinclude parameters? It is an unusual location for OpenSSL to be installed, so I guess you compiled it yourself? It also ought to pull in libdl.so automatically, but that probably requires some magic when compiling OpenSSL. Anyway, I believe you can work around it by setting NETLIBS in xymon-4.3.27/build/Makefile.Linux like NETLIBS="-ldl" Regards, Henrik On 7/21/17 10:41, Henrik Størner via Xymon wrote: > Hi Frank, > > what happens if you leave out the --ssllib and --sslinclude > parameters? It is an unusual location for OpenSSL to be installed, so > I guess you compiled it yourself? > > It also ought to pull in libdl.so automatically, but that probably > requires some magic when compiling OpenSSL. > > Anyway, I believe you can work around it by setting NETLIBS in > xymon-4.3.27/build/Makefile.Linux like > > NETLIBS="-ldl" > > > Regards, > > Henrik -- sysadm cronomagic.com/gemstelecom.com e-mail ve2cii at canasoft.net POWERED BY LINUX

1 0

xymon with tls1.2
by ve2cii＠canasoft.net 21 Jul '17

21 Jul '17

I am re-sending this from my member account. Hi everyone, We are changing all our SSL web sites on windows over to tls1.2. So I have upgraded the openssl on the xymon server. I have run into an ssl issue compiling xymon-4.3.27 and xymon-4.3.28 openssl is in /usr/share/openssl-1.0.21 ./configure.server --ssllib /usr/share/openssl-1.0.21/lib --sslinclude /usr/share/openssl-1.0.21/include This is my error: Checking for OpenSSL ... Compiling with SSL library works OK /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_globallookup': dso_dlfcn.c:(.text+0x1a): undefined reference to `dlopen' dso_dlfcn.c:(.text+0x31): undefined reference to `dlsym' dso_dlfcn.c:(.text+0x3b): undefined reference to `dlclose' /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_pathbyaddr': dso_dlfcn.c:(.text+0x81): undefined reference to `dladdr' dso_dlfcn.c:(.text+0xf8): undefined reference to `dlerror' /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_func': dso_dlfcn.c:(.text+0x3fe): undefined reference to `dlsym' dso_dlfcn.c:(.text+0x46f): undefined reference to `dlerror' /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_var': dso_dlfcn.c:(.text+0x4ee): undefined reference to `dlsym' dso_dlfcn.c:(.text+0x571): undefined reference to `dlerror' /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_unload': dso_dlfcn.c:(.text+0x5d7): undefined reference to `dlclose' /usr/share/openssl-1.0.21/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load': dso_dlfcn.c:(.text+0x697): undefined reference to `dlopen' dso_dlfcn.c:(.text+0x6f5): undefined reference to `dlclose' dso_dlfcn.c:(.text+0x72c): undefined reference to `dlerror' collect2: ld returned 1 exit status make: *** [test-link] Error 1 Warning: Cannot link with SSL library OpenSSL include- or library-files not found. -- Regards, Frank Torontour Network Administrator frank at cronomagic.com 514-341-1579 EXT-214 1-800-427-6012 Ext-214 -- sysadm cronomagic.com/gemstelecom.com e-mail ve2cii at canasoft.net POWERED BY LINUX

2 1

NSSM & Xymon PowerShell Client
by christopherrowson＠gmail.com 18 Jul '17

18 Jul '17

Hi list, I've been asked to look at a Xymon install which needs updating. The first thing I noticed was that the monitored Windows servers in the environment are using the old BBWin client which doesn't seem to be maintained any longer. Checking the mailing list I've noticed that a lot of people are now using the WinPSClient so I've been trying to familiarise myself with it. As I hadn't come across the software before, I ran the source for NSSM (the manager which runs the PS script as a service) past a C++ code analysis tool and it came out with a few /potential/ issues. The critical and high vulnerabilities are: Critical: Use of memmove Allows Buffer Overflow ------------------------------------------------------- - The size limit is larger than the destination buffer, while the source is a char* and so, could allow a buffer overflow to take place. - nssm-master\io.cpp Line 213 High: LoadLibrary ------------------ - The function searches several paths for a library if called with a filename, but no path. This can allow trojan DLLs to be deployed, regardless of the presence of the correct DLL. Manually check the code to ensure that the full path is specified. - nssm-master\imports.cpp Line 15 I'm not a C++ programmer, but looking at the code, the findings of the analysis tool look at least possible. Has anybody else performed code scrutiny against this aspect of the solution who can confirm or deny any issues? I also wondered if there's any particular reason why the PowerShell script can't be run at intervals by task scheduler instead of running as a service? Thanks, Chris

3 5