[Rails] Re: Dealing with Application error (Rails) in production

Brian Hogan
Mon, 03 Apr 2006 21:35:57 -0000

I''m only posting this so the next person who has this error will see
it...
Whenever you see this error, modify your database.yml file so that your
development and production databases are the same and then launch your app
with WEBrick in Development mode. This will rule out your Rails app as the
problem so you can then look at the OS / webserver / database.


On 4/3/06, Peter Gibbons <pgibbons@initech.lan>
wrote:
>
> Dan Croak wrote:
> > Kent Sibilev wrote:
> >> Look in the log file, I presume.
> >>
> >> Kent.
> >
> > Thanks, Kent.  I looked in the production.log file and found this
> > particular error:
> >
> > Errno::EPIPE (Broken pipe)
> >
> > Any idea what that is about?
> >
> > I started seeing the error when I switched over from Apache to a
> > lighttpd web server .
>
> If you look at the unreleased changelog for Lighttpd, it shows that it
> fixes a fastcgi problem.  The unreleased fixes in Lighttpd also include
> connections not getting closed on certain errors, and memory leaks.
>
> Try compiling the Lighttpd version in the repository, or wait until
> 1.4.12 is released.  Or use Apache 2.0.55 with mod_fcgid-1.08 (not
> mod_fastcgi!).
>
> You can see the changesets at
>
> http://trac.lighttpd.net/trac/timeline?changeset=on&update=Update
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
-------------- next part --------------
An HTML attachment was scrubbed...