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