check_logfiles

C. Bensend benny at bennyvision.com
Mon Jul 9 04:18:00 CEST 2012


>  Here's the run of the command I am trying
>
>  [db:~] root% /opt/nagios/libexec/check_logfiles
> --logfile=/u01/app/oracle/admin/ecom/bdump/alert_ecom1.log --tag=oracle
> --rotation=linux --criticalpattern='ORA-00600' --warningpattern='ORA-*'
> OK - no errors or warnings|oracle_lines=0 oracle_warnings=0
> oracle_criticals=0 oracle_unknowns=0
>
>
>  This is what is in that logfile -
>
> [db07:~] root% grep 'ORA-00600'
> /u01/app/oracle/admin/ecom/bdump/alert_ecom1.log
> ORA-00600 - This is only a test.. please disregard

Try using the allyoucaneat option to test on the command line...
IIRC, check_logfiles will only check a reasonable number of lines in
the log file the first time, and from that point on only new ones.  If
that ORA-00600 is a long ways back, check_logfiles may not grok it.
The allyoucaneat option should force the plugin to check *all* lines
in the file.

Benny


-- 
"Death rays, advanced technology or not, no creature wants to be
stabbed in their hoo-hoo."        -- Seen on zombiehunters.org


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list