Problem with false status

Dale Hobbs dhobbs at chancery.com
Fri Aug 20 19:29:50 CEST 2004


Nope, that all looks good.

 

Note. 

If you decide to use fping instead of ping the only thing you will need
to do now that you've got fping installed would be to change ping to
fping in the checkcommands file and setuid to root on the fping file.
Not sure where it is on your system but on my machine it's in
/usr/sbin/fping. If you decide that you do not want to use fping then
disregard this part

 

-----Original Message-----
From: lmcilwain [mailto:lmcilwain at opnet.com] 
Sent: Friday, August 20, 2004 10:21 AM
To: Dale Hobbs
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Problem with false status

 

Alright, 

 

Here is what I have changed if I read correctly: 

 

1. In my hosts.cfg file I have the following entry (in bold is what was
changed): 

 

# 'jello' host definition 

define host{ 

use generic-host ; Name of host template to use 

host_name jelloxx 

alias jelloxx 

address 172.16.1.x 

check_command check_host_alive 

max_check_attempts 10 

notification_interval 30 

notification_period 24x7 

notification_options d,u,r 

 

2. In my checkcommands.cfg I have the following entries. Entry number
one was change back to it's original and entry number 2 was added. These
are both generic so if I decide to add more machines I will most likely
be ok. 

 

# 'check-host-alive' command definition 

define command{ 

command_name check-host-alive 

command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80% -c
5000.0,100% -p 1 

} 

 

# 'check_ping' command definition 

define command{ 

command_name check_ping 

command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80% -c
5000.0,100% -p 5 

 

3. I installed fping from sunfreeware.com using pkgadd -d so that is now
installed on my machine. 

 

Is there anything else that you can think of that I may need before I
restart nagios? 

 

Thanks, 

 

On Aug 20, 2004, at 12:44 PM, Dale Hobbs wrote: 

	 

	If you want to use check_ping instead of check_fping then you
can change 

	the check_ping command definition in the checkcommands.cfg file
to: 

	 

	# 'check_ping' command definition 

	define command{ 

	command_name check_ping 

	command_line $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ 

	-c $ARG2$ -n $ARG3$ 

	} 

	 

	You should probably leave the check-host-alive command as it was
upon 

	installation otherwise you will run into problems if you have
more than 

	one host. The check-host-alive command should be as follows: 

	 

	# 'check-host-alive' command definition 

	define command{ 

	command_name check-host-alive 

	command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 

	3000.0,80% -c 5000.0,100% -p 1 

	} 

	If you set it the way that you changed it 

	# 'check-host-alive' command definition 

	define command{ 

	command_name check_ping 

	command_line $USER1$/check_ping -H $jello -w 3000.0,80% -c 

	5000.0,100% -p 1 

	 

	Then it will only check the host jello. The -H $HOSTADDRESS$ is
a string 

	that gets it's info from the ip address of the hosts.cfg file.
For 

	example 

	 

	You have a host called jello whose ip address is 192.168.1.1. In
the 

	services.cfg file you specify that you want Nagios to do a
check_ping on 

	the host jello. The services.cfg file then looks at the
hosts.cfg file 

	to find the ipaddress for the host jello and inserts it into the


	$HOSTADDRESS$ string. Now, if you have a jello2 host and want to
do a 

	check_ping on it as well it will take that hosts ip address and
insert 

	it into the $HOSTADDRESS$ string. If you change that string to
$jello$ 

	then the check_ping command will only ever check the host jello.


	
	
	
	
	
	
	

	-----Original Message----- 

	From: lmcilwain [mailto:lmcilwain at opnet.com] 

	Sent: Friday, August 20, 2004 9:21 AM 

	To: Dale Hobbs 

	Cc: nagios-users at lists.sourceforge.net 

	Subject: Re: [Nagios-users] Problem with false status 

	 

	Is there a way to tell it to use check_ping instead of
check_fping? 

	 

	I have made the first change and my checkcommands has the
following: 

	 

	# 'check-host-alive' command definition 

	define command{ 

	command_name check_ping 

	command_line $USER1$/check_ping -H $jello -w 3000.0,80% -c 

	5000.0,100% -p 1 

	# command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 

	3000.0,80% -c 5000.0,100% -p 1 

	 

	I will check and see if they have an fping program for solaris 8
since 

	this is what my program is running on. 

	 

	Thanks 

	On Aug 20, 2004, at 11:45 AM, Dale Hobbs wrote: 

		 

		You may want to modify your hosts.cfg file as follows 

		 

		# 'jello' host definition 

		define host{ 

		use generic-host ; Name of 

	host 

		 

		template to use 

		 

		host_name jello2 

		alias jello2 

		address 172.16.1.x 

		check_command check_host_alive 

		max_check_attempts 10 

		notification_interval 30 

		notification_period 24x7 

		notification_options d,u,r 

		 

		Also you should have something in relating to the
check_ping in your 

		checkcommands.cfg file similar to this 

		 

		# 'check_ping' command definition 

		define command{ 

		command_name check_ping 

		command_line $USER1$/check_fping -H $HOSTADDRESS$ -w
$ARG1$ 

		-c $ARG2$ -n $ARG3$ 

		} 

		 

		I believe by default it uses the check_fping instead of
check ping. If 

		you compiled Nagios yourself then there is a file called
REQUIREMENTS 

		that is included with all the files that says the
following 

		 

		check_fping: 

		- Requires the fping utility distributed with SATAN.
Either 

		download and install SATAN or grab the fping program
from 

		http://www.fping.com 

		http://www.stanford.edu/~schemers/docs/fping/fping.html 

		 

	
ftp://ftp.redhat.com/pub/contrib/libc6/SRPMS/fping-2.2b1-1.src.rpm 

		 

	
ftp://ftp.redhat.com/pub/contrib/libc6/RPMS/fping-2.2b1-1.i386.rpm 

		Note that the fping command must be setuid root to
function. 

		 

		That will most likely fix the problem for you. Or you
could just 

	change 

		the fping to ping in the checkcommands.cfg file 

		 

		-----Original Message----- 

		From: nagios-users-admin at lists.sourceforge.net 

		[mailto:nagios-users-admin at lists.sourceforge.net] On
Behalf Of 

		lmcilwain 

		Sent: Friday, August 20, 2004 7:23 AM 

		To: Darren.Lichty at alltel.com 

		Cc: nagios-users at lists.sourceforge.net 

		Subject: Re: [Nagios-users] Problem with false status 

		 

		Sorry I didn't see this e mail before. Here is what you
wanted to 

	see. 

		 

		It is only one machine that I need to monitor. 

		 

		Here is what my hosts.cfg file looks like. 

		 

		# 'jello' host definition 

		define host{ 

		use generic-host ; Name of 

	host 

		 

		template to use 

		 

		host_name jello2 

		alias jello2 

		address 172.16.1.x 

		check_command check_ping 

		max_check_attempts 10 

		notification_interval 30 

		notification_period 24x7 

		notification_options d,u,r 

		 

		Here is my services.cfg file for that same machine: 

		 

		# Service definition 

		define service{ 

		use generic-service ; 

	Name 

		 

		of service template to use 

		 

		host_name jello2 

		service_description check_ping 

		is_volatile 0 

		check_period 24x7 

		max_check_attempts 3 

		normal_check_interval 3 

		retry_check_interval 1 

		contact_groups opnet-admins 

		notification_interval 30 

		notification_period 24x7 

		notification_options w,u,c,r 

		check_command check_ping 

		 

		On Aug 19, 2004, at 11:05 PM, <Darren.Lichty at alltel.com>
wrote: 

			 

			Can you provide an example of the host and
service definitions? 

			 

			At first glance, I would have to say there is an
option in the host 

			definition that needs adjustment, but it is
difficult to say for 

	sure. 

			 

			Seeing the definition may help in trying to
isolate the issue. 

			 

			-Darren 

			 

			-----Original Message----- 

			From: nagios-users-admin at lists.sourceforge.net 

	
[mailto:nagios-users-admin at lists.sourceforge.net]On Behalf Of 

		lmcilwain 

			Sent: Thursday, August 19, 2004 1:51 PM 

			To: nagios-users at lists.sourceforge.net 

			Subject: [Nagios-users] Problem with false
status 

			 

			Hello all, 

			 

			I am new to installing nagios and I am having a
common problem that I 

			can't seem to solve. 

			 

			Right now I have configured nagios to monitor a
machine to check and 

			see if it is up or down using ping. Nagios has
noticed that the 

			particular machine was done when I did a reboot
to test to see if the 

			notification was working. That worked with no
problems. However... 

			Now that the machine is back up and running,
nagios is still saying 

			that this machine is down. If I look at the web
interface it says 

		that 

			its down and I am getting a page every 2 hours
letting me know that 

		the 

			machine is still down. I can get the machine
that it is monitoring 

			with no problems and even the machine that
nagios is running on can 

		get 

			to this machine. 

			 

			I checked the FAQ on nagios.org and it told me
to "Make sure that the 

			host check command in your host definition is
configured correctly." 

			Unfortunately I don't know which file they are
talking about. I 

			checked the hosts.cfg file and it seems to be
fine (from what I can 

			tell). Can anyone give me a better idea of what
I am looking for and 

			how to solve this? 

			 

			Thanks, 

			
			
			

	
------------------------------------------------------- 

			SF.Net email is sponsored by
Shop4tech.com-Lowest price on Blank 

	Media 

			100pk Sonic DVD-R 4x for only $29 -100pk Sonic
DVD+R for only $33 

			Save 50% off Retail on Ink & Toner - Free
Shipping and Free Gift. 

	
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 

			_______________________________________________ 

			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 

			 

		 

	
*********************************************************************** 

			******************* 

			The information contained in this message,
including attachments, may 

			 

			contain 

			privileged or confidential information that is
intended to be 

			delivered only to the 

			person identified above. If you are not the
intended recipient, or 

	the 

			 

			person 

			responsible for delivering this message to the
intended recipient, 

			ALLTEL requests 

			that you immediately notify the sender and asks
that you do not read 

			the message or its 

			attachments, and that you delete them without
copying or sending them 

			 

			to anyone else. 

			
			
			

	
------------------------------------------------------- 

			SF.Net email is sponsored by
Shop4tech.com-Lowest price on Blank 

	Media 

			100pk Sonic DVD-R 4x for only $29 -100pk Sonic
DVD+R for only $33 

			Save 50% off Retail on Ink & Toner - Free
Shipping and Free Gift. 

	
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 

			_______________________________________________ 

			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 

			 

		
		
		

		------------------------------------------------------- 

		SF.Net email is sponsored by Shop4tech.com-Lowest price
on Blank Media 

		100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for
only $33 

		Save 50% off Retail on Ink & Toner - Free Shipping and
Free Gift. 

		http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 

		_______________________________________________ 

		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 

		 

	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040820/5b227870/attachment.html>


More information about the Users mailing list