On 30 Nov 2012, at 20:26, Eric Wong wrote: >> Nginx logged: >> >> x.xxx.xx.xx - - [27/Nov/2012:14:40:28 +0000] "POST /clients/2248 >> HTTP/1.1" 499 0 "https://example.com/clients/2248/edit"; "Mozilla/5.0 >> (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)" >> x.xxx.xx.xx - - [27/Nov/2012:14:40:29 +0000] "POST /clients/2248 >> HTTP/1.1" 404 592 "https://example.com/companies/2248/edit"; "Mozilla/5.0 >> (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)" >> >> You can see the first request was terminated by the user. Hot on its >> heels the user tried again and got a 404. > > Weird, and this is the only nginx instance that saw this request?
That's right, I only run a single nginx worker process. > Also, according to your logs above, the two requests above came from > different Referer pages, so perhaps there were more requests involved > that hit a different nginx? Bizarre as it sounds, that was a copy-paste mistake on my part. The second referrer should read: "https://example.com/clients/2248/edit";. > Odd. It's been a long time since I looked at Rails; but doesn't Rails > log when a request _starts_? Also, doesn't Rails log all DB queries? I think Rails logs when a request starts, then logs some more when the request ends – but I'm not certain and I couldn't find the answer when I looked in the Rails source. It must be there somewhere. Rails doesn't log the DB queries in production, at least not by default. > Or, by any chance, do you have query logging enabled in your DB to track > this down? Regrettably not. It's a weird problem which I'd like to dismiss, but it's happened on two occasions now. I'm running an old version of Rails (3.0.12) which may or may not be relevant. Hmm. _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
