Home / server / Questions / 365041
Accepted
99miles
Asked: 2012-03-01 13:00:40 +0800 CST

301 response when monit checks for file on nginx

  • 772

I have a monit script that checks that nginx is up and running. One thing it does is checks for a file 'ping.txt'. I can view it in the browser, but what would cause the script to get a 301 redirect response back?

monit script snippet:

if failed port 80 protocol http and request '/ping.txt'

Here's what's in the nginx log:

127.0.0.1 - - [29/Feb/2012:20:59:58 +0000] "GET /ping.txt HTTP/1.1" 301 185 "-" "monit/5.2.5"
ubuntu nginx monit

2 Answers

  1. Best Answer

    Are you actually able to browse to ping.txt on the localhost? Maybe you need to try the LAN IP.

    You can use a shell browser such as lynx or links2 to test. From your comment I see you may have configured it as a virtualhost. You mayneede to access the webpage using the hostname or full url, i.e. http://www.example.org/ping.txt.

    In your example you try to access 127.0.0.1 hence your webserver returns a 301.

    To change the host do something like:

    check host host.example.com with address 192.0.43.10
if failed port 80 protocol http and request '/ping.txt'

    Or leave out the address.

    • 1

  2. I know this is old but I had the same problem and got to this question through googling "monit 301" the problem in my case after quite a lot of hair pulling was that "monit was not setting the hostname header when checking my server, thus it did not get directed to the correct vhost. You can add the hostname to the check with the hostheader directive eg:

    check host www.mysite.co.uk with address wwwmysite.co.uk
  if failed
     port 443 protocol https
     and request / hostheader www.mysite.co.uk
     and status = 200
  then alert
    • 0