I have noticed in my production Rails log that exactly every 5 minutes, I have a GET request to my root url from 127.0.0.1 which apparently is my localhost.
Started GET "/" for 127.0.0.1 at 2012-07-01 14:05:03 -0500
Processing by ApplicationController#landing as */*
Rendered shared/_header.html.erb (0.9ms)
Rendered shared/_footer.html.erb (0.5ms)
Rendered application/landing.html.erb (5.7ms)
Completed 200 OK in 8ms (Views: 7.9ms)
I have never seen this in any other Rails apps. I am using New Relic, MongoDB, Nginx, and Unicorn. Can anyone tell my why this is happening or what it means?
This is most likely a monitoring application, especially since it's only checking the root path for a successful connection (i.e. HTTP 200). Have you installed any tools such as monit? What hosting provider are you using? They may monitor without you knowing.
Related
Hosting a rails web app on heroku; no recent code changes but about 2 days ago the application started reporting constant H31 misdirect errors. After looking into the documentation, since the application was still accessible I moved on.
The next day users from some of the subdomains could not access the application while others could. The application uses a wildcard certificate and we are behind a WAF. The first thing I tried was checking firewall logs and nothing was showing as blocked. I turned off the firewall and connected the domain directly to the application and still received the H31 stream, after 15 minutes of no change i re-enabled the firewall.
Reached out to the firewall and they said that their logs only showed upstream prematurely closed connection while reading response header
At this point they suggested the issue was most likely on the Heroku DNS servers, so I'm waiting for a response at this point.
Is there anything I can do in the heroku environment that would change this or am I stuck waiting for a response?
I am relatively new to the world of java. I am building a web application where I use Spring. So here's the case:
We have deployed the web app to our development server , and have it out in the open. This is how our network administrator explained it (don't really understand it but might be important for you):
55.555.55.5 is a NAT port to 77.77.77.77 ; 77.77.77.77 is an apache proxy server that makes a connection to 99.9.99.999.
We tell this server - 55.555.55.5 on http port to connect to 99.9.99.999 on port 8080 and give the client a connection on port 80 of 55.555.55.5; At the moment it is 1:1 connection...
And here is the problem:
On http://localhost:8080/myapp/ and on http://99.9.99.999:8080/myapp/ (our development server) everything works fine.
But on http://55.555.55.5:8080/myapp/ which is visible to the clients if I load the login page and right away login its ok, but if I wait like a couple of minutes on the page I get this:
HTTP Status 501 - Method email=something%40gmail.com&password=somethingGET is not implemented by this servlet for this URI
type Status report
description The server does not support the functionality needed to fulfill this request
Apache Tomcat/8.0.32
This is really strange and I don't know why it's happening?
Required Sinatra, got '/', did 'hello, world.', requested application root in browser and received nothing.
Literally the barest of bones Sinatra web application will not run as intended on my Mac, after previously working just fine. Page requests do not show up in the console.
I feel this may be due to force quitting an instance of a running application but after searching for a solution on the web I am at a loss and do not know how to rectify the issue.
edit:
require 'sinatra'
get '/' do
'Hello, World.'
end
Problem does persist after a restart
Definitely the correct URL (exactly as I've been working with all day). localhost:4567 as stated in the output when the application is run:
== Sinatra (v1.4.7) has taken the stage on 4567 for development with backup from Thin
Thin web server (v1.6.4 codename Gob Bluth)
Maximum connections set to 1024
Listening on localhost:4567, CTRL+C to stop
edit 2: scorched earth strategy; full reinstall with rvm fixed this issue.
I am getting this "nginx 504 gateway timeout" when accessing my website, even when low traffic, server is 1000mbit, 36GB RAM and 2(Intel Xeon 2556). All traffic going to my site comes through a proxy server (but this error occurs even when connecting directly to the server ip)
What could be the reason, and a possible solution to this?
Have you checked if the load time of your site (eg. php script) is bigger than the proxy timeout value?
Nginx simple say: "ok I've tried but not respond in time", maybe your webserver behind nginx have a service port, try to load the website with point to this port and you can understand what is the issue.
Summary
Sessions within my local IIS7.5 stop responding for no obvious reason.
Details
I'm developing ASP.NET 2.0 web applications using Visual Studio 2010 on a Windows 7 Ultimate 32-bit machine (which is a VMware instance running in VMware Workstation).
For no obvious reason, IIS just appears to stop working for the current session. If I restart the browser, it works... for a short time, and then stops again. If I open a different browser (while the first one is hanging) the new one works... for a short time.
Restarting IIS works (for a short time) or rebuilding the application (for a short time) - but there is absolutely no pattern to when it stops working... and it's driving me insane!!
There is no high-CPU-usage during this time, nor any high-memory-usage.
Nor does it not appear to be browser specific - I generally use FireFox for development, but this also happens on Chrome and IE. Nor is it just on the machine, but also when I test the website on old browsers running in other virtual instances.
I'm not sure when this started happening, so I am unable to say what (if anything) had changed at the time.
Can anybody suggest any reason why this might be happening?
UPDATE
This is now driving me insane - so I've been doing more investigation.
Here is a screen-shot of FireBug which is showing that the actual .aspx request is completing correctly, but for some reason IIS is simply not responding to the request for all the files within the page. The files are definitely there and have been served by IIS many, many times.
I have turned on the logs for IIS, and the only requests it has logged are those that show as successful in FireBug... those in red are missing.
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port c-ip sc-status sc-substatus sc-win32-status time-taken
2013-02-06 11:00:40 127.0.0.1 GET /default.aspx - 80 superuser 127.0.0.1 200 0 0 15
2013-02-06 11:00:40 127.0.0.1 GET /Org/Layout/Css/v0/FrontGeneral.css - 80 - 127.0.0.1 200 0 0 15
2013-02-06 11:00:40 127.0.0.1 GET /WebResource.axd d=IJ9YYVsWm9qkk8kUYcn2sYcQLbYErTn4We9MkwgF6JGUiPeoRWMmAKKsi_AbjNJQ-Je-l4D-1zuU66SBZi_kDHe1u7c1&t=634604425351482412 80 superuser 127.0.0.1 200 0 0 0
2013-02-06 11:00:40 127.0.0.1 GET /Scripts/v0/DefaultButtonFix.js - 80 - 127.0.0.1 304 0 0 0
I have also turned on the "Trace Failed Requests" (using information from here) but that is not producing anything... the directory is empty
Still testing this but have finally found success. Disabling my AVG virus scanner seems to clear this issue right up. If you have a virus scanner/security package dont bother adding exceptions, just blanket disable it temporarily and give it a go. You can add the exceptions back in if this test proves successful.
Know how you feel. This has been driving me nuts for weeks. I have been tweaking FF and Chrome settings with no effect whatsoever.
Best of luck...