September 2013 - Xymon - Xymon mailman web

File monitoring with `date` in filename
by schritte＠ub.uni-frankfurt.de 26 Sep '13

26 Sep '13

Hi Mark, thanks, but this doesn't work either. I assume the problem is that the backticks are evaluated, but the "$(date)" isn't as that is done by sh and sh doesn't know $(variable). So what we need is some thing like one backtick expansion after the other. or a way to let ksh do the job. But I don't know if there is way to achieve that. The workaround is ok for the moment. If the log is missing it wouldn't be very serious as we are checking for MTIME<600 (last access more then 10 minutes ago). So xymon will get red in case todays file is missing as it is older than that, kind regards Rolf > > Wonder if you need to preface the operation with an eval to get the > date command to operate first -- don't know if this will work with Xymon. > > FILE `eval find /home/mypath/log/update_out_$(date +%Y%m%d).txt` MTIME<red > > The other thing I would be a little leery of, is having any expression > calculation in the filepath variable in the find command -- some older > Unix flavors may get upset over this syntax. Calculations/regex tend > to be better supported with the --name attribute. Ditto with presumed > output versus need to use "-print " in older find commands. If you > don't need to support older Unix flavors, then ignore all of this. > > FILE `eval find /home/mypath/log --name "update_out_$(date > +%Y%m%d).txt" --print` MTIME<red > > Above would need more work though as by itself it will keep hunting > down the log directory tree for possibly other files. > > The thing I don't particular care for with `ls --tr > /home/mypath/log/update_put_*.txt| tail -1` is what happens if the > current day's file is missing? Then you are parsing yesterday's or the > last log file. No complaints if the wrong file is being operated on. > Would ~assume you want some kind of alert if the today's log file is > missing.... > > *From:*Xymon [mailto:xymon-bounces at xymon.com] *On Behalf Of *Rolf > Schrittenlocher > *Sent:* Thursday, September 26, 2013 7:44 AM > *To:* deepak deore > *Cc:* xymon > *Subject:* Re: [Xymon] File monitoring with `date` in filename > > Thanks Deepak, > > unfortunately that won't help as I need the file with the present date > in its name. I did now: > `ls -tr /home/mypath/log/update_out_*.txt|tail -1` > This workaround helped. But I'm still curious if there is a solution > for first expanding the date and second the whole expression > `find /home/mypath/log/update_out_$(date +%Y%m%d).txt` (sorry, I > dropped the find in my first posting) > > kind regards > Rolf > > > Looks like your analysis.cfg entry is wrong.Try this. > > FILE /home/mypath/log/update_out_[0-9]*-[0-9]*-[0-9]*\.txt > MTIME<600 red > > On Thu, Sep 26, 2013 at 1:04 PM, Rolf Schrittenlocher > <schritte at ub.uni-frankfurt.de <mailto:schritte at ub.uni-frankfurt.de>> > wrote: > > Dear xymon users, > > I got stuck while trying to monitor a file which should be updated > regularly and which has got a timestamp in its name. > "files" on the server remains clear, no data . Could someone tell me > what is wrong with these settings or what have i forgotten? > > On the server we have in > analysis.cfg > HOST=myserver > FILE `/home/mypath/log/update_out_$(date +%Y%m%d).txt` MTIME<600 red > > in client-local.cfg: > [myserver] > file:`find /mypath/log/update_out_$(date +%Y%m%d).txt` > > > I see an entry for this file on the client > in tmp logfetch.myserver.cfg > file:`find /mypath/log/update_out_$(date +%Y%m%d).txt` > > but there is nothing for this file in msg.myserver.txt > > File exists and is readable: > find /home/mypath/log/update_out_$(date +%Y%m%d).txt -exec ls -l {} \; > -rw-rw-r-- 1 ... 2467070 Sep 26 08:43 > /home/mypath/log/update_out_20130926.txt > > In xymonclient.log I see an entry > sh: syntax error at line 1: `(' unexpected > but I don't know if it is related to the file problem or to anything else. > I know that sh can't deal with $(xy), I tried as well > FILE /home/mypath/log/update_out_`date +%Y%m%d`.txt MTIME<600 red > but in vain. > > Any help appreciated, > kind regards > Rolf > > > -- > Mit freundlichen Gruessen > Rolf Schrittenlocher > > Lokales Bibliothekssystem Frankfurt > Senckenberganlage 31, 60054 Frankfurt > Tel: (49) 69 - 798 28908 Fax: (49) 69 798 28817 > LBS: lbs-f at mlist.uni-frankfurt.de <mailto:lbs-f at mlist.uni-frankfurt.de> > Persoenlich: schritte at ub.uni-frankfurt.de > <mailto:schritte at ub.uni-frankfurt.de> > > _______________________________________________ > Xymon mailing list > Xymon at xymon.com <mailto:Xymon at xymon.com> > http://lists.xymon.com/mailman/listinfo/xymon > > > > > -- > Mit freundlichen Gruessen > Rolf Schrittenlocher > > Lokales Bibliothekssystem Frankfurt > Senckenberganlage 31, 60054 Frankfurt > Tel: (49) 69 - 798 28908 Fax: (49) 69 798 28817 > LBS:lbs-f at mlist.uni-frankfurt.de <mailto:lbs-f at mlist.uni-frankfurt.de> > Persoenlich:schritte at ub.uni-frankfurt.de <mailto:schritte at ub.uni-frankfurt.de> -- Mit freundlichen Gruessen Rolf Schrittenlocher Lokales Bibliothekssystem Frankfurt Senckenberganlage 31, 60054 Frankfurt Tel: (49) 69 - 798 28908 Fax: (49) 69 798 28817 LBS: lbs-f at mlist.uni-frankfurt.de Persoenlich: schritte at ub.uni-frankfurt.de

