Re: [Nagios-users] Nagios v3.5.0 transitioning immediately to a HARD state upon host problem
I ran into a similar problem, because my template set the service to "*
is_volatile=1*".
http://nagios.sourceforge.net/docs/3_0/volatileservices.html
Check to see if you have this flag enabled.
Doug
Sincerely,
Doug Eubanks
ad...@dougware.net
K1DUG
(919) 201-8750
On Thu, May 23, 2013 at 11:43 AM, C. Bensend wrote:
>
> Hey folks,
>
>I recently made two major changes to my Nagios environment:
>
> 1) I upgraded to v3.5.0.
> 2) I moved from a single server to two pollers sending passive
>results to one central console server.
>
>Now, this new distributed system was in place for several months
> while I tested, and it worked fine. HOWEVER, since this was running
> in parallel with my production system, notifications were disabled.
> Hence, I didn't see this problem until I cut over for real and
> enabled notifications.
>
> (please excuse any cut-n-paste ugliness, had to send this info from
> my work account via Outlook and then try to cleanse and reformat
> via Squirrelmail)
>
>As a test and to capture information, I reboot 'hostname'. This
> log is from the nagios-console host, which is the host that accepts
> the passive check results and sends notifications. Here is the
> console host receiving a service check failure when the host is
> restarting:
>
> May 22 15:57:10 nagios-console nagios: SERVICE ALERT: hostname;/var disk
> queue;CRITICAL;SOFT;1;Connection refused by host
>
>
> So, the distributed poller system checks the host and sends its
> results to the console server:
>
> May 22 15:57:30 nagios-console nagios: HOST
> ALERT:hostname;DOWN;SOFT;1;CRITICAL - Host Unreachable (a.b.c.d)
>
>
> And then the centralized server IMMEDIATELY goes into a hard state,
> which triggers a notification:
>
> May 22 15:57:30 nagios-console nagios: HOST ALERT:
> hostname;DOWN;HARD;1;CRITICAL - Host Unreachable (a.b.c.d)
> May 22 15:57:30 nagios-console nagios: HOST NOTIFICATION:
> cbensend;hostname;DOWN;host-notify-by-email-test;CRITICAL -
> Host Unreachable (a.b.c.d)
>
>
>Um. Wat? Why would the console immediately trigger a hard
> state? The config files don't support this decision. And this
> IS a problem with the console server - the distributed monitors
> continue checking the host for 6 times like they should. But
> for some reason, the centralized console just immediately
> calls it a hard state.
>
>Definitions on the distributed monitoring host (the one running
> the actual host and service checks for this host 'hostname':
>
> define host {
> host_namehostname
> aliasOld production Nagios server
> address a.b.c.d
> action_url /pnp4nagios/graph?host=$HOSTNAME$
> icon_image_alt Red Hat Linux
> icon_image redhat.png
> statusmap_image redhat.gd2
> check_commandcheck-host-alive
> check_period 24x7
> notification_period 24x7
> contact_groups linux-infrastructure-admins
> use linux-host-template
> }
>
> The linux-host-template on that same system:
>
> define host {
> name linux-host-template
> register 0
> max_check_attempts 6
> check_interval 5
> retry_interval 1
> notification_interval360
> notification_options d,r
> active_checks_enabled1
> passive_checks_enabled 1
> notifications_enabled1
> check_freshness 0
> check_period 24x7
> notification_period 24x7
> check_commandcheck-host-alive
> contact_groups linux-infrastructure-admins
> }
>
> And said command to determine up or down:
>
> define command {
> command_name check-host-alive
> command_line $USER1$/check_ping -H $HOSTADDRESS$ -w
> 5000.0,80% -c 1.0,100% -p 5
> }
>
>
> Definitions on the centralized console host (the one that notifies):
>
> define host {
> host_namehostname
> aliasOld production Nagios server
> address a.b.c.d
> action_url /pnp4nagios/graph?host=$HOSTNAME$
> icon_image_alt Red Hat Linux
> icon_image redhat.png
> statusmap_image redhat.gd2
> check_commandcheck-host-alive
> check_period 24x7
> notification_period 24x7
> contact_groups linux-infrastructure-admins
> use
[Nagios-users] Escalations and Notification Intervals
I have four escalations setup. Overall, they work well, but sometimes I get a RECOVERY and never got a WARNING or CRITICAL, or I'll get a WARNING or CRITICAL and never get the recovery. My guess is that it has to do with my notification intervals. Does that look like the problem? The normal notification is 1 time unit, or 1 minute. Recovery Notifications Escalation Information *First Notification:* #3 Notification *Notification Interval:* 4 Time-Units *Escalation Period:* 24x7 *Escalation Options:* Ok Hourly Notification Escalation Information *First Notification:* #5 Notification *Notification Interval:* 60 Time-Units *Escalation Period:* 24x7 *Escalation Options:* Warning,Unknown,Critical 10 Minute Delay / 4 Minute Page / Max 4 Pages Escalation Information *First Notification:* #2 Notification *Last Notification:* #5 Notification *Notification Interval:* 4 Time-Units *Escalation Period:* 24x7 *Escalation Options:* Warning,Unknown,Critical Thanks, Doug Eubanks ad...@dougware.net K1DUG (919) 201-8750 -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may___ 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
Re: [Nagios-users] Nagios running checks way too often
I fixed the problem! It was an issue with our Check Result Reaper Frequency and Maximum Check Result Reaper Time, adjusting these fixed the issue. Thanks for the pointers! Doug Eubanks ad...@dougware.net K1DUG (919) 201-8750 On Fri, Dec 7, 2012 at 2:56 AM, Claudio Kuenzler wrote: > On Fri, Dec 7, 2012 at 6:34 AM, Doug Eubanks wrote: > >> I removed the spaces from the command. I noticed that there were two >> Nagios processes running, so I killed them both and restarted Nagios. >> >> Within a few minutes, it was checking the site more often that it should: >> Nagios - - [07/Dec/2012:00:29:05 -0500] "GET / HTTP/1.1" 200 22458 "-" >> "check_http/v1.4.16 (nagios-plugins 1.4.16)" >> Nagios - - [07/Dec/2012:00:29:28 -0500] "GET / HTTP/1.1" 200 22459 "-" >> "check_http/v1.4.16 (nagios-plugins 1.4.16)" >> Nagios - - [07/Dec/2012:00:30:13 -0500] "GET / HTTP/1.1" 200 22459 "-" >> "check_http/v1.4.16 (nagios-plugins 1.4.16)" >> Nagios - - [07/Dec/2012:00:31:19 -0500] "GET / HTTP/1.1" 200 22459 "-" >> "check_http/v1.4.16 (nagios-plugins 1.4.16)" >> Nagios - - [07/Dec/2012:00:31:22 -0500] "GET / HTTP/1.1" 200 22459 "-" >> "check_http/v1.4.16 (nagios-plugins 1.4.16)" >> Nagios - - [07/Dec/2012:00:31:44 -0500] "GET / HTTP/1.1" 200 22459 "-" >> "check_http/v1.4.16 (nagios-plugins 1.4.16)" >> Nagios - - [07/Dec/2012:00:32:29 -0500] "GET / HTTP/1.1" 200 22458 "-" >> "check_http/v1.4.16 (nagios-plugins 1.4.16)" >> Nagios - - [07/Dec/2012:00:33:36 -0500] "GET / HTTP/1.1" 200 22459 "-" >> "check_http/v1.4.16 (nagios-plugins 1.4.16)" >> Nagios - - [07/Dec/2012:00:33:38 -0500] "GET / HTTP/1.1" 200 22459 "-" >> "check_http/v1.4.16 (nagios-plugins 1.4.16)" >> > > Can you still post the command definition? > > Did you try to use an alternative command defintion, e.g. check_website, > see last mail. > > > -- > 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
Re: [Nagios-users] Nagios running checks way too often
I removed the spaces from the command. I noticed that there were two
Nagios processes running, so I killed them both and restarted Nagios.
Within a few minutes, it was checking the site more often that it should:
Nagios - - [07/Dec/2012:00:29:05 -0500] "GET / HTTP/1.1" 200 22458 "-"
"check_http/v1.4.16 (nagios-plugins 1.4.16)"
Nagios - - [07/Dec/2012:00:29:28 -0500] "GET / HTTP/1.1" 200 22459 "-"
"check_http/v1.4.16 (nagios-plugins 1.4.16)"
Nagios - - [07/Dec/2012:00:30:13 -0500] "GET / HTTP/1.1" 200 22459 "-"
"check_http/v1.4.16 (nagios-plugins 1.4.16)"
Nagios - - [07/Dec/2012:00:31:19 -0500] "GET / HTTP/1.1" 200 22459 "-"
"check_http/v1.4.16 (nagios-plugins 1.4.16)"
Nagios - - [07/Dec/2012:00:31:22 -0500] "GET / HTTP/1.1" 200 22459 "-"
"check_http/v1.4.16 (nagios-plugins 1.4.16)"
Nagios - - [07/Dec/2012:00:31:44 -0500] "GET / HTTP/1.1" 200 22459 "-"
"check_http/v1.4.16 (nagios-plugins 1.4.16)"
Nagios - - [07/Dec/2012:00:32:29 -0500] "GET / HTTP/1.1" 200 22458 "-"
"check_http/v1.4.16 (nagios-plugins 1.4.16)"
Nagios - - [07/Dec/2012:00:33:36 -0500] "GET / HTTP/1.1" 200 22459 "-"
"check_http/v1.4.16 (nagios-plugins 1.4.16)"
Nagios - - [07/Dec/2012:00:33:38 -0500] "GET / HTTP/1.1" 200 22459 "-"
"check_http/v1.4.16 (nagios-plugins 1.4.16)"
Doug Eubanks
ad...@dougware.net
K1DUG
(919) 201-8750
On Thu, Dec 6, 2012 at 11:22 AM, Claudio Kuenzler
wrote:
>
>
> On Thu, Dec 6, 2012 at 1:13 AM, Doug Eubanks wrote:
>
>> 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_delay0
>> active_checks_enabled 1
>> passive_checks_enabled 1
>> check_period24x7
>> 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_information1
>> 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_namewebsite.com
>> notification_optionsw,u,c,r,f,s
>> stalking_optionso,w,u,c
>> contact_groups Null Placeholder Group
>> servicegroups Public Facing Services
>> }
>>
>>
> You're right, the check should only happen every 2 mins
> (normal_check_interval).
> But what looks strange to me is the check_command.
> Do you actually have command definition called "check_http - vhost - url -
> string" ? I'm not sure if spaces are allowed in the definition.
> Can you post the command definition?
>
>
> What happens if you change the check_command to the following:
>
> check_commandcheck_website!www.website.com!-u /
>
> where the command definition of check_website looks like that:
>
> define command{
> command_namecheck_website
> c
Re: [Nagios-users] Nagios running checks way too often
We use Lilac as a configuration GUI, and as a sanity check I checked to
make sure the service was only specified once in the configuration file.
Sincerely,
Doug Eubanks
ad...@dougware.net
K1DUG
(919) 201-8750
On Wed, Dec 5, 2012 at 7:13 PM, Doug Eubanks wrote:
> 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_delay0
> active_checks_enabled 1
> passive_checks_enabled 1
> check_period24x7
> 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_information1
> 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_namewebsite.com
> notification_optionsw,u,c,r,f,s
> stalking_optionso,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
> wrote:
>
>>
>>
>> On Tue, Dec 4, 2012 at 4:44 PM, Doug Eubanks 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
Re: [Nagios-users] Nagios running checks way too often
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_delay0
active_checks_enabled 1
passive_checks_enabled 1
check_period24x7
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_information1
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_namewebsite.com
notification_optionsw,u,c,r,f,s
stalking_optionso,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
wrote:
>
>
> On Tue, Dec 4, 2012 at 4:44 PM, Doug Eubanks 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
[Nagios-users] Nagios running checks way too often
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: sleep_time=20 service_interleave_factor=s max_concurrent_checks=0 service_reaper_frequency=5 interval_length=60 service_check_timeout=75 host_check_timeout=75 obsess_over_services=1 process_performance_data=1 check_for_orphaned_services=0 check_service_freshness=1 service_inter_check_delay_method=s use_retained_scheduling_info=1 max_service_check_spread=1 host_inter_check_delay_method=s max_host_check_spread=1 auto_reschedule_checks=1 auto_rescheduling_interval=15 auto_rescheduling_window=30 Nagios Version Information: nagios-3.4.1-2.el6.i686 Here's the access log from the service being checked. This is only one vhost, and that one vhost is only in Nagios as a service once. 198.17.xxx.xxx - - [04/Dec/2012:10:31:41 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:31:41 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:31:44 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:31:50 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:31:50 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:31:50 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:32:37 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:32:37 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:32:38 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:33:46 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:33:46 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:33:48 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:33:55 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:33:55 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:33:55 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:34:43 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:34:43 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:34:43 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:35:52 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:35:52 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:35:55 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:36:01 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:36:01 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:36:01 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:36:49 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:36:49 -0500] "GET / HTTP/1.1" 200 22414 "-" "check_http/v1.4.16 (nagios-plugins 1.4.16)" 198.17.xxx.xxx - - [04/Dec/2012:10:36:49 -0500] "GET / HTTP/1.1" 200 22414
[Nagios-users] 'Service is not scheduled to be checked...' & 'Host is not scheduled to be checked...'
otifications_enabled 1 failure_prediction_enabled 0 alias server1.dougware.net display_nameServer1 address server1.dougware.net notification_optionsd,u,r,s contact_groups DougWare hostgroups DougWare } I'm sure that I have a really simple issue, but I just can't put my finger on it. Thanks for the help! Sincerely, Doug Eubanks ad...@dougware.net (919) 201-8750 -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ 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
