unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: nick@auger.net
To: "unicorn list" <mongrel-unicorn@rubyforge.org>
Subject: Re: A barrage of unexplained timeouts
Date: Tue, 20 Aug 2013 13:27:43 -0400 (EDT)	[thread overview]
Message-ID: <1377019663.33997248@apps.rackspace.com> (raw)
In-Reply-To: <20130820163745.GA22586@dcvr.yhbt.net>

"Eric Wong" <normalperson@yhbt.net> said:
> Can you take a look at the nginx error and access logs?  From what
> you're saying, there's a chance a request never even got to the Rails
> layer.  However, nginx should be logging failed/long-running requests to
> unicorn.

The nginx access logs show frequent 499 responses.  The error logs are filled with:

connect() failed (110: Connection timed out) while connecting to upstream
upstream timed out (110: Connection timed out) while reading response header from upstream

What specific pieces of information should I be looking for in the logs?

Thanks Again,

-Nick

_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2013-08-20 17:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 14:47 A barrage of unexplained timeouts nick
2013-08-20 16:37 ` Eric Wong
2013-08-20 17:27   ` nick [this message]
2013-08-20 17:40     ` Eric Wong
2013-08-20 18:11       ` nick
2013-08-20 18:49         ` Eric Wong
2013-08-20 20:03           ` nick
2013-08-20 20:42             ` Eric Wong
2013-08-20 21:19               ` nick
2013-08-20 21:32                 ` Eric Wong
2013-08-21 13:33                   ` nick
2013-08-22  2:32                     ` Jimmy Soho
2013-08-22  4:09                       ` Eric Wong
2013-08-22 13:10                         ` nick
2013-08-22 17:05                           ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1377019663.33997248@apps.rackspace.com \
    --to=nick@auger.net \
    --cc=mongrel-unicorn@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).