Make sure you understand the underlying design of distributed nagios setup. <br>Obssessive-Compulsive (ocsp) command need to be correctly configurated on nagios slave. <br><br><div class="gmail_quote">2010/5/14 Sérgio Afonso <span dir="ltr"><<a href="mailto:sergioafonsojr@gmail.com">sergioafonsojr@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hello Marcel,<br>
<br>
My nagios version is 3.2.0. About my command_check_interval I<br>
couldn't understand very well what you mean. My command_check_interval<br>
is set to -1<br>
<br>
Rgs,<br>
<font color="#888888"><br>
Sérgio.<br>
</font><div><div></div><div class="h5"><br>
On Fri, May 14, 2010 at 1:50 PM, Marcel <<a href="mailto:mitsuto@gmail.com">mitsuto@gmail.com</a>> wrote:<br>
> With only 150 services, it should not delay that much nor stops execution of<br>
> the main process.<br>
> Please check you main nagios.cfg file and look for command_check_interval,<br>
> if the value attributed to that variable isn't "-1" then there is your<br>
> problem.<br>
><br>
> Also, which nagios version are you running?<br>
><br>
><br>
> On Fri, May 14, 2010 at 2:28 PM, Trisha Hoang <<a href="mailto:trisha@rockyou.com">trisha@rockyou.com</a>> wrote:<br>
>><br>
>> Hi Sergio,<br>
>> Some of the directives I found helpful for our MASTER server are listed<br>
>> below.<br>
>><br>
>> Since status.dat and nagios.cmd are disk bound, put them on ramdisk will<br>
>> be faster.<br>
>> status_file=/mnt/ramdisk/status.dat<br>
>> command_file=/mnt/ramdisk/nagios.cmd<br>
>><br>
>> I don't think aggressive_host_checking is needed as nagios checks for host<br>
>> when a service is in error anyway.<br>
>> use_aggressive_host_checking=0<br>
>> check_host_freshness=0<br>
>><br>
>> Service freshness is important as the MASTER tends to process passive<br>
>> checks much slower so the services may go stale. However, since our checks<br>
>> are 5 min interval, having the MASTER wait for the next round of check is<br>
>> fine.<br>
>> check_service_freshness=1<br>
>> service_freshness_check_interval=420<br>
>><br>
>> We use nagios-3.2.1 and I think these directives are still experimental<br>
>> but they seem to help. You will see defunct nagios processes that come and<br>
>> go. I think it's caused by child forked once instead of twice so one gets<br>
>> killed (my theory), but again, it seems to be running ok.<br>
>> use_large_installation_tweaks=0<br>
>> child_processes_fork_twice=0<br>
>><br>
>> Our MASTER receives ~7000 passive checks from the SLAVE but it could only<br>
>> process max ~5000 passive checks per 5 min. The latency is about <10 secs.<br>
>> For the rest, the MASTER actively checks them. If you or someone knows a way<br>
>> to improve passive check processing, that will be great.<br>
>><br>
>> Also, in our setup, we don't use NSCA. The slaves have<br>
>> ocsp_command=send_service_check where this command inserts the checks into a<br>
>> file that gets sent every 5 sec to the master. On the master, there's a<br>
>> script that opens this file and inserts the lines directly into the<br>
>> nagios.cmd pipe every 5 sec.<br>
>><br>
>> Trisha<br>
>><br>
>><br>
>><br>
>> ------------------------------------------------------------------------------<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Nagios-users mailing list<br>
>> <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br>
>> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>
>> ::: Please include Nagios version, plugin version (-v) and OS when<br>
>> reporting any issue.<br>
>> ::: Messages without supporting info will risk being sent to /dev/null<br>
><br>
><br>
> ------------------------------------------------------------------------------<br>
><br>
><br>
> _______________________________________________<br>
> Nagios-users mailing list<br>
> <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br>
> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>
> ::: Please include Nagios version, plugin version (-v) and OS when reporting<br>
> any issue.<br>
> ::: Messages without supporting info will risk being sent to /dev/null<br>
><br>
<br>
------------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Nagios-users mailing list<br>
<a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br>
::: Messages without supporting info will risk being sent to /dev/null<br>
</div></div></blockquote></div><br>