Nagios 3.1.0 / is_volatile

[Stuart Browne]

Hi,

I'm trying to get a passive-checked is_volatile service working.

Currently, it accepts the passive result, changes to 'WARNING', but that's the end of it.

It doesn't return back to an OK state.

Service definition exploded out from templates as follows:

define service {
	parallelize_check			1
	freshness_threshold		1
	active_checks_enabled		0
	passive_checks_enabled		1
	obsess_over_service		0
	check_freshness			0
	notifications_enabled		1
	event_handler_enabled		1
	flap_detection_enabled		0
	failure_prediction_enabled	1
	process_perf_data			1
	retain_status_information	1
	retain_nonstatus_information	1
	is_volatile				1
	check_period			24x7
	max_check_attempts		1
	normal_check_interval		1
	retry_check_interval		1
	contact_groups			admins
	notification_options		w,u,c,r
	notification_interval		30
	notification_period		24x7
	check_command			check_dummy!0!Nobody Accessed Server Room
	host_name				cam-lock
	service_description		Server Room Access
}

Has anybody else seen this sort of behaviour before, or am I just missing something with the service configuration?

Nagios server quick-sheet:
	2 x Dual-Core 3Ghz Xeon
	2GB Memory
	65GB RAID1 SAS Storage
	RedHat Enterprise 5
	Nagios v3.1.0 (built as RPM, but no source patches)
	-> 202 Hosts
	-> 733 Services

Any other details needed?

Stuart J. Browne

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
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