Of course you are correct, here's one of the services. According to the
site log, it looks like Nagios is firing off three to four requests to the
server, each time it's being checked. These log entries are all from one
vhost log file, so it's not like Nagios is checking 4 sites, it's checking
the same site 4 times at once.
NagiosServer - - [05/Dec/2012:19:09:40 -0500] "GET / HTTP/1.1" 200 22459
"-" "check_http/v1.4.16 (nagios-plugins 1.4.16)"
NagiosServer - - [05/Dec/2012:19:09:40 -0500] "GET / HTTP/1.1" 200 22459
"-" "check_http/v1.4.16 (nagios-plugins 1.4.16)"
NagiosServer - - [05/Dec/2012:19:09:40 -0500] "GET / HTTP/1.1" 200 22459
"-" "check_http/v1.4.16 (nagios-plugins 1.4.16)"
NagiosServer - - [05/Dec/2012:19:09:40 -0500] "GET / HTTP/1.1" 200 22459
"-" "check_http/v1.4.16 (nagios-plugins 1.4.16)"
define service {
host_name server
service_description www.website.com
initial_state o
is_volatile 0
max_check_attempts 2
normal_check_interval 2
retry_interval 1
first_notification_delay 0
active_checks_enabled 1
passive_checks_enabled 1
check_period 24x7
parallelize_check 1
obsess_over_service 1
check_freshness 1
freshness_threshold 60
event_handler_enabled 1
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
notification_interval 4
notification_period 24x7
notifications_enabled 1
action_url
/pnp4nagios/index.php?host=$HOSTNAME$&srv=$SERVICEDESC$
check_command check_http - vhost - url - string!www.website.com
!/!Ap$
icon_image www.png
display_name website.com
notification_options w,u,c,r,f,s
stalking_options o,w,u,c
contact_groups Null Placeholder Group
servicegroups Public Facing Services
}
Sincerely,
Doug Eubanks
ad...@dougware.net
K1DUG
(919) 201-8750
On Wed, Dec 5, 2012 at 2:26 AM, Claudio Kuenzler
<c...@claudiokuenzler.com>wrote:
>
>
> On Tue, Dec 4, 2012 at 4:44 PM, Doug Eubanks <ad...@dougware.net> wrote:
>
>> Nagios is checking services way too often. It's supposed to check once
>> every 2 minutes, then failback to checking once every 1 minute on a failure.
>>
>> I believe this is the relevant parts of the nagios.cfg file:
>>
>
> Actually the relevant part for how often a check should be executed is in
> the service definition of the check. Mostly the service itself uses a
> template with the "use" option. In this case you have to check your
> templates.cfg file.
>
> If you don't find it, please post the relevant service definition and the
> definition of the template being used by the service.
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Nagios-users mailing list
> Nagios-users@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
>
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Nagios-users mailing list
Nagios-users@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