1 0

copy compiled server code from dev to prod
by bakgat8＠hotmail.com 25 Sep '13

25 Sep '13

I compiled xymon-4.3.10 on a development server. Now I copied the "install" over to a production server. Here is what I see. if I do a findhost via http://prodserver/xymondev1-cgi/findhost.sh if the checkbox Jump to page is checked - it "jumps" to the development server. If I uncheck the box - it shows a link which works correctly. If there is a better/approved way to move the installed code ... let me know!

2 2

get more log lines in xymn msgs
by vaida.dan＠gmail.com 25 Sep '13

25 Sep '13

Hi Mike, Thanks for being so fast. I actually increased that value to 30k as oposed to the default one of 10240. Still, didn't help :( Sent from my iPhone On Sep 18, 2013, at 5:18 PM, "Mike Burger" <mburger at bubbanfriends.org> wrote: > You'll want to adjust the log: line for the log in question. The numeric > value at the end specifies the number of bytes to monitor at a shot. If > the lines in your log file are particularly long, the number of bytes > being monitored/displayed may be cutting you off at that 35 line number. > > Increasing that number should increase the number of lines you see. > -- > Mike Burger > http://www.bubbanfriends.org > > "It's always suicide-mission this, save-the-planet that. No one ever just > stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1 > > On Sunday, September 8, I'll be participating in the Spokes of Hope ride, > to raise money for cancer awareness and make a difference in the lives of > cancer victims and their families/friends. If you'd care to donate, please > click: > > http://ow.ly/nIdrC > > Thank you. > > >> by default, this looks like it is set to 35 lines. >> >> my question is: how can I have more log entries showing up in the web >> interface for a custom log that I've started to monitor ? >> >> thank you ! >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com >> http://lists.xymon.com/mailman/listinfo/xymon >> >

1 1

calculation of memory and swap
by schritte＠ub.uni-frankfurt.de 25 Sep '13

25 Sep '13

Hi all, we are using solaris zones. I know, memory and swap is a bit triggy on zones, but I have a case where I think data is correct but the interpretation made by xymon (4.3.7) is wrong. The zone is restricted up to 17 Gb swap and 8.5 Gb memory. This is was the client collects [memory] 0 0 0 4430008 9320720 4403 39524 0 0 0 0 0 0 0 0 0 4752 113338 6142 1 3 96 [swap] total: 1745856k bytes allocated + 10589520k reserved = 12335376k used, 4441840k available [swaplist] swapfile dev swaplo blocks free /dev/swap 4294967295,4294967295 16 4194288 702832 This is what xymon is presenting as result after interpretation: Physical -971M 8192M -11% Swap 1646M 2047M 80% My idea is that values larger than 10 Gb are calculated the wrong way (because all zones using total memory less than 10 Gb are presented correctly). But I cannot find the place to fix this. Any ideas or hints? Thanks, Rolf -- Mit freundlichen Gruessen Rolf Schrittenlocher Lokales Bibliothekssystem Frankfurt Senckenberganlage 31, 60054 Frankfurt Tel: (49) 69 - 798 28908 Fax: (49) 69 798 28817 LBS: lbs-f at mlist.uni-frankfurt.de Persoenlich: schritte at ub.uni-frankfurt.de

