- Xymon - Xymon mailman web

findhost.sh search info/description?
by jon.dustin＠gmail.com 04 Feb '17

04 Feb '17

Greetings - I'm a longtime Xymon user (Hobbit and BB before that), and am finally able to start using Xymon in $currentJob. HUGE fan! This operation uses "app-specific" DNS CNAMEs for systems, which I have added as 'descriptions' in hosts.cfg. They show up properly when I hover over hostnames and when clicking the info button. What would REALLY be nice is to have findhost.sh be able to search this field in addition to hostnames. I looked through the archives for a bit of time and didn't find any discussion around this issue. Am I alone in this request? I can certainly dig into the source and see if I can add this functionality myself. Thanks for anything you can pass along.

1 0

drop a test without clearing its history?
by rlhamil2＠gmail.com 03 Feb '17

03 Feb '17

Can one drop the _current_ info for a test, without dropping its history? Sometimes a situation may arise that makes the current state invalid, and one might want to get rid of it; but the earlier history might still be useful. More broadly, can one remove specific history entries for a host/test?

1 0

Absolute free space value for DISK gone rogue?
by David.Mills＠hhsc.state.tx.us 03 Feb '17

03 Feb '17

All - I have a file system on a host which is alarming "red" even though the file system is brand new / empty. In the notes below, the mis-reporting filesystem is "/ora_data_estdmprd" The stanza in analysis.cfg that covers it is: HOST=pwdu008 # Stand-alone prod DB hosts: won't have shared FS's DISK /ora_bin 85 95 # 85%/95% = CRQ000000013038 DISK /ora_data 85 95 # 85%/95% = CRQ000000013038 DISK /ora_admin 85 95 # 85%/95% = CRQ000000013038 DISK /ora_temp 85 95 # 85%/95% = CRQ000000013038 DISK /ora_redoa 85 95 # 85%/95% = CRQ000000013038 DISK /ora_redob 85 95 # 85%/95% = CRQ000000013038 DISK /ora_arch 85 95 # 85%/95% = CRQ000000013038 DISK /ora_data_finprod1 85 95 # 85%/95% = CRQ000000013038 DISK /ora_finbin 85 95 # 85%/95% = CRQ000000013038 DISK %/ora_data_perpr 85 95 # 85%/95% = CRQ000000013038 DISK %/ora_ 262144000U 209715200U # I.e. Yellow: <= 256GB; Red <= 204.8GB The output from the "Disk" detail page for that host was: status pwdu008.disk yellow Tue Jan 31 14:06:20 CST 2017 - Filesystems NOT ok &red /ora_data_estdmprd (3045500329 units free) has reached the CRITICAL level (209715200 units) Filesystem kbytes used avail capacity Mounted on /dev/md/dsk/d1 16525754 7879972 8480525 49% / /dev/md/dsk/d4 20655025 2723628 17724847 14% /var /dev/md/dsk/d7 17197130 2708305 14316854 16% /export /dev/odm 0 0 0 0% /dev/odm sharefs 0 0 0 0% /etc/dfs/sharetab swap 147391344 1936 147389408 1% /etc/svc/volatile swap 147396208 6840 147389368 1% /tmp swap 147389344 0 147389344 0% /dev/vx/dmp swap 147384744 0 147384744 0% /dev/vx/rdmp /dev/vx/dsk/ORA_DATA/ora_data 249925632 5610862 229045230 3% /ora_data /dev/vx/dsk/ORA_ARCH/ora_arch 249958400 685078 233695152 1% /ora_arch /dev/vx/dsk/ORA_BIN/ora_bin 124930048 54292389 66222935 46% /ora_bin /dev/vx/dsk/ORA_ADMIN/ora_admin 62465024 202884 58405611 1% /ora_admin /dev/vx/dsk/ORA_REDOA/ora_redoa 124962816 833493 116371374 1% /ora_redoa /dev/vx/dsk/ORA_ARCH_ESTDMPRD/ora_arch_estdmprd 1749710848 966260000 777330408 56% /ora_arch_estdmprd /dev/vx/dsk/ORA_TEMP/ora_temp 999961600 521070 936975632 1% /ora_temp /dev/vx/dsk/ORA_REDOB/ora_redob 124962816 423857 116755408 1% /ora_redob /dev/vx/dsk/ORA_DATA_DMSTGPRD/ora_data_dmstgprd 4999072768 1751121 4728890415 1% /ora_data_dmstgprd /dev/vx/dsk/ORA_DATA_ESTDMPRD/oradata_estdmprd01 3249462272 929825 3045500329 1% /ora_data_estdmprd In the report above, we see that the "critical" threshold (in KB on Solaris) is 209,715,200 free space (about 256 GB), but the actual free space for that file system is 3,045,500,329 (around 3 TB). Something is clearly not right! Also, note the file system second-from-the bottom: /ora_data_dmstgprd. It has _even more_ free space and should be triggered by the same rule in analysis.cfg (DISK %/ora_ ...) yet it is not flagged as having a problem. As a stop-gap to keep the filesystem from alarming, I've had to change the "DISK" rule in analysis.cfg to percentages (85 95) which makes everything go green. Particulars: Xymon v. 4.3.3 running on Solaris 10 host. (Have also tried restarting the server without impact.) Any thoughts? Thanks! david ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ David Mills Systems Administrator Northrop Grumman (512) 595-1238 (mobile)

