CPU Load and scheduling queue

[louafi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>-----Message d'origine-----
>De : nagios-users-admin at lists.sourceforge.net
>[mailto:nagios-users-admin at lists.sourceforge.net] >De la part de
>Subhendu Ghosh Envoyé : mardi 3 juin 2003 18:10
>À : nagios-users at lists.sourceforge.net
>Objet : Re: [Nagios-users] CPU Load and scheduling queue
>
>
>On Tue, 3 Jun 2003, louafi wrote:
>
>>  
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> Hi,
>> 
>> I have a problem with my nagios.
>> 
>> I have 1800 services on 130 hosts.
>> 
>> All my services have the same configuration :
>> 
>> define service{
>>         host_name 42.42.42.42
>>         service_description CPU:CPU_1
>>         check_command 
>> check_unix_cpu!500!0!1000!0!.1.3.6.1.4.1.2021.10.1.3.1!public
>>         max_check_attempts 4
>>         normal_check_interval 5
>>         retry_check_interval 5
>>         active_checks_enabled 1
>>         passive_checks_enabled 0
>>         check_period 24x7
>>         parallelize_check 1
>>         check_freshness 0
>>         flap_detection_enabled 0
>>         process_perf_data 1
>>         retain_status_information 1
>>         retain_nonstatus_information 1
>>         notification_interval 60
>>         notification_period 24X7
>>         notification_options w,c,r
>>         notifications_enabled 0
>>         stalking_options o,w,u,c
>> }
>> 
>> My nagios.cfg is :
>> 
><snip>
>
>> inter_check_delay_method=s
>> service_interleave_factor=s
>> max_concurrent_checks=10000
>> service_reaper_frequency=10
>> sleep_time=1
><snip>
>
>> 
>> My perfdata function enter the check result in RRD and in a mysql 
>> database to generate statistics.
>> 
>> Nagios schedules the check, but the check are not executed at the 
>> scheduling time. For example a sheduled check at 9:42 is executed
>> at  9:55... My average CPU load is not high (load average: 2.27,
>> 1.41,  1.18).
>> 
>> My computer is a bi P3 1,26GHz
>> 
>> I have tried inter_check_delay_method=0.01 without best result.
>> The  schedule is different (more aggressive) but the check are
>> late.
>> 
>> Any ideas ? Thanks a lot.
>> 
>
>You are using a "smart" check interleave factor. That allows to
>Nagios to  schedule the time of the actual check within a time
>boundary.  It will not  be the same interval every time, but close.
>
>Look at the docs for check interleave factor if you want precise
>control.  
>
>-- 
>-sg

Thanks for your reply.
I disagree with you or i don't understand the link between my problem
and th check interleave factor.

I don't have a problem with the scheduling, the check interleave
factor only affect scheduling and not scheduling execution.

All my scheduling checks are not executed at the time indicated in
the Scheduling Queue. Nagios execute this queue with 5-8 minutes of
late.

Thanks

>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: eBay
>Get office equipment for less on eBay!
>http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
>_______________________________________________
>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  
>
>

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPt2z1OL+f7HHv3GYEQKlCgCgzjsS6AJgcE5Txk4qhvsEHSraL/oAnAl+
C5xkMqPftf8B1qAXc9whfpOF
=DWbX
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
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