host state not changing

[Sbergonzi]

I have set up multiple hosts via the wizards and all are showing as 'up'. One host i configured manually, piece mail if you will via Nagios core. This host continually shows a status of 'pending'.

I compared its configuration with other hosts (items such as 'manage variable definitions' and 'status image') and all looks the same. I'm missing something, just don't know what it is. This image shows the pending one and the others. i scheduled an immediate check and it hasn't changed.

thanks!

pending state.jpg

[slansing]

Can you show the configuration for this host? CCM > Hosts > Click the diskette icon next to the host and paste the output here, highlight the configuration information once it is in the reply text box, then click the "Code" button.

[Sbergonzi]

Does first_notification_delay mean something? I noticed this host has it set(to 0) and no other host has it at all.

Code: Select all

###############################################################################
#
# Host configuration file
#
# Created by: Nagios QL Version 3.0.3
# Date:	      2014-05-07 17:55:54
# Version:    Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND --- 
# Nagios QL will overwite all manual settings during the next update
#
###############################################################################

define host {
	host_name			ctdapanwnaa1tsg
	use				xiwizard_windowsserver_host
	alias				Alfresco Auth Server
	address				10.209.22.71
	max_check_attempts		5
	check_interval			60
	retry_interval			1
	check_period			workhours
	contacts			bergonzis
	notification_interval		60
	notification_period		workhours
	first_notification_delay	0
	icon_image			win_server.png
	statusmap_image			win_server.png
	_xiwizard			windowsserver
	register			1
	}	

###############################################################################
#
# Host configuration file
#
# END OF FILE
#

[tmcdonald]

That's just the delay in minutes after an issue is raised before an alert gets sent.

[Sbergonzi]

it's now changed to 'up' and the timestamp is corrected. i guess i didn't wait long enough.

ok to close issue -