1 1

linux client disk warning levels
by kspringer＠innovateteam.com 02 Feb '17

02 Feb '17

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20170130/6cf79fc2/attach…>

7 8

Graphs not showing
by Wim.Nelis＠nlr.nl 31 Jan '17

31 Jan '17

Hello, my previous post was mangled because there were some snippets of HTML in it. Therefore the message is posted again, this time without HTML. the status of audio streams through an Open Digital Radio multiplexer is monitored in Xymon. A Perl script retrieves the status and statistics from the multiplexer, and sent them to Xymon. The statistics are to be shown in graphs. However, while the RR databases are build, no graphs are shown. I am using debian 8.6 with xymon 4.3.17. (An update to version 4.3.27 failed, as the configure script does not recognise rrdtool 1.4.8, resulting in a version of xymon which does not support trend graphs.) A perl script retrieves the status of (the input channels of) the multiplexer, and sends the message to xymon. The statistics are included in the format which is also used by devmon. The last part of the status message of test odr_mux contains the following as HTML comment: linecount=2 DEVMON RRD: odr 0 0 DS:PeakLeft:GAUGE:600:-100:100 DS:PeakRight:GAUGE:600:-100:100 \ DS:Underrun:DERIVE:600:0:U DS:Overrun:DERIVE:600:0:U \ DS:BufferMin:GAUGE:600:-1:U DS:BufferMax:GAUGE:600:0:U sub-ozo -90:-90:176972:0:-1:0 sub-urk -90:-90:176972:0:-1:0 In xymonserver.cfg two lines are adapted: TEST2RRD=".... ,odr_mux=devmon" GRAPHS=" .... ,odr_mux::1" The statistics are entered in RRD's: root at debian:/var/lib/xymon/rrd/OzoNop# ls -l odr* -rw-r--r-- 1 xymon xymon 114560 Jan 8 19:04 odr.sub-ozo.rrd -rw-r--r-- 1 xymon xymon 114560 Jan 8 19:04 odr.sub-urk.rrd root at debian:/var/lib/xymon/rrd/OzoNop# The graph definition is: [odr_mux] FNPATTERN ^odr\.(.+)\.rrd$ TITLE , Frame loss rate YAXIS Rate [/s] DEF:ur at RRDIDX@=@RRDFN@:Underrun:AVERAGE DEF:or at RRDIDX@=@RRDFN@:Overrun:AVERAGE LINE1:ur at RRDIDX@#FF0000:@RRDPARAM@ underrun GPRINT:ur at RRDIDX@:MIN:Min \: %5.1lf %s GPRINT:ur at RRDIDX@:MAX:Max \: %5.1lf %s GPRINT:ur at RRDIDX@:AVERAGE:Avg \: %5.1lf %s GPRINT:ur at RRDIDX@:LAST:Cur \: %5.1lf %s\n LINE1:or at RRDIDX@#00FF00:@RRDPARAM@ overrun GPRINT:or at RRDIDX@:MIN:Min \: %5.1lf %s GPRINT:or at RRDIDX@:MAX:Max \: %5.1lf %s GPRINT:or at RRDIDX@:AVERAGE:Avg \: %5.1lf %s GPRINT:or at RRDIDX@:LAST:Cur \: %5.1lf %s\n The web page of this test shows the two tables, but no graphs. Only the magnifying glasses, which should be on the right of a graph, are shown. When clicking on the magnifying glass, an empty page is shown. The source code of this page is two lines long, the first one specifying the title to be "Invalid request", the second on showing an empty body. Removing the graph definition results in a link to be displayed, and the magnifying glass shows an appropriate error message. Further experiments showed that if all multi-graph stuff is removed (that is, FNPATTERN and the @RRD...@ parameters) a single graph is shown. Extending the graph definition with FNPATTERN causes to problem to surface again. The logfiles of xymon do not contain messages related to this problem, as far as I can see. Enabling debugging for xymond_rrd, the one spawn by the status channel reader, does not give any helpful information. All the other graphs, including one multi-graph (test memory), of this host are displayed. The problem is only visible in test odr_mux. Can anyone give me a hint on how to proceed to solve this issue? Regards, Wim Nelis.

3 4

linux client disk warning levels
by kspringer＠innovateteam.com 30 Jan '17

30 Jan '17

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20170130/88406003/attach…>

1 0

odd behavior for UP rule
by erik＠schminke.us 30 Jan '17

30 Jan '17

