- Xymon - Xymon mailman web

How many times does xymonnet retry?
by glauber.ribeiro＠experian.com 13 Jan '16

13 Jan '16

Hello, all, I didn’t find this information in the man pages for xymonnet and xymonnet-again. How many times does xymonnet retry a failed test? Does it go red on the first failure (assuming default configuration), or only after all the retries failed? Thanks, glauber

4 6

Able to generate RRD but graphs do not show up
by kothari.raunak＠gmail.com 12 Jan '16

12 Jan '16

Hi all, I have a check in xymon to plot the time taken for several reports on the system to be run. For each report, I have xymon monitors that are collecting the data to the rrds but I am unable to populate the graph for these checks. Below is the output of rrdtool <info> on one of the rrds - filename = "SecondsElapsed.rrd" rrd_version = "0003" step = 300 last_update = 1446514863 header_size = 1216 ds[SecondsElapsed].index = 0 ds[SecondsElapsed].type = "GAUGE" ds[SecondsElapsed].minimal_heartbeat = 900 ds[SecondsElapsed].min = 0.0000000000e+00 ds[SecondsElapsed].max = NaN ds[SecondsElapsed].last_ds = "5" ds[SecondsElapsed].value = NaN ds[SecondsElapsed].unknown_sec = 63 rra[0].cf = "AVERAGE" rra[0].rows = 576 rra[0].cur_row = 258 rra[0].pdp_per_row = 1 rra[0].xff = 5.0000000000e-01 rra[0].cdp_prep[0].value = NaN rra[0].cdp_prep[0].unknown_datapoints = 0 rra[1].cf = "AVERAGE" rra[1].rows = 576 rra[1].cur_row = 481 rra[1].pdp_per_row = 6 rra[1].xff = 5.0000000000e-01 rra[1].cdp_prep[0].value = 0.0000000000e+00 rra[1].cdp_prep[0].unknown_datapoints = 2 rra[2].cf = "AVERAGE" rra[2].rows = 576 rra[2].cur_row = 382 rra[2].pdp_per_row = 24 rra[2].xff = 5.0000000000e-01 rra[2].cdp_prep[0].value = 0.0000000000e+00 rra[2].cdp_prep[0].unknown_datapoints = 20 rra[3].cf = "AVERAGE" rra[3].rows = 576 rra[3].cur_row = 338 rra[3].pdp_per_row = 288 rra[3].xff = 5.0000000000e-01 rra[3].cdp_prep[0].value = 0.0000000000e+00 rra[3].cdp_prep[0].unknown_datapoints = 20 Below is my graph definition in graphs.cfg (The column name in Xymon is "Status") [Status] FNPATTERN SecondsElapsed.rrd TITLE Report Execution time in seconds YAXIS Seconds DEF:SecondsElapsed=SecondsElapsed.rrd:SecondsElapsed:AVERAGE GPRINT:SecondsElapsed:LAST:Minutes\: %5.0lf (cur) Any clues why my graphs are not working ? Thanks! Regards, Raunak

2 1

Alerts
by john＠executech.com 11 Jan '16

11 Jan '16

I am getting strange behavior that I can't solve. I have specific users monitoring a subpage of servers. When I move a set of servers from one user (subpage) to another user (a different subpage), the new user is getting the alerts but the alerts are also going to previous user as well. One thing that helped in the past was to delete any data related to the set of servers in the subpage folder inside www. But recently that hasn't helped. Alerts are based on the page so that all subpages under them will alert them by default: PAGE=%.*UserPage/ SCRIPT=/custom-alerts/alert.sh user at domain.com RECOVERED REPEAT=720 DURATION>10 If I check the info page of any of the servers, the new user is listed but nothing is listed for the old user. Has anyone seen this before? John Tullis

1 0

Couple of questions on client data
by davieb＠gmail.com 11 Jan '16

11 Jan '16

