Scheduling queue

[Steve Meyers]

On Tue, 2004-03-09 at 11:02, Steve Meyers wrote:
> I figured out the problem, I think.  Somehow my check_service_freshness
> got enabled, and turning that off seems to have fixed the problem.  I
> don't know why, and it doesn't make sense to me, but as long as it works
> I'm happy. :)

Okay, I lied.  It worked for a little bit, now it's screwed up again. 
Here is the info from my "Performance Info" page:

==============================================
ACTIVE CHECKS

Time Frame            Checks Completed 
<= 1 minute:          22 (22.9%)
<= 5 minutes:         73 (76.0%)
<= 15 minutes:        75 (78.1%)
<= 1 hour:            91 (94.8%)
Since program start:  52 (54.2%)

Metric                Min.     Max.     Average 
Check Execution Time: < 1 sec  1 sec    0.021 sec 
Check Latency:        < 1 sec  1 sec    0.021 sec 
Percent State Change: 0.00%    0.00%    0.00%


PASSIVE CHECKS

Time Frame            Checks Completed 
<= 1 minute:          0 (0.0%)
<= 5 minutes:         13 (81.2%)
<= 15 minutes:        16 (100.0%)
<= 1 hour:            16 (100.0%)
Since program start:  13 (81.2%)

Metric                Min.     Max.     Average 
Percent State Change: 0.00%    0.00%    0.00%
==============================================

The load on the server is 0.02, 0.04, 0.00.

My service_reaper_frequency is 10, and my max_concurrent_checks is 0. 
What other info can I provide?

Thanks!

Steve Meyers



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
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