February 2018 - Xymon - Xymon mailman web

Configuring alerts
by even.juberg＠artsdatabanken.no 20 Feb '18

20 Feb '18

Hi! I've been trying a few things to get the correct alerts to the correct staff-member, but for some reason I cannot get it to work. In order to find out if I'm doing something wrong within the configuration of Xymon, or if I have to search somewhere else, I'm reaching out here to see if anyone can give me any pointers. The scenario is that I have one particular host, that should be running a specific process. Let's say this process is "notepad.exe" - if "notepad.exe" is not running, John should get an email. What I have done so far is this: 1. Edited the configuration file on my host as follows in the "procs section": <setting name="notepad.exe" rule="=1" comment="Notepad" alarmcolor="red" /> a. My goal here is to check if there is one instance of notepad.exe running - if not, give a "red alert". b. This seems to be working. The host in the web-view of Xymon turns red in the procs column, and notepad.exe is shown as running -1 instance if there is not one running. So far so good! 2. Now I want John to be alerted if notepad is not running so I have edited the alert.cfg in the following way: a. HOST=myhostname(the same as in hosts.cfg NAME:myhostname) SERVICE=notepad.exe MAIL john at testlab.local<mailto:john at testlab.local> DURATION>10 COLOR=red b. As "notepad.exe is not a service, but a process this is not working. AS "procs" is not a valid argument(at least not listed in the documentation, SERVICE was the closest thing that came to mind. So my question is simply, is there a way to filter alerts by the procs column or will I have to attack this in another way? c. I would like to avoid John getting nagged by any other red-alerts from this host, as his responsibility is notepad. :) Any pointers would be highly appreciated! Sicnerely, Even Hauge Juberg Senior Engineer Norwegian Biodiversity Information Centre

3 2

How to setup a back-up xymon server
by wim.nelis＠ziggo.nl 18 Feb '18

18 Feb '18

