• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 11316
  • Last Modified:

Nagios check_http

Hello,

When I try to run the check_http plug-in from Nagios to a Sharepoint (Windows) server I get the HTTP WARNING: HTTP/1.1 401 Unauthorized message.  I run the check_http command on other Unix boxes without any problems.  I've tried it with the -a option and a valid username and password but get the same message.  Here's what I get:

GET / HTTP/1.0
User-Agent: check_http/v1759 (nagios-plugins 1.4.10)
Connection: close

STATUS: HTTP/1.1 401 Unauthorized
**** HEADER ****
Server: Microsoft-IIS/7.0
WWW-Authenticate: NTLM
X-Powered-By: ASP.NET
MicrosoftSharePointTeamServices: 12.0.0.6335
Date: Wed, 29 Apr 2009 20:12:06 GMT
Connection: close
Content-Length: 0
**** CONTENT ****

HTTP WARNING: HTTP/1.1 401 Unauthorized

Any help would be appreciated.

Thanks,

John
0
cirrusitaus
Asked:
cirrusitaus
1 Solution
 
James MurrellProduct SpecialistCommented:
You can use Filemon from Sysinternals http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx to see what folders / files are getting access denied.  You can also look in your Security event log to see what failures (assuming you have auditing enabled) to see what user account is accessing the machine.
0
 
cirrusitausAuthor Commented:
Thanks for the suggestion, I looked at the security event logs and didn't see anything that pertained to the check_http command from Nagios.  Also, I forgot to mention that Sharepoint is on a Windows 2008 server and I didn't mention that the Nagios version we use is Nagios 2.10.

Thanks,

John
0
 
cirrusitausAuthor Commented:
Figured out a work-around.  Normal check_http in this case returns a warning.  Will not notify admins unless check returns a critical.
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
cirrusitausAuthor Commented:
Just to let you know that this question will be put on hold.  The admin had to leave on a family emergency
0
 
mikedaddyCommented:
I came across this post, when I was having the same issue, i modified the config file for http in /etc/nagios-plugins/config/http.cfg

added:

define command{
    command_name    check_http_authntlm
    command_line    /usr/lib/nagios/plugins/check_http -H $HOSTADDRESS$ -I $HOSTADDRESS$ -e 'HTTP'
}

this was a simple quick fix. As long as the server responds with an HTTP header, then its considered up. Which is fine, we dont need to authenticate to know IIS is working.
0
 
TPS SupportCommented:
Make sure that you have a separate hostgroup and a separate service defined that runs the command_name / check_command 'check_http_authntlm'

It took me hours to figure this out because the command http and service http was the same.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now