3 4

xymon-client startup script issue (and fix)
by bakgat8＠hotmail.com 25 Sep '13

25 Sep '13

I am documenting this for whomever else may need this. This file is from an rpm xymon-client-4.3.10-1 that I got off the net somewhere. I just figured out why the "stop" does not work. I set CLIENTHOSTNAME in here => more /etc/default/xymon-client # Configure the Xymon client settings. # You MUST set the list of Xymon servers that this # client reports to. # It is good to use IP-adresses here instead of DNS # names - DNS might not work if there's a problem. # # E.g. (a single Xymon server) # XYMONSERVERS="192.168.1.1" # or (multiple servers) # XYMONSERVERS="10.0.0.1 192.168.1.1" XYMONSERVERS="10.65.1.66 10.65.20.151" # The defaults usually suffice for the rest of this file, # but you can tweak the hostname that the client reports # data with. # Thu Mar 21 15:30:16 EDT 2013 CLIENTHOSTNAME="$(hostname | cut -f1 -d'.')" # Red Hat EL version 3 uses a different vmstat layout # than all other Linux versions. So for a client running this # particular OS, set CLIENTOS as below. # Do NOT set this on any other Red Hat version. # CLIENTOS="rhel3" but the script does not pass that info on the stop - so the start worked fine, but the stop not. Even the restart worked. I fixed below # # xymon-client This shell script takes care of starting and stopping # the Xymon client. # # chkconfig: 2345 80 20 # description: Xymon is a network monitoring tool that allows \ # you to monitor hosts and services. This client reports local \ # system statistics (cpu-, memory-, disk-utilisation etc) \ # to the Xymon server. PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin DAEMON=/usr/lib/xymon/client/runclient.sh NAME=xymon-client DESC=xymon-client test -x $DAEMON || exit 0 CMD="$1" # Include xymon-client defaults if available DMNOPTS="" if [ -f /etc/default/xymon-client ] ; then . /etc/default/xymon-client else echo "Installation failure - missing /etc/default/xymon-client" exit 1 fi if [ "$XYMONSERVERS" = "" ]; then echo "Please configure XYMONSERVERS in /etc/default/xymon-client" exit 1 fi set $XYMONSERVERS if [ $# -eq 1 ]; then echo "XYMSRV=\"$XYMONSERVERS\"" >/var/run/xymonclient-runtime.cfg echo "XYMSERVERS=\"\"" >>/var/run/xymonclient-runtime.cfg else echo "XYMSRV=\"0.0.0.0\"" >/var/run/xymonclient-runtime.cfg echo "XYMSERVERS=\"$XYMONSERVERS\"" >>/var/run/xymonclient-runtime.cfg fi if [ "$CLIENTHOSTNAME" != "" ]; then DMNOPTS="${DMNOPTS} --hostname=${CLIENTHOSTNAME}" fi if [ "$CLIENTOS" != "" ]; then DMNOPTS="${DMNOPTS} --os=${CLIENTOS}" fi set -e case "$CMD" in start) echo -n "Starting $DESC: " su -c "$DAEMON $DMNOPTS start" - xymon echo "$NAME." ;; stop) echo -n "Stopping $DESC: " su -c "$DAEMON stop" - xymon ### is ## su -c "$DAEMON $DMNOPTS stop" - xymon # ## should be this!!! echo "$NAME." ;; restart) echo -n "Restarting $DESC: " su -c "$DAEMON stop" - xymon su -c "$DAEMON $DMNOPTS start" - xymon echo "$NAME." ;; *) N=/etc/init.d/$NAME # echo "Usage: $N {start|stop|restart}" >&2 echo "Usage: $N {start|stop|restart}" >&2 exit 1 ;; esac exit 0

