check_http

[VanZee, Timothy]

It could be resolving the server name with something other than dns, in
which case it may be case sensitive as *NIX platforms are.  Browsers are
intended to resolve the issues themselves and generally are not case
sensitive.
 
Whatever the cause, I'm not sure what your problem is because you have
stated your question/problem and your own resolution in the same e-mail.
 
 

Tim Van Zee 
ITS Network Specialist 
Governors State University 


	-----Original Message-----
	From: Matthew.Quinney at hollandandholland.com
[mailto:Matthew.Quinney at hollandandholland.com] 
	Sent: Wednesday, March 26, 2003 3:45 AM
	To: nagios-users at lists.sourceforge.net
	Subject: [Nagios-users] check_http
	
	

	Good morning all, 
	
	I am having a problem with check_http. I have added another
server to my check_http service service which has been working fine with
a number of other servers for almost a year now. Whenever the check_http
commands runs against the new server, I get the following warning
message : 
	
	[root at MyServer libexec]# ./check_http -H 194.0.1.95 
	HTTP WARNING: HTTP/1.1 403 Forbidden 
	
	If I run it against the server name, ie ./check_http -H eros,
then it fails....BUT, if I run it against the capitalised server name,
ie EROS then it works ! I'm stumped ! 
	
	I can surf to the web server okay throgh a web browser by IP and
lower and upper case server names. 
	
	I'm running Nagios V1.0 and v1.30-alpha of the plugins. Has
anybody else seen this...because I am loosing hair now ! 
	
	Many thanks 
	
	Matt 
	

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