[Nagios-devel] Re: how long does a check_tcp s ervice check take?

Bishop, Dean dean.bishop at tcdsb.org
Thu Oct 24 16:09:31 CEST 2002


sure.  i have two normal_check_interval values.  Once for switches'
check_tcp!23 and check_nt(20minutes) and one for servers' check_tcp!135 (5
minutes).

i had the everything set for 20 minutes but i really need the information
faster.  i changed it just to see what would happen and i am seeing no
increase in time.

This just doesn't make sense to me.  i went from 1400 services at a 20
minute interval to 1200 services at 20 minutes and 200 services at a 5
minute interval and they all seem to be getting done within 20 minutes.  My
math says that effectively i have 1400+200*4=2200 services being checked in
a 20 minute window.

hmmm.  Is Nagios adjusting speed to balance the load?

i ran 'nagios -s' to get an idea of what my interval should be and it said
17 minutes.  i realize that this is meant as a reference only but...<shrug>.

by the way, even though i have added 250 check_nt services (at 20 minute
intervals) my 'nagios -s' provides the same value.  <shrug>

anyway, here is my snippet


thanks,
dean



# Generic service definition template

	define service{							
		name					generic-service

		active_checks_enabled		1	
		check_freshness			0	
		check_period			24x7	
		event_handler_enabled		1	
		flap_detection_enabled		1	
		is_volatile				0	
		max_check_attempts		2	
		normal_check_interval		20			
		notification_interval		60	
		notification_options		u,c,r	
		notification_period		24x7	
		notifications_enabled		1	
		obsess_over_service		0			
		parallelize_check			1	
		passive_checks_enabled		1	
		process_perf_data			1		
		retain_nonstatus_information	1
		retain_status_information	1
		retry_check_interval		2	
		register				0	
		}				


# Service definition for a basic Server				
define service {				
	name				Port-Check-135
	use				generic-service
	service_description	Port Check-135
	normal_check_interval	5
	check_command		check_tcp!135
	register			0
	}			
				
# Service definition for a basic Switch				
define service {				
	name				Port-Check-23
	use				generic-service
	service_description	Port Check-23
	check_command		check_tcp!23
	register			0
	}			


-----Original Message-----
From: Mike McClure [mailto:mmcclure at pneservices.com]
Sent: Thursday, October 24, 2002 10:09 AM
To: nagios-users at lists.sourceforge.net;
nagios-devel at lists.sourceforge.net
Subject: [Nagios-devel] Re: [Nagios-users] how long does a check_tcp
service check take?


Dean,

What are the "normal_check_interval" settings on your services?  Can you
post a
portion of your services.cfg file?

Mike

> Good morning,
>
> 	i am in the process of trying to squeeze as much out of my box as
> possible and have some problems understanding what is happening.
>
> 	i started out on a P-II 350 with 384M RAM.  i added about 1400
> services most of which are check_tcp checks.  These checks report that the
> response came in 0 seconds.  i know that this isn't a true reading but it
at
> least tells me that it took less than 1 second.
>
> 	It actually takes about 17 minutes to complete these checks.  Doing
> the math 1400/(17*50) it is taking about 3/4 seconds per check.
>
> 	i moved this installation (physically moved the hdd) to a P-4 800
> (Non-Celeron).  i was hoping for an improvement.  i didn't see one.  It
> still takes 17 minutes.
>
>
> 	Is there any way of speeding this up or am i now at the mercy of the
> network?
>
> 	What would happen if i add another NIC?  Would the load be balanced?
>
> 	i have diddled with varios settings in my nagios.cfg but nothing
> seems to help.
>
> thanks in advance,
> dean
>
>
> nagios.cfg
> ----------
> log_file=/usr/local/nagios/var/nagios.log
> cfg_file=/usr/local/nagios/etc/checkcommands.cfg
> cfg_file=/usr/local/nagios/etc/misccommands.cfg
> cfg_file=/usr/local/nagios/etc/contactgroups.cfg
> cfg_file=/usr/local/nagios/etc/contacts.cfg
> cfg_file=/usr/local/nagios/etc/dependencies.cfg
> cfg_file=/usr/local/nagios/etc/escalations.cfg
> cfg_file=/usr/local/nagios/etc/hostgroups.cfg
> cfg_file=/usr/local/nagios/etc/hosts.cfg
> cfg_file=/usr/local/nagios/etc/services.cfg
> cfg_file=/usr/local/nagios/etc/timeperiods.cfg
> resource_file=/usr/local/nagios/etc/resource.cfg
> status_file=/usr/local/nagios/var/status.log
> nagios_user=nagios
> nagios_group=nagios
> check_external_commands=1
> command_check_interval=-1
> command_file=/usr/local/nagios/var/rw/nagios.cmd
> comment_file=/usr/local/nagios/var/comment.log
> downtime_file=/usr/local/nagios/var/downtime.log
> lock_file=/usr/local/nagios/var/nagios.lock
> temp_file=/usr/local/nagios/var/nagios.tmp
> log_rotation_method=d
> log_archive_path=/usr/local/nagios/var/archives
> use_syslog=0
> log_notifications=1
> log_service_retries=1
> log_host_retries=1
> log_event_handlers=1
> log_initial_states=1
> log_external_commands=1
> log_passive_service_checks=1
> #global_host_event_handler=somecommand
> #global_service_event_handler=somecommand
> inter_check_delay_method=s
> service_interleave_factor=s
> max_concurrent_checks=0
> service_reaper_frequency=2
> sleep_time=1
> service_check_timeout=60
> host_check_timeout=30
> event_handler_timeout=30
> notification_timeout=30
> ocsp_timeout=5
> perfdata_timeout=5
> retain_state_information=1
> state_retention_file=/usr/local/nagios/var/status.sav
> retention_update_interval=60
> use_retained_program_state=1
> interval_length=60
> use_agressive_host_checking=0
> execute_service_checks=1
> accept_passive_service_checks=1
> enable_notifications=1
> enable_event_handlers=1
> process_performance_data=1
> host_perfdata_command=process-host-perfdata
> service_perfdata_command=process-service-perfdata
> obsess_over_services=0
> #ocsp_command=somecommand
> check_for_orphaned_services=0
> check_service_freshness=1
> freshness_check_interval=60
> aggregate_status_updates=1
> status_update_interval=15
> enable_flap_detection=0
> low_service_flap_threshold=5.0
> high_service_flap_threshold=20.0
> low_host_flap_threshold=5.0
> high_host_flap_threshold=20.0
> date_format=euro
> admin_email=nagios
> admin_pager=pagenagios
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
>
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
>
>


-- 
Mike McClure, CCIE # 5125, CISSP # 30232
PNE Services, Inc. -  http://www.pneservices.com
mmcclure at pneservices.com
mobile: 913-636-5590





-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote
_______________________________________________
Nagios-devel mailing list
Nagios-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-devel


-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote




More information about the Users mailing list