I sent this in a while ago.. I got no response, so I need to bump it. It also seems to not be just the UP rule; I've since seen the problem with the PROC test as well. I don't quite understand why, but when I write a rule for a specific page, the rule seems to get randomly applied to hosts on the "top page". I say randomly, because it doesn't seem to always occur. I'm still haven't figured out the best way to use the component binaries of the Xymon system to troubleshoot issues like this; to know whether a config I have is causing a parsing error somewhere in the config files. In this case, nothing is appearing in any of the logs in my logs directory. I'm kind of at a loss... any help would be appreciated. Thanks!

1 0

TS - Is there a DB frontend for Xymon maintenance?
by erik＠schminke.us 30 Jan '17

30 Jan '17

In our enviornment, we use SVN. We committed the servers/etcdirectory to an SVN repository. Admins check out the files, make their edits, then commit them back to the repository. They then go to the Xymon server to do an "svn update". It makes the process a bit more cumbersome, to be sure, but has done a great job of keeping us from clobbering each others edits. SVN makes merging changes much easier.

1 0

script won't run in tasks.cfg but it will on the command line
by ralphmitchell＠gmail.com 27 Jan '17

27 Jan '17

The documentation for selenium/webdriver/remote/webdriver.py says: "Controls a browser by sending commands to a remote server." When you run it from the command line using xymoncmd, it will have access to your display and any browser that you have running. When xymon runs the same script as a task, it doesn't own the display, so it gets "connection refused". Probably. Ralph Mitchell On Fri, Jan 27, 2017 at 11:53 AM, usa ims via Xymon <xymon at xymon.com> wrote: > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > > > ---------- Forwarded message ---------- > From: usa ims <usaims at yahoo.com> > To: "xymon at xymon.com" <xymon at xymon.com> > Cc: > Date: Fri, 27 Jan 2017 16:46:08 +0000 (UTC) > Subject: script won't run in tasks.cfg but it will on the command line > Hi, > > I have this Python Selenium script that works if I go into the > '/usr/lib/xymon/server/bin/' and fire off 'xymoncmd' and execute the script > -- it reports to the Xymon Display and life is peachy. > > When I put the script in tasks.cfg, it runs at the desired internal of > every two minutes but it errors out. The script uses a combination of a > driver '/usr/local/bin/geckodriver' which I even gave 777 permissions on it > and changed ownership to 'xymon:xymon'. The script also uses an executable > script in '/usr/bin/firefox' which I gave '777' permissions on it. Any help > will be greatly appreciated. > > Here is the error message: > > Fri Jan 27 11:37:39 2017 > Traceback (most recent call last): > File "/usr/lib/xymon/server/ext/wslcb_licensee.py", line 31, in <module> > driver = webdriver.Firefox() > File "/usr/local/lib/python2.7/dist-packages/selenium/ > webdriver/firefox/webdriver.py", line 150, in __init__ > keep_alive=True) > File "/usr/local/lib/python2.7/dist-packages/selenium/ > webdriver/remote/webdriver.py", line 92, in __init__ > self.start_session(desired_capabilities, browser_profile) > File "/usr/local/lib/python2.7/dist-packages/selenium/ > webdriver/remote/webdriver.py", line 179, in start_session > response = self.execute(Command.NEW_SESSION, capabilities) > File "/usr/local/lib/python2.7/dist-packages/selenium/ > webdriver/remote/webdriver.py", line 236, in execute > self.error_handler.check_response(response) > File "/usr/local/lib/python2.7/dist-packages/selenium/ > webdriver/remote/errorhandler.py", line 192, in check_response > raise exception_class(message, screen, stacktrace) > selenium.common.exceptions.WebDriverException: Message: connection refused > > >

1 0

script won't run in tasks.cfg but it will on the command line
by usaims＠yahoo.com 27 Jan '17

27 Jan '17

Hi, I have this Python Selenium script that works if I go into the '/usr/lib/xymon/server/bin/' and fire off 'xymoncmd' and execute the script -- it reports to the Xymon Display and life is peachy. When I put the script in tasks.cfg, it runs at the desired internal of every two minutes but it errors out. The script uses a combination of a driver '/usr/local/bin/geckodriver' which I even gave 777 permissions on it and changed ownership to 'xymon:xymon'. The script also uses an executable script in '/usr/bin/firefox' which I gave '777' permissions on it. Any help will be greatly appreciated. Here is the error message: Fri Jan 27 11:37:39 2017Traceback (most recent call last): File "/usr/lib/xymon/server/ext/wslcb_licensee.py", line 31, in <module> driver = webdriver.Firefox() File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/firefox/webdriver.py", line 150, in __init__ keep_alive=True) File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/webdriver.py", line 92, in __init__ self.start_session(desired_capabilities, browser_profile) File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/webdriver.py", line 179, in start_session response = self.execute(Command.NEW_SESSION, capabilities) File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/webdriver.py", line 236, in execute self.error_handler.check_response(response) File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/errorhandler.py", line 192, in check_response raise exception_class(message, screen, stacktrace)selenium.common.exceptions.WebDriverException: Message: connection refused

1 0