too many lines in archive log

[Andreas Ericsson]

On 12/12/2011 10:35 AM, Marco Borsani wrote:
> Hi all
> 
> Probably I made some errors in the passive checks configuration ..
> 
> The main Nagios server has 132 passive hosts and 400 passive services
> configured (only 30 active hosts and 60 active services), received from two
> remote Nagios systems.
> 
> 
> 
> In each archive file I have more than 420.000 lines (compared to another
> Nagios server with about 20.000, with no passive checks configured).
> 
> 
> 
> I see many and many rows like :
> 
> [1323564139] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT; …
> 
> [1323564139] EXTERNAL COMMAND: PROCESS_HOST_CHECK_RESULT; …
> 
> ………….
> 
> And
> 
> [1323564137] PASSIVE HOST CHECK: …
> 
> [1323564137] PASSIVE SERVICE CHECK: …
> 
> 
> 
> Is it normal ?
> 

Yes.

> What can I check/modify to reduce the logs ?
> 

Set log_external_commands=0 in your nagios.cfg file. That should cut
your logs in half, roughly. You could also send in the passive checks
less frequently.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

------------------------------------------------------------------------------
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure
_______________________________________________
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