Pending status
Marc Powell
marc at ena.com
Mon Jun 6 16:28:39 CEST 2005
> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Aditya Ivaturi
> Sent: Friday, June 03, 2005 4:24 PM
> To: nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Pending status
>
>
>
>
>
> > Service definitions for nagios to check.
>
> Yup I realized that. I think there was a similar thread on the
archives
> where someone mentioned that Nagios doesn't check host without
services.
> So I defined 5 services on the localhost. But it was always in Pending
> state. Also there was another suggestion to go ahead and disable all
> service checks and then reenable them through the interface. That
didn't
> work either.
What does your scheduling queue show for Next Check?
> > Are the services on your other
> > host being checked? If no, please post the host, service and command
> > definitions in question as well as nagios version and plugins
version.
>
> Nope, as I said earlier, services on itself were not being checked.
Here
> are the details (all of them are modified version of sample configs
that
> come with fresh install of Nagios v2.0b3 and Nagios-plugin v1.4 on
Redhat
> 7.3):
>
> Host:
>
> define host{
> use generic-host ; Name of host
> template to use
> host_name localhost
> alias moya
> address 127.0.0.1
> check_command check-host-alive
> max_check_attempts 10
> notification_interval 120
> notification_period 24x7
> notification_options d,r
> contact_groups admins
> }
>
>
> SERVICES:
> define service{
> use generic-service ; Name
of
> service template to use
> host_name localhost
> service_description Root Partition
> is_volatile 0
> check_period 24x7
> max_check_attempts 4
> normal_check_interval 5
> retry_check_interval 1
> contact_groups admins
> notification_interval 960
> notification_period 24x7
> check_command check_local_disk!20%!10%!/
> }
> # Define a service to check the load on the local machine.
>
> define service{
> use generic-service ; Name
of
> service template to use
> host_name localhost
> service_description Current Load
> is_volatile 0
> check_period 24x7
> max_check_attempts 4
> normal_check_interval 5
> retry_check_interval 1
> contact_groups admins
> notification_interval 960
> notification_period 24x7
> check_command
> check_local_load!5.0,4.0,3.0!10.0,6.0,4.0
[service/command definitions snipped]
All these look good. To simplify things for troubleshooting, I'd disable
these in your generic-service template --
passive_checks_enabled
obsess_over_service
check_freshness
event_handler_enabled
failure_prediction_enabled
process_perf_data
retain_status_information
retain_nonstatus_information
I would also, if you have it enabled, disable retain_state_information
in nagios.cfg, stop nagios, verify that all processes are dead, remove
the state_retention_file and restart nagios.
Finally, check nagios.log for any interesting output that might indicate
a problem.
--
Marc
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
_______________________________________________
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
More information about the Users
mailing list