From: Pierre <oct@fotopedia.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Unicorn and HAProxy, 500 Internal errors after checks
Date: Wed, 1 Dec 2010 12:59:31 +0100 [thread overview]
Message-ID: <AANLkTim=DQ7qKBK-r6WKW5P4kvjm8neELKA0BQ-xB6UL@mail.gmail.com> (raw)
Hi,
This morning, while checking for a correct deployment, we found out
that the Unicorns we are using were sending 500 Internal errors very
frequently to the HAProxy that sits in front of them. After some
investigation, It turned out that HAProxy checks the backend by
opening and closing a connection to the unicorn. Unfortunately the
Unicorns we use ( v 0.990.0 ) will try to reply to this probe by a
500, resulting in the error being sent to the HAProxy when the proxy
has already close the connection. I think Unicorn should refrain from
sending an error in this case. There is no visible side effect,
excepted that there are a "lot" of 500s running on the wire that
nobody will ever read. Also, these errors are not sent in the Unicorn
log, making it quite difficult to understand what's going on :-)
Cheers,
--
Pierre <oct@fotopedia.com>
Server Shepherd at http://www.fotopedia.com/
_______________________________________________
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
next reply other threads:[~2010-12-01 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 11:59 Pierre [this message]
2010-12-01 16:12 ` Unicorn and HAProxy, 500 Internal errors after checks Clifton King
2010-12-01 17:02 ` Pierre
2010-12-01 16:52 ` Eric Wong
2010-12-01 17:14 ` Pierre
2010-12-01 19:58 ` Eric Wong
2010-12-02 0:42 ` Lawrence Pit
2010-12-02 4:59 ` Eric Wong
2010-12-02 8:38 ` Pierre
2010-12-02 17:39 ` Eric Wong
2010-12-03 8:41 ` Pierre
2010-12-04 23:38 ` Eric Wong
2010-12-05 1:04 ` russell muetzelfeldt
2010-12-06 18:39 ` Eric Wong
2010-12-02 17:41 ` 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='AANLkTim=DQ7qKBK-r6WKW5P4kvjm8neELKA0BQ-xB6UL@mail.gmail.com' \
--to=oct@fotopedia.com \
--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).