Xymon is also used to monitor my home-network. One of the clients is a raspberry pi 0 (rpi0, IP address 192.168.178.71), which controls the home ventilation unit and which will monitor more in the near future as sensors are added. Sometimes the Wifi-connection is not operational for some time. The obvious results are that status messages do not reach the xymon server (IP address 192.168.178.72), and that the associated graphs (RRD's) are not updated. I would like to be able to check the graphs once the network connection is operational again. The current solution is to install a (secondary) xymon server, version 4.3.28, on rpi0 as well. (Note that there is no intention to use this xymon server for other purposes: there is no web server active on the rpi0, nor would I like to have a web server on this tiny computer.) The configuration file /etc/default/xymon-client on rpi0, which is included in file /usr/lib/xymon/client/etc/xymonclient.cfg, is modified to contain the addresses of both xymon servers: XYMONSERVERS="127.0.0.1 192.168.178.72" The default section and the host section for rpi0 in configuration file /usr/lib/xymon/server/etc/analysis.cfg is the same on both xymon servers. The client data arrives at the primary xymon server, resulting in tests and their associated graphs. When the need arise, the RRD files are copied from rpi0 to the primary xymon server, and can then be inspected. However, it seems that the data arrives twice at the primary xymon server. Xymond reports: Multi-source statuses rpi0:conn reported by 192.168.178.71 and 127.0.0.1 rpi0:cpu reported by 192.168.178.71 and 127.0.0.1 rpi0:disk reported by 192.168.178.71 and 127.0.0.1 rpi0:files reported by 192.168.178.71 and 127.0.0.1 rpi0:inode reported by 192.168.178.71 and 127.0.0.1 rpi0:memory reported by 192.168.178.71 and 127.0.0.1 rpi0:msgs reported by 192.168.178.71 and 127.0.0.1 rpi0:ports reported by 192.168.178.71 and 127.0.0.1 rpi0:procs reported by 192.168.178.71 and 127.0.0.1 The associated graphs one the primary xymon server are not complete: quite often de measurements of 2 or 3 consecutive periods of 5 minutes are missing. The xymon logfile rrd-status.log shows that multiple RRD updates, with slightly different values at about the same time, are the root cause of the incomplete graphs. In this situation I would like to stop the secondary xymon server from sending the test results to the primary xymon server. How can one achieve that? Regards, Wim Nelis.

2 2

checking on compatibility of XYMON/HOBBIT with Java 8 release 151
by Karthik.Mangu＠karauctionservices.com 15 Feb '18

15 Feb '18

Hello Xymon Team, May I know if XYMONN/HOBBIT are compatible with JAVA 8 release 151 as our security team want to upgrade it to avoid any security vulnerabilities with JAVA Thanks Karthik Mangu WMQ/IIB Administrator Integration Hosting Services KAR Auction Services, Inc. Desk: (317) 843 3175 Cell: (317) 601 9380

3 2

ipconfig:netstat:diskpart|route|ifstat|iis_sites not displaying in the gui
by ian.buckle＠gmail.com 08 Feb '18

08 Feb '18

I have just setup xymonPSClient on a windows server . I have been running it for ages on my unix servers. >From the windows server stuff like [cpu]. [memory] display in my xymon gui but things like the following do not ipconfig netstat diskpart route ifstatiis_sites Any thoughts? cheers Ian

2 1

xymon client host name not including domain name in systemd scripts
by Phil.Crooker＠orix.com.au 05 Feb '18

05 Feb '18

I've this issue with SUSE linux - SUSE just returns the plain hostname without the domain when it uses uname -n -- the xymon client then doesn't match the FQDN in the xymon hosts.cfg file, the entry goes purple and the client ends up in the ghost report. I'm compiling my own client and inserting the xymonlaunch.service file in /etc/systemd/system, etc -- somehow it doesn't send the correct hostname. I tried adding CLIENTNAME=blah.domain.com in xymonlaunch to no effect (also put it in the xymonclient config file, still no good). If I manually run /bin/hostname with the FQDN, that works, but is lost on the next reboot. And yes I ensured the FQDN is in /etc/hostname, etc... I do not want to have to put in a "CLIENT:whatever" statement in hosts.cfg for every host with a client, which works but is inelegant to me. Looking at the old runclient.sh script that comes with the client (and is not used with systemd), the MACHINEDOTS variable is set before launch. In the good ol SYS5 init.d days, I used to insert MACHINEDOTS=`hostname -f` in the runclient.sh script, which worked. So, I found if you run: systemctl edit xymonlaunch.service and add the following, it works: [Service] Environment="MACHINEDOTS=whatever.domain.com" This creates a /etc/systemd/system/xymonlaunch.service.d/override.conf file and all is well. Unfortunately it doesn't work with `hostname -f`. There is a warning that if there is no override.conf in whatever.service.d/ the service won't run. That isn't true with SUSE SLES 12, it works fine w/o it (less the correct name, of course), but YMMV... HTH Someone, Phil Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

5 5

State of the art for monitoring ESXi hosts?
by earle＠isolar.DynDNS.ORG 05 Feb '18

05 Feb '18

On 31 Jan 2018, at 11:07 AM, John Thurston <john.thurston at alaska.gov> wrote: > Can anyone offer a 'state of the art' statement regarding Xymon and > VMware ESXi hosts (versions 6.0 and 6.5)? Looking in the archives, I > see > a little content from several years ago. > > It's now 2018. What are y'all monitoring, and how are ya' doing it? We set up our ESXi hosts (all 6.0 at the moment) to point their syslog configs at our central syslog server, and then set up <syslog server>.msgs red & yellow alerts from what we get out of that. Crude but quasi-effective. (In case you've never set it up, ESXi hosts emit a FLOOD of syslog messages.) - Greg

2 1

State of the art for monitoring ESXi hosts?
by chrisp＠lightstoneauto.co.za 01 Feb '18

01 Feb '18

Will be very useful for us as well. Regards From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Kris Springer Sent: Wednesday, January 31, 2018 10:02 PM To: John Thurston <john.thurston at alaska.gov>; xymon at xymon.com Subject: Re: [Xymon] State of the art for monitoring ESXi hosts? I'd be interested in that as well. I abandoned those particular tests a while ago because they didn't give much info. Kris Springer On 01/31/2018 11:07 AM, John Thurston wrote: Can anyone offer a 'state of the art' statement regarding Xymon and VMWare ESXi hosts (versions 6.0 and 6.5)? Looking in the archives, I see a little content from several years ago. It's now 2018. What are y'all monitoring, and how are ya' doing it?

1 0