Here is an example of a Host. I have ~40-50 of these one after another in the minimal.cfg file.<br><br>define host{<br> use nn-ping ; Name of host template to use<br> host_name Ryan Whalen
<br> alias Ryan Whalen<br> address <a href="http://192.168.1.15">192.168.1.15</a><br> check_command check-host-alive<br> max_check_attempts 10<br>
notification_interval 120<br> notification_period 24x7<br> notification_options d,r<br> contact_groups admins<br> }<br><br>Here is the service template:<br><br>define service{
<br> name nn-service ; The 'name' of this service template<br> active_checks_enabled 1 ; Active service checks are enabled<br> passive_checks_enabled 1 ; Passive service checks are enabled/accepted
<br> parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead t<br> obsess_over_service 1 ; We should obsess over this service (if necessary)
<br> check_freshness 0 ; Default is to NOT check service 'freshness'<br> notifications_enabled 1 ; Service notifications are enabled<br> event_handler_enabled 1 ; Service event handler is enabled
<br> flap_detection_enabled 1 ; Flap detection is enabled<br> failure_prediction_enabled 1 ; Failure prediction is enabled<br> process_perf_data 1 ; Process performance data
<br> retain_status_information 1 ; Retain status information across program restarts<br> retain_nonstatus_information 1 ; Retain non-status information across program restarts<br> register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE
<br> }<br><br>Here is the actual service:<br><br>define service{<br> use nn-service ; Name of service template to use<br> host_name Ryan Whalen,(other hosts go here)
<br> service_description PING<br> is_volatile 0<br> check_period 24x7<br> max_check_attempts 4<br> normal_check_interval 5
<br> retry_check_interval 1<br> contact_groups admins<br> notification_interval 960<br> notification_period 24x7<br> check_command check_ping!100.0,20%!500.0,60%
<br> }<br><br><br><br><br><br><div><span class="gmail_quote">On 1/27/06, <b class="gmail_sendername">Marc Powell</b> <<a href="mailto:marc@ena.com">marc@ena.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>> -----Original Message-----<br>> From: <a href="mailto:nagios-users-admin@lists.sourceforge.net">nagios-users-admin@lists.sourceforge.net</a> [mailto:<a href="mailto:nagios-users-">nagios-users-</a><br>>
<a href="mailto:admin@lists.sourceforge.net">admin@lists.sourceforge.net</a>] On Behalf Of Ryan Whalen<br>> Sent: Friday, January 27, 2006 12:09 PM<br>> To: <a href="mailto:nagios-users@lists.sourceforge.net">nagios-users@lists.sourceforge.net
</a><br>> Subject: [Nagios-users] Pinging every host at a specific interval?<br>><br>> Hey everyone-<br>><br>> I am new to Nagios, and this morning set everything up...everything<br>seems<br>> to be working, and I have nagios pinging a small number of hosts
<br>(~50).<br>> What I would like to happen is for Nagios to ping them all every 5<br>> minutes, and display their status. However, some hosts have not been<br>> polled for over 2 hours.<br>><br>> It appears that since one device is down, Nagios is putting the
<br>priority<br>> on polling that device rather than polling the other devices in the<br>list.<br>> I would like to avaid that, because the devices that are being polled<br>are<br>> at customer locations, so there will be times when either the device
<br>is<br>> unplugged or simply locked up.<br><br>I wouldn't consider this normal behavior and may indicate a<br>configuration issue. Can you post your host and service definitions for<br>one of these 'priority' hosts? You'll probably want to specifically look
<br>at normal_check_interval, retry_check_interval and max_check_attempts.<br>Those specify how long nagios will 'dwell' on a particular host or<br>service. For service checks nagios will continue to process other checks<br>
while performing retry checks of downed services. For host checks,<br>nagios will stop all other processing while performing a host check (up<br>to max_check_attempts for that host) but will then move back to normal<br>scheduling after reaching max_check_attempts.
<br><br>--<br>Marc<br><br><br>-------------------------------------------------------<br>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files<br>for problems? Stop! Download the new AJAX search engine that makes
<br>searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!<br><a href="http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642">http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
</a><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">
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></blockquote></div><br>