Page 1 of 1

LOG CHECK SENDING ALERTS OF OLD TIMESTAMP

Posted: Fri Jul 21, 2017 12:10 pm
by ericssonvietnam
I am using check logfile check in order to generate alert for the critical pattern form the log file in past few days i have received the alert in Nagios with old time stamp.
Can you let me know what should i check attaching the alert generated on the Nagios.

Below is the configuration to generate critical pattern :

SSH:nagios@HNUSS2# cat AuthCri.conf
$seekfilesdir = '/export/home/nagios/logfile_basedir/tmp';
$protocolsdir = '/export/home/nagios/logfile_basedir/tmp';
$scriptpath = '/export/home/nagios/bin';
#$MACROS = { CL_DISK01 => "/dev/dsk/c0d1", CL_DISK02 => "/dev/dsk/c0d2" };

@searches = (
{
tag => 'Authcri',
warningpatterns => ['auth.crit] rebooted by'] ,
#okpatterns => ['ALARM_CLR'] ,
options => 'sticky=1800,noprotocol,report=long,allyoucaneat',
logfile => '/var/log/authlog'

}
);

Re: LOG CHECK SENDING ALERTS OF OLD TIMESTAMP

Posted: Fri Jul 21, 2017 1:36 pm
by ssax
That is likely because of your sticky=1800 option:

Code: Select all

--sticky[=<lifetime>] Errors are propagated through successive runs.
Try removing that and see if it resolves the issue.


Thank you

Re: LOG CHECK SENDING ALERTS OF OLD TIMESTAMP

Posted: Fri Jul 21, 2017 3:36 pm
by ericssonvietnam
ssax wrote:That is likely because of your sticky=1800 option:

Code: Select all

--sticky[=<lifetime>] Errors are propagated through successive runs.
Try removing that and see if it resolves the issue.


Thank you
Should i comment out whole options line in the configuration.
As shown below :
#options => 'sticky=1800,noprotocol,report=long,allyoucaneat',

Re: LOG CHECK SENDING ALERTS OF OLD TIMESTAMP

Posted: Sun Jul 23, 2017 10:57 pm
by tacolover101
it's hard to say if a comment will do, so test by removing it fully. (it should though.)

Re: LOG CHECK SENDING ALERTS OF OLD TIMESTAMP

Posted: Mon Jul 24, 2017 10:11 am
by ssax
That should be fine, give it a try and let us know if that resolves your issue.

Thank you