I see that there is data in the client data that is not turned into columns? Can I turn this data into columns to report? I'm using xymon 4.3.20 on both the client/server. On linux, I see that this data is not turned into any columns: [who] [route] [netstat] [ifstat] Not that I'd use all of them, just wondering what the reasoning is behind it. Also, I notice that getting the data via xymondboard is not 100% either... [xymon at ztest bin]$ ./xymon 192.168.1.230 "clientlog yumlist section=who" [who] davieb tty1 May 11 21:01 (:0) davieb pts/1 May 11 21:02 (:0.0) davieb pts/2 May 11 21:40 (:0.0) As you can see below, requesting a status on all the tests, there is no "who" being reported. But just a moment ago, asking for just that data it works. [xymon at ztest bin]$ ./xymon 192.168.1.230 "xymondboard host=yumlist" yumlist|trends|green||0|0|0|0|0||| yumlist|info|green||0|0|0|0|0||| yumlist|uptime|green||1436045636|1452380534|1452382334|0|0|192.168.1.9||green Sat Jan 9 18:02:08 EST 2016 Uptime OK yumlist|memory|green||1431806850|1452380534|1452382334|0|0|192.168.1.9||green Sat Jan 9 18:02:08 EST 2016 - Memory OK yumlist|files|clear||1451081789|1452380534|1452382334|0|0|192.168.1.9||clear Sat Jan 9 18:02:08 EST 2016 - Files ok yumlist|msgs|green||1431807151|1452380534|1452382334|0|0|192.168.1.9||green Sat Jan 9 18:02:08 EST 2016 - System logs ok yumlist|ports|clear||1431806850|1452380534|1452382334|0|0|192.168.1.9||clear Sat Jan 9 18:02:08 EST 2016 - Ports ok yumlist|procs|green||1436043229|1452380534|1452382334|0|0|192.168.1.9||green Sat Jan 9 18:02:08 EST 2016 - Processes ok yumlist|inode|green||1431806850|1452380534|1452382334|0|0|192.168.1.9||green Sat Jan 9 18:02:08 EST 2016 - Filesystems ok yumlist|disk|green||1431806850|1452380534|1452382334|0|0|192.168.1.9||green Sat Jan 9 18:02:08 EST 2016 - Filesystems ok yumlist|cpu|green||1431806850|1452380534|1452382334|0|0|192.168.1.9||green Sat Jan 9 18:02:08 EST 2016 up: 289 days, 3 users, 261 procs, load=0.02 yumlist|hostinfo|clear||1432774838|1452380534|1452382334|0|0|192.168.1.9||clear Sat Jan 9 18:02:14 EST 2016 yumlist|cpu2|green||1431806845|1452380529|1452382329|0|0|192.168.1.9||green Sat Jan 9 18:02:09 EST 2016 yumlist|smart|green||1431806845|1452380528|1452382328|0|0|192.168.1.9||green SMART health check yumlist|fyi|green||1431806845|1452380719|1452382519|0|0|192.168.1.9||green Sat Jan 9 18:05:19 EST 2016 yumlist|rpc|green||1431805465|1452380560|1452382360|0|0|192.168.1.230||green Sat Jan 9 18:02:32 2016 rpc ok, yumlist|conn|green|OrdAsTLe|1431805465|1452380560|1452382360|0|0|192.168.1.230||green  Sat Jan 9 18:02:32 2016 conn ok

3 7

Couple of questions on client data
by novosirj＠ca.rutgers.edu 11 Jan '16

11 Jan '16

This is the info I need but it sounded like I can get it from historical periods, which is what I'm after. ____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* || \\UTGERS |---------------------*O*--------------------- ||_// Biomedical | Ryan Novosielski - Senior Technologist || \\ and Health | novosirj at rutgers.edu<mailto:novosirj at rutgers.edu>- 973/972.0922 (2x0922) || \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark `' On Jan 10, 2016, at 18:56, David Boyer <davieb at gmail.com<mailto:davieb at gmail.com>> wrote: Ryan, What specific data are you looking for? If it's the kernel version, this could pull the info: [xymon at xytest bin]$ ./xymon localhost "clientlog yumlist section=uname" [uname] Linux yumlist 2.6.32-504.12.2.el6.x86_64 x86_64 Or more detailed info: [xymon at xytest bin]$ ./xymon localhost "clientlog yumlist section=osversion" [osversion] CentOS 6.6 LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: CentOS Description: CentOS release 6.6 (Final) Release: 6.6 Codename: Final and grab what you need... Dave On Sun, Jan 10, 2016 at 6:31 PM, Novosielski, Ryan <novosirj at ca.rutgers.edu<mailto:novosirj at ca.rutgers.edu>> wrote: Actually: how do you get at this? I can't see a way after hunting around a bit. I thought maybe in a client data link at the bottom of a historical page, but none is present. ____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* || \\UTGERS |---------------------*O*--------------------- ||_// Biomedical | Ryan Novosielski - Senior Technologist || \\ and Health | novosirj at rutgers.edu<mailto:novosirj at rutgers.edu>- 973/972.0922<tel:973%2F972.0922> (2x0922) || \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark `' On Jan 10, 2016, at 06:48, J.C. Cleaver <cleaver at terabithia.org<mailto:cleaver at terabithia.org>> wrote: This becomes even more relevant when you consider snapshoting. When a status goes "red", a snapshot of the client data at that time is kept. So if you went back later to try to figure out why (e.g.) CPU was rising, the output of the '[who]' section tells you who might have been doing something then, even if the data wasn't used for making a test out of at that time.

