error code 127 after each server reload

[FM]

I already red this FAQ thank you :-)

For ex, tomcat service
in my nagios.cfg :
resource_file=/etc/nagios/resource.cfg
resource_file=/etc/nagios/services.cfg
resource_file=/etc/nagios/checkcommands.cfg


inside /etc/nagios/services.cfg
My service for tomact for example :
define command {
	command_name	check_tomcat
	command_line	$USER1$/check_http -H $HOSTADDRESS$ -p 8080

inside /etc/nagios/resource.cfg :
$USER1$=/usr/lib/nagios/plugins

inside /etc/nagios/services.cfg :
define service{
	use				generic-service		; Name of service template to use

	host_name			salerno.lan.lexum.pri
	service_description		TOMCAT
	is_volatile			0
	check_period			24x7
	max_check_attempts		3
	normal_check_interval		5
	retry_check_interval		1
	contact_groups			linux-admins
	notification_interval		120
	notification_period		24x7
	notification_options		w,u,c,r
	check_command			check_tomcat
	}

Bu I still have :


Subhendu Ghosh wrote:
> On Wed, 31 Aug 2005, FM wrote:
> 
>> Hello,
>> I'm having a great time configuring this beast !
>> Each time that I reload or restart NAGIOS I recevied error 127 for all 
>> services (and also lots of false positive email)
>> ex :
>> Warning: Return code of 127 for check of service 'NFS' on host 
>> 'SERVER' was out of bounds. Make sure the plugin you're trying to run 
>> actually exists.
>>
>> I'm using nagios 2.0b4
>>
>>
> 
> FAQ ID F0017
> 

-- 
Frederic Medery
System Administrator

LexUM, University of Montreal


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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