July 2021 - Xymon - Xymon mailman web

Removing Columns and http monitoring 401 error
by Cory.Fiala＠bethel.k12.or.us 16 Jul '21

16 Jul '21

Hello all, I somehow created 2 new columns in the dashboard while I was trying to fix a http monitor. I've removed my changes and the columns still show up. How do you remove them from the dashboard? My second issue is I'm wanting to monitor a URL and am only wanting to know if its alive. Since it requires authentication I'm getting HTTP status 401 error. How can I only monitor if it's up or down? Here is the last thing I've tried: xxx.xxx.xxx.xxx fs1 # httpstatus=http;https://workfolders.somesite.k12.or.us;200 Thanks! Cory

2 1

More patches for SNMP processing
by bscott＠bunyatech.com.au 14 Jul '21

14 Jul '21

Hi List, Having now completed my investigation into SNMP handling in Xymon, I have some more changes to propose.? Basically, this change introduces an extra method for finding indexes in SNMP tables when nothing that is provided is unique. I've also allowed for negative values and decimal points in returned data since both seemed to happen very quickly for me (no, the negative values weren't an error - they were wireless signal strengths). I have some documentation updates in progress to try and fill some of the holes in this area. I send them soon. Cheers, Brian Scott

1 0

fresh install xymon shows exe contents on screen
by oei＠zeelandnet.nl 14 Jul '21

14 Jul '21

Hello, After a fresh install xymon 4.3.30 on a new server (ubuntu 20.04 ) the website shows up. When I use a link to a html file on the server there is no problem (allnongreen view, main view) If the link uses the cgi folders then the screen is filled with (I Think) the contents of an excutable. Starting with the text ELF. I can't find errors in the apache2 logs and also the xymon logfiles shows nothing to work with. Where should I look to fix this. I want to migrate my current hobbit configuration from a centos 7 machine to this one Thanks

4 3

Checking clients from two proxies simultaneously
by zechner＠vrvis.at 13 Jul '21

13 Jul '21

Hi, I've got a few clients in a separate subnet which I want to check via two xymon servers (= proxies with multiple network interfaces) which then send the results to a central xymon server. Client: X Proxy 1: A Proxy 2: B Xymon Server: C So A and B have their own network checks defined in tasks.cfg [1] for multiple networks, in this case "mgmt". Both A and B report their result for X to Server C, which works fine, as long as A and B are responsive. If either A or B fail to successfully connect to X, connection checks on C turn red and fail. According to an old mailing list entry [2] all the checks' results should be merged at the server, or did I misunderstand? I thought as long as A or B can connect fine to X, everything in xymon should be fine, because after all, target X is up. Is there any other way to achieve what I am trying to do? Thanks in advance! Best regards Christoph Zechner [1] [xymonnetmgmt] ENVFILE /usr/lib/xymon/server/etc/xymonserver.cfg CMD XYMONNETWORK=mgmt xymonnet --report --ping --checkresponse --concurrency=4 LOGFILE $XYMONSERVERLOGS/xymonnet.log INTERVAL 5m [2] https://lists.xymon.com/archive/2006-May/006833.html

2 2

linked libs test warning bpfilter_umh
by rich＠slyone.org 11 Jul '21

11 Jul '21

I have the following installed on Ubuntu server 20.04, hobbit-plugins/focal,now 20191218 all xymon/focal,now 4.3.30-1 amd64 xymon-client/focal,now 4.3.30-1 amd64 Many of my hosts keep getting the yellow warning on the libs test: Sat Jul 10 23:21:58 2021 - libs NOT ok [green] Newest kernel is running: 5.4.0-77-generic, version #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 [yellow] The following processes have libs linked that were upgraded: root: / (deleted) (768) The system is up to date, and I have not run an update since the last reboot That process is bpfilter_umh. Reboot does not seem to clear it. Not all of my hosts have it, but many do. Why is it (deleted) and how can I clear it? Regards Rich

2 2

Trouble starting ext test to rrd, graph
by josh＠imaginenetworksllc.com 09 Jul '21

09 Jul '21

I wrote a script that will pull out a few lines of unbound stats and that submission appears good. I've got a green column by the host on the Xymon server. The web page is showing this: totalnumqueries:51 totalnumqueries_ip_ratelimited:0 totalnumcachehits:22 totalnumcachemiss:29 totalrecursiontimeavg:0075215 numquerytcp:0 numquerytcpout:0 numanswerrcodeSERVFAIL:0 unwantedqueries:0 unwantedreplies:0 The part where I'm stuck at is that it won't generate RRD files. From the help page it suggests Ijust add a value to TEST2RRD and NCV_ like I've done here: TEST2RRD="<allTheDefaultsHere>,unboundstats=ncv" NCV_unboundstats="totalnumqueries:GAUGE,totalnumqueries_ip_ratelimited:GAUGE,totalnumcachehits:GAUGE,totalnumcachemiss:GAUGE,totalrecursiontimeavg:GAUGE,numquerytcp:GAUGE,numquerytcpout:GAUGE,numanswerrcode.SERVFAIL:GAUGE,unwantedqueries:GAUGE,unwantedreplies:GAUGE" Something odd I did notice was that the link to the graphs (which have no images, no rrd, etc) will say "No DS called 'inodecache' in 'unboundstats.rrd'". What is the reference to inodecache? I have restarted it with xymonlaunch on the server. Now the data/rrd/ directory doesn't contain a host dir, I'm pretty sure that is something that will be created by Xymon. Any idea what I'm doing wrong? Josh Luthman 24/7 Help Desk: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

