Nagios check_http

Posted on 2009-04-29
Last Modified: 2014-06-30

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
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.


Question by:cirrusitaus
    LVL 31

    Expert Comment

    by:James Murrell
    You can use Filemon from Sysinternals 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.

    Author Comment

    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.



    Author Comment

    Figured out a work-around.  Normal check_http in this case returns a warning.  Will not notify admins unless check returns a critical.

    Accepted Solution

    Just to let you know that this question will be put on hold.  The admin had to leave on a family emergency
    LVL 1

    Expert Comment

    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


    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.

    Expert Comment

    by:TPS Support
    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.

    Featured Post

    What Is Threat Intelligence?

    Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

    Join & Write a Comment

    Have you ever stumbled upon a software that is so great that you just love? It happened to me. Love at first sight. Filezilla Server.   Ok its not the most advanced ftp server I've came across. But its a fairly simple piece of software to get the …
    In this article we have discussed the manual scenarios to recover data from Windows 10 through some backup and recovery tools which are offered by it.
    Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
    Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…

    732 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    19 Experts available now in Live!

    Get 1:1 Help Now