2 2

logfetch unreliable?
by bakgat8＠hotmail.com 24 Sep '13

24 Sep '13

Yes, yes I have all that. But fair point. It did not show up in nemo - msgs from history: Date Status Duration Mon Sep 23 17:55:51 2013 yellow 0:10:03 Tue Aug 13 13:56:01 2013 green 41 days 3:59:50 The entry I wanted (see below) was at about 17:05 and as you can see above msgs was happily green. The yellow was me adding the fake file entry - without adding the file yet. So it threw a legit error. If cut a chunk of the file and cat it into the fake file - it alerts perfectly. So I believe my alert setup is good. And msgs does turns red - just to be specific. 451 Transfer aborted due to file error. File is catalogued. 221 Quit command received. Goodbye. /usr/local/bin/rmsupload.sh[27694]: Fatal error: RMS Report upload for rmsfile43 failed. File Transfer Failed. Notify Mainframe On-Call. (rmsupload.sh) Mon Sep 23 17:05:58 EDT 2013 /usr/local/bin/rmsupload.sh[28432]: Arguments: 32 181 /ftpstage/rms/HEERDTS.10094575_MAINFRAME_ASCII.txt.tmp Mon Sep 23 17:05:58 EDT 2013 /usr/local/bin/rmsupload.sh[28432]: converting /ftpstage/rms/HEERDTS.10094575_MAINFRAME_ASCII.txt.tmp to /ftpstage/rms/rmsupload28432.t > Date: Tue, 24 Sep 2013 09:46:25 -0400 > Subject: Re: [Xymon] logfetch unreliable? > From: mburger at bubbanfriends.org > To: bakgat8 at hotmail.com > > Per the man page for client-local.cfg > (http://http://www.xymon.com/xymon/help/manpages/man5/client-local.cfg.5.html: > > "The trigger PATTERN line (optional) is used only when there is more data > in the log than the maximum size set in the "log:FILENAME:SIZE" line. The > "trigger" pattern is then used to find particularly interesting lines in > the logfile - these will always be sent to the Xymon server. After picking > out the "trigger" lines, any remaining space up to the maximum size is > filled in with the most recent entries from the logfile. "PATTERN" is a > regular expression." > > I don't see anything where it's supposed to do anything more than send > those entries to the "msgs" area in Xymon. > > You'd have to actually put together something that causes that pattern to > generate a status (yellow, red) and then something in the alerts.cfg to > actually send out an alert, if so desired. > > -- > Mike Burger > http://www.bubbanfriends.org > > "It's always suicide-mission this, save-the-planet that. No one ever just > stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1 > > On Sunday, September 8, I'll be participating in the Spokes of Hope ride, > to raise money for cancer awareness and make a difference in the lives of > cancer victims and their families/friends. If you'd care to donate, please > click: > > http://ow.ly/nIdrC > > Thank you. > > > > > > > > > > I am in the throws of replacing a commercial monitoring product with > > xymon. (Before this product we ran big brother. ) > > > > But I am in a pickle. The commercial product picked up a log entry last > > night, that xymon did not. I know this because both products are alerting > > currently. My biggest issue is the non-report is not reproducible. If I > > send test messages into my fake log, it works - but I have proof it failed > > last night in the real log file. How do I even go about debugging this? > > > > My client-local.cfg has > > > > [nemo] > > log:/var/log/fake.log:1024 > > trigger "Notify Mainframe On-Call." > > log:/var/log/rmsupload.log:1024 > > trigger "Notify Mainframe On-Call." > > > > > > G > > > > _______________________________________________ > > Xymon mailing list > > Xymon at xymon.com > > http://lists.xymon.com/mailman/listinfo/xymon > > >

2 3

logfetch unreliable?
by bakgat8＠hotmail.com 24 Sep '13

24 Sep '13

I am in the throws of replacing a commercial monitoring product with xymon. (Before this product we ran big brother. ) But I am in a pickle. The commercial product picked up a log entry last night, that xymon did not. I know this because both products are alerting currently. My biggest issue is the non-report is not reproducible. If I send test messages into my fake log, it works - but I have proof it failed last night in the real log file. How do I even go about debugging this? My client-local.cfg has [nemo] log:/var/log/fake.log:1024 trigger "Notify Mainframe On-Call." log:/var/log/rmsupload.log:1024 trigger "Notify Mainframe On-Call." G

2 1

Missing custom trends graph
by jlaidman＠rebel-it.com.au 23 Sep '13

23 Sep '13

Hiya I have a custom graph on the trends page, essentially a duplicate of the [bind] graph but with a few more record types (eg AAAA, CNAME). The extended graph displays correctly if I bring up the "bind" graph in my browser and change the URL so "bind" becomes "bind-extended". Or, if I adjust the graphs.cfg config so that [bind-extended] becomes [bind], then the trends page shows my new graph format instead (because it comes after the default [bind] in graphs.cfg). So I know the graph works just fine. What I want is for both graphs to display on the trends page, not just the [bind] graph. So I've adjusted the TRENDS setting in hosts.cfg, for the relevant hosts, to include "bind:bind|bind-extended". Like so: 10.1.1.1 dns1 # testip noping TRENDS:*,bindstats:bindstats|bindstats1,bind:bind|bind-extended Of course "bind" is defined in GRAPHS (xymonserver.cfg) as per default, so that Xymon knows to show it on the trends page - and it does. However, I expected that the TRENDS setting would cause "bind-extended" to also be shown on the trends page. But it isn't. Perplexingly (if that's a word) the "bindstats" graph does the right thing. I have bindstats RRD files, I have bindstats included in GRAPHS, I have both [bindstats] and [bindstats1] graph definitions, and I have "bindstats:bindstats|bindstats1" set in TRENDS for the relevant hosts. On the trends graph, I'm shown the graphs for [bindstats] and [bindstats1]. I can't see how my treatment of bindstats and bind are different, yet one works as per the doco, and the other doesn't. Any suggestions what I might be doing wrong, or where to look? Cheers Jeremy

1 1

host doesn't report http
by troy＠athabascau.ca 20 Sep '13

20 Sep '13

I have two hosts : XXX.XXX.XXX.XXX www # trace http://www XXX.XXX.XXX.XXX www2 # trace http://www ...and only one of them is reporting http. The only difference is the name "www2". The IPs and configs are the same. I have looked everywhere I can think and was hoping for ideas. / Troy -- This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. ---

4 4

Asis error on NetApp filer with the netapp.pl plugin
by linuxmasterjedi＠free.fr 20 Sep '13

20 Sep '13

Hi, The netapp.pl plugin works fine here, except when I enable the compression on one our filers. Now, I have this error : red Error in last ASIS operation on vol /vol/foo_vol1: Fri Sep 20 00:00:00 CEST 2013 red Error in last ASIS operation on vol 4383 gb/49 tb (9%): 1 yellow ASIS on Volume 4383 gb/49 tb (9%) is Disabled red Error in last ASIS operation on vol 8112 mb: Idle for 117:56:43 yellow ASIS on Volume 8112 mb is Disabled red Error in last ASIS operation on vol sun sep 15 12:03:52 cest 2013: yellow ASIS on Volume sun sep 15 12:03:52 cest 2013 is Disabled There are a couple of information in the script, but I don't think it could help : # asisshowrule = [yes|no] default yes # Show asis rule near the warning/alert reported # asisfullreport = [yes|no] default yes # Show the full output of asis status -v at the end of the reported data # asislegend = [yes|no] default yes # Show the full legend of rules used for warning/alert at the end of the reported data # asischeck = [rule1];[rule2];...;[rulen] # With this options it's possible to define multiple rule for the asis check of filers. The rule # is similar to the one used for snaplistcheck and snapmirrorcheck but only the lag time is used. # A rule is composed by 3 parameters separated by ":". # rule=path:lagwarn:lagalert # path = a string rappresenting the volume on which you want to do the check (the full path) # lagwarn/lagalert = Check for the lag of the deduplication of the volume # When using age you can use ">" (default) or "<" in front of a number followed by # "d" for day, "h" for hours and "m" for minutes. Some examples are: >10h 10d <10m Any feedback around this ? Thanks !

1 0