From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Cc: Joe Van Dyk <joe@tanga.com>
Subject: Re: Rack content-length Rack::Lint::LintErrors errors with unicorn
Date: Sat, 13 Aug 2011 08:17:03 +0000 [thread overview]
Message-ID: <20110813081703.GA13967@dcvr.yhbt.net> (raw)
In-Reply-To: <CACfv+pLWivs2KoBT-nKMdYS5+i2vvBxRKS_B-X-a_aeF_huCng@mail.gmail.com>
Joe Van Dyk <joe@tanga.com> wrote:
> On Fri, Aug 12, 2011 at 9:51 PM, Eric Wong <normalperson@yhbt.net> wrote:
> > Joe Van Dyk <joe@tanga.com> wrote:
> >> On Thu, Aug 11, 2011 at 10:42 PM, Eric Wong <normalperson@yhbt.net> wrote:
> >> > What web framework and other middlewares are you running? Are you using Rack::Head to
> >> > generate HEAD responses or something else?
> >>
> >> Does unicorn use Rack::Lint by default? What about Rack::ShowBacktrace?
> >
> > Yes with RACK_ENV=development, it loads Rack::CommonLogger,
> > Rack::ShowExceptions and Rack::Lint. This stack should match what
> > "rackup" loads in development.
>
> Hm -- RACK_ENV is set to 'production'. I don't see Rack::Lint or
> Rack::ShowExceptions when I do 'rake middleware' on the servers that
> exhibit the bug.
"rake middleware" won't show what the Rack server (Unicorn in this case)
loads automatically. If you can, share what "rake middleware" shows[1]
Also, are you sure it's RACK_ENV or could it be RAILS_ENV? If you're
sure it's RACK_ENV=production, then there's no way it should load
Rack::Lint behind your back...
Can you share your command-line for launching unicorn?
Are you using "unicorn" or "unicorn_rails"? The latter was designed for
Rails 1/2.x, the former may work better with Rails 3 but really both
should work...
[1] Ideally, you'd be able to share the full source +
configs of your app, but I'm not going to push you to violate NDAs
and such. If you can put up an isolated test case that reproduces
this problem reliably, that'd be awesome, too.
--
Eric Wong
_______________________________________________
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 prev parent reply other threads:[~2011-08-13 8:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 4:39 Rack content-length Rack::Lint::LintErrors errors with unicorn Joe Van Dyk
2011-08-12 5:42 ` Eric Wong
2011-08-12 18:09 ` Joe Van Dyk
2011-08-12 19:22 ` Joe Van Dyk
2011-08-12 22:36 ` Eric Wong
2011-08-13 4:09 ` Joe Van Dyk
2011-08-13 4:51 ` Eric Wong
2011-08-13 7:24 ` Joe Van Dyk
2011-08-13 8:29 ` Eric Wong
2011-08-13 7:29 ` Joe Van Dyk
2011-08-13 8:17 ` Eric Wong [this message]
2011-08-22 20:13 ` Joe Van Dyk
2011-08-22 20:38 ` Eric Wong
2011-08-23 18:22 ` Joe Van Dyk
2011-08-23 18:29 ` Joe Van Dyk
2011-08-23 19:54 ` Joe Van Dyk
2011-08-23 20:00 ` 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=20110813081703.GA13967@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=joe@tanga.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).