The status file is only created/updated:
1. At regular intervals when aggregated updates are enabled
and/or
2. When the status of a host or service changes (i.e. a check is
performed, a notification occurs, etc.)
Check the log file to make sure the passive checks are being received
and processed. I'm guessing that's where the problem lies - if the
passive checks aren't being processed, there's no reason for Nagios
to create the status file. Actually, that might not be totally
correct. Nagios should create a status file immediately upon
startup. Check your config file to make sure you don't have more
than one status_file definition, etc.
I would also suggest that you enable aggregated status updates - not
doing so is a huge waste of CPU/disk time when you have a lot of
monitoring activity.
On 26 Nov 2003 at 14:42, Marc Powell wrote:
> Hey all,
>
> I'm starting to play with 2.0a1 (CVS autobuild dated 11/25) and I'm
> having a problem right off the bat. I'm starting with a pretty simple
> compile (only specifying cgi/htmurl) and configuration (3 hosts, 4
> services, 1 contact). The hosts and services are set up to be passive
> --
>
> (template definitions)
>
> define host{
> name generic-host
> notifications_enabled 1 ; Host notifications
> are
> enabled
> event_handler_enabled 1 ; Host event handler
> is
> enabled
> flap_detection_enabled 1 ; Flap detection is
> enabled
> process_perf_data 1 ; Process performance
> data
> retain_status_information 1 ; Retain status
> information across program restarts
> retain_nonstatus_information 1 ; Retain non-status
> information across program restarts
> max_check_attempts 10
> notification_interval 10080
> notification_period 24x7
> notification_options d,r
>
> register 0 ; DONT REGISTER THIS
> DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
> }
>
> # Generic service definition template
> define service{
> name generic-service
> active_checks_enabled 1 ; Active service
> checks
> are enabled
> passive_checks_enabled 1 ; Passive service
> checks
> are enabled/accepted
> parallelize_check 1 ; Active service
> checks
> should be parallelized
> obsess_over_service 1 ; We should obsess
> over
> this service (if necessary)
> check_freshness 0 ; Default is to NOT
> check service 'freshness'
> notifications_enabled 1 ; Service
> notifications
> are enabled
> event_handler_enabled 1 ; Service event
> handler
> is enabled
> flap_detection_enabled 1 ; Flap detection is
> enabled
> process_perf_data 1 ; Process performance
> data
> retain_status_information 1 ; Retain status
> information across program restarts
> retain_nonstatus_information 1 ; Retain non-status
> information across program restarts
> is_volatile 0
> check_period none
> max_check_attempts 5
> normal_check_interval 5
> retry_check_interval 3
> notification_interval 10080
> notification_period 24x7
> notification_options c,r
>
> register 0 ; DONT REGISTER THIS
> DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
> }
>
> (example host and service definitions) --
>
> # Host definition
> define host {
> use generic-host
> host_name tnops-cedarbluff-int.knox.tn.ena.net
> alias ced
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]