4 5

Problems with 'COMPACT'
by colin.coe＠gmail.com 06 Jul '21

06 Jul '21

Any thoughts on this? I've had a look at the source but can't see anything obvious. Thanks On Tue, 29 Jun 2021 at 06:12, Colin Coe <colin.coe at gmail.com> wrote: > Hi all > > I'm trying to use the 'COMPACT' directive for a few custom tests. My > config looks a it like: > 1.1.1.1 a_fim # noconn COMPACT:fim=fim_test1|fim_test2|fim_test3|fim_test4 > NOCOLUMNS:conn,info,trends > 1.1.1.2 b_fim # noconn COMPACT:fim=fim_test1|fim_test2|fim_test3|fim_test4 > NOCOLUMNS:conn,info,trends > 1.1.1.3 c_fim # noconn COMPACT:fim=fim_test1|fim_test2|fim_test3|fim_test4 > NOCOLUMNS:conn,info,trends > > The problem is that the first compacted test (fim_test1) seems to not get > included in the compacting (ie, it shows on the non-green page) and if any > of the compacted tests for any host are non-green, every host with the > compacted test is shown on the non-green page. > > Anyone else having this problem or have I configured it wrong? > > Thanks > >

3 3

My SNMP collection adventure
by bscott＠bunyatech.com.au 01 Jul '21

01 Jul '21

Hi, Just in case anyone wants to follow how I've got SNMP data collection and trend graphing working, I've done a bit of a write up. https://www.dropbox.com/s/ftn695y3fv4ykur/Misc%2022%20Xymon%20SNMP.docx?dl=0 It would be nice to get this up into documentation somewhere (with any suggested improvements) but not sure where. The wikibooks site looks very out of date (more discussion about hobbit than xymon) but nothing else seems appropriate. Cheers, Brian Scott

2 1

A few patches to improve SNMP data collection
by Brian.Scott＠bunyatech.com.au 01 Jul '21

01 Jul '21

Hi, I've been poking about with SNMP data collection with xymon for the last few days and have a few patches that may be useful for the next release, or for others exploring SNMP processing. The one for snmpmibs.cfg is from a post by Jeremy Laidman a while back so may already be in source control. It just removes a unwanted '(' from a mib definition. Thanks. The graphs.cfg patch is for typing mistake in the graph definition for ifmib and ifmib1. The xymon-snmpcollect.c one is for a programming error in automatically finding the snmphosts.cfg file if not specified on the command line. Finally, the showgraph.c patch is an enhancement to create a new substitutable, @BLANK@, that outputs blanks to take up the same space as @RRDPARAM@ in the graph legend. I've done a bit of a write-up of what I've done/found which I'll send a link to in the next few days. Cheers, Brian Scott

2 1

Patch for vmstat processing for FreeBSD
by Brian.Scott＠bunyatech.com.au 01 Jul '21

01 Jul '21

Hi, Another patch that I wanted to keep apart from the others I've just posted because it isn't really related. I seem to have 2 problems when dealing with vmstat output from FreeBSD. * Unknown variable disk_fd0 when updating the rrd. * Insufficient columns of data provided. I'm not sure if anything cares about data from vmstat or if it's just stamp collecting. The data doesn't have much value. The messages are annoying though. Anyway, the problem is that the FreeBSD vmstat command has a variable number of disks displayed. In early versions of FreeBSD (5 and earlier) there were a maximum of 3 devices selected and now (6 and later) there is a maximum of 2. The problem occurs when there aren't that many devices attached. The system will pick any junk it can find to make up the numbers (e.g. pass0) but when that fails, it just displays less devices. On a virtual system you will commonly only have one disk device attached. No CDs. No Floppy disks. If the attached disk doesn't attach through the CAM layer, there won't be a pass0 device created (it's not really a disk anyway). I have a few virtual systems running using a virtual block device (vtbd) as the only device attached. vmstat can't make anything up so only displays one device. What this means is that there are no guarantees that you will have the same number of devices on a given system from time to time as devices come and go. It also means that apart from the first disk which will be the main system disk, the actual device types may vary from time to time. They are essentially worthless. On a server with many disks attached, you will only see the first 2 so the data is incomplete. My approach has been to ignore all but the first disk and discard the rest, whether there be 0, 1 or 2 extras. No good for multi-disk servers, but then it wasn't anyway. I also cleaned up the column ordering stuff for older systems because it was wrong according to old man pages. Nobody will have a FreeBSD 4 or older system to test this on though. I'd be interested to know if other systems have variable behaviour like this in their vmstat processing that should be addressed. FreeBSD had special treatment in the code dating back to the transition from the maximum of 3 devices to 2. As I said before, I don't know if anything takes this data seriously. There is mention in the file about LARRD compatibility but that seems to be really ancient compatibility that I couldn't check. Cheers, Brian Scott

1 0