3 3

Merging hosts
by thomleavitt＠gmail.com 09 Jan '16

09 Jan '16

Is there an easy (or even medium hard) way to merge the content of two hosts? I updated the entry for a server in Xymon to a fully qualified hostname, but the server is identifying itself with an unqualified hostname, and putting the CLIENT: tag fixed it, but for some reason, it seems to have lost track of the prior history. :/ Regards, Thomas Leavitt

2 1

vpage
by Galen.Johnson＠sas.com 08 Jan '16

08 Jan '16

Hey, I have a few pages that have lots of tests but few servers so I wanted to see if vpage would work for me. It did what I wanted except it has an all or nothing aspect to it. Ideally, vpage would let me keep my organizational structure (including the group headers) and only switch the tests to the rows. Or am I missing something? I read the man page and tried several different setups but couldn't make it work the way I'd hoped. Anyone else managed to get Xymon rendering to work this way? thanks =G=

2 2

log monitoring hostname matching trouble
by EDSchminke＠Hormel.com 08 Jan '16

08 Jan '16

Hello, I'm trying to get log monitoring to work on a new implementation of Xymon (v4.3.24) For whatever reason, my client doesn't seem to be receiving a logfetch.cfg file from the server after it checks in. I've tried a number of combinations of hostname and none of them seem to work: [lpcobwas2p] (hostname only) [lpcobwas2p.hfc.ad] (FQDN, periods) [lpcobwas2p,hfc,ad] (FQDN, commas) None of them seem to work. Any ideas? Server side: [root at lxcobxymonp server]# pwd /home/xymon/server [root at lxcobxymonp server]# hostname lxcobxymonp.hfc.ad [root at lxcobxymonp server]# [root at lxcobxymonp server]# tail -2 etc/client-local.cfg [lpcobwas2p] log:/var/log/messages:20480 [root at lxcobxymonp server]# [root at lxcobxymonp server]# grep lpcobwas2p etc/hosts.cfg 0.0.0.0 lpcobwas2p # CLIENT:lpcobwas2p.hfc.ad [root at lxcobxymonp server]# Client side: [root at lpcobwas2p client]# pwd /home/xymon/client [root at lpcobwas2p client]# hostname lpcobwas2p.hfc.ad [root at lpcobwas2p client]# [root at lpcobwas2p client]# head -2 tmp/msg.lpcobwas2p.hfc.ad.txt @@client#1|1|127.0.0.1|lpcobwas2p.hfc.ad|linux client lpcobwas2p,hfc,ad.linux linux [root at lpcobwas2p client]# Erik D. Schminke | Associate Systems Programmer Hormel Foods Corporation | One Hormel Way | Austin, MN 55912 Phone: (507) 434-6817 edschminke at hormel.com | www.hormelfoods.com

1 0

MAGMA XYMon Web GUI Admin Now Available!
by sanderson＠CORNETSER.com 07 Jan '16

07 Jan '16

Henrik and Fellow Xymoners, Just for you I have pushed off any real work for today just to get you all a first release of MAGMA the XYMon Web GUI Admin. MAGMA is an add-on web GUI for managing Host, Groups and Alarms on a XYmon 4.3 or newer system. You can find MAGMA at http://www.squidworks.net/magma/ There you will find the description, screen shots and features of MAGMA along with the link to download the source package. It requires MySQL and PHP5 and is very simple to install. All supporting information is included in the tarball. How does it work? --------------------------- It stores all alarm and host/group configs in the SQL database and rewrites the Host.cfg, Analysis.cfg and Alarms.cfg files causing the XYmon system to update its tests and pages based on the changes in these files. It will overwrite the files each time a host is added or edited making the process of updating automatic. To get the full benefit of MAGMA you should place all hosts in "central" mode, although this is not required, without it your management is somewhat restrictive (external test management only). In Central mode you get full management features for all tests. If you have any questions or need some help just send me a email @ sanderson @ squidworks.net Cubert 8-) Aka Shannon Anderson

9 10

Extraneous DNS queries from Xymon
by john.thurston＠alaska.gov 06 Jan '16

06 Jan '16

I have defined some hosts with fake host names: 0.0.0.0 foo.bar.foo # noconn They are defined so that clients may send messages to the Xymon server and have their status displayed. What I don't understand is why my Xymon server insists on performing name queries for foo.bar.foo. Even adding "testip" to the line doesn't eliminate all of the queries. The only way I can make them stop is by making bogus entries in my server's hosts file, of the form: 127.0.0.2 foo.bar.foo There are no xymonnet tests defined for this host. The server is not running xymond_alert or xymongen. What component is querying DNS, and why? -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska

3 4