Joe Van Dyk <[email protected]> wrote:
> On Fri, Aug 12, 2011 at 9:51 PM, Eric Wong <[email protected]> wrote:
> > Joe Van Dyk <[email protected]> wrote:
> >> On Thu, Aug 11, 2011 at 10:42 PM, Eric Wong <[email protected]> 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 - [email protected]
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
