service check intervall

[Matthias Kurzer]

Moser Wolfgang wrote:
> Try to enable following in the nagios.cfg.
> 
> ###################
> # ORPHANED SERVICE CHECK OPTION
> # This determines whether or not Nagios will periodically
> # check for orphaned services.  Since service checks are not
> # rescheduled until the results of their previous execution
> # instance are processed, there exists a possibility that some
> # checks may never get rescheduled.  This seems to be a rare
> # problem and should not happen under normal circumstances.
> # If you have problems with service checks never getting
> # rescheduled, you might want to try enabling this option.
> # Values: 1 = enable checks, 0 = disable checks
> 
> check_for_orphaned_services=1
> ###################
> 
> The explanation is in the sample-nagios.cfg.
> I did a simple cut and paste.
> 
> I hope this help you!!

Sorry, but it did not solve my problem. But I get a new one. With this 
option enabled I get the message:

Wed Mar 12 17:08:09 2003  Warning: The check of service 'SSH' on host 
'quiz' looks like it was orphaned (results never came back).  I'm 
scheduling an immediate check of the service...

and after a few minutes I have hundreds of nagios processes, no more 
memory and a high CPU-Utilisation. Even if I set

max_concurrent_checks=50

But I did not find a way to log every check nagios is made. In my 
logfile is only the line

Sun Mar 23 11:04:23 2003  Auto-save of retention data completed 
successfully.

and of course alerts.

Maybe I can see then something in the logs.
-- 
Matthias Kurzer/IT Systemadministrator
c: Channel Business Service GmbH
Tel.: +49 40 76629-1966
Mail: kurzer at c-bs.de




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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