Forum: Ruby on Rails Mongrel cluster died only in production environment

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
9dea97e0df502124073cad2a48cf5e1a?d=identicon&s=25 Phil K. (pkulak)
on 2007-03-05 22:35
I'm new to setting up a production server with Rails, so I tried to do
what seems to be the standard setup right now: a couple mongrel servers
behind Apache 2.2. I've got a test page that refreshes itself every
couple of seconds, and I've noticed that I get a "Proxy Error" when
that's run for about a minute or so, from what appears to be a mongrel
server dieing a horrible death. If I refresh, the other one will shortly
follow, forcing me to manually start the cluster again.

The odd thing, is that everything runs flawlessly if I'm in
"development" in my mongrel_cluster.yml file. My setup is totally
standard, so I was hoping that someone would know what the difference
between these two environments could be that is actually killing the
server. Thanks for any help!
9dea97e0df502124073cad2a48cf5e1a?d=identicon&s=25 Phil K. (pkulak)
on 2007-03-05 23:34
Okay, nevermind, I figured it out. It looks like an uncaught exception
crashes Mongrel when it's in production. Odd... Oh well, I can live with
it.
This topic is locked and can not be replied to.