# Mongrel cluster died only in production environment

**URL:** <https://www.ruby-forum.com/t/mongrel-cluster-died-only-in-production-environment/87776>\
**Category:** Rails\
**Created:** [March 5, 2007, 10:35pm UTC](https://www.ruby-forum.com/t/mongrel-cluster-died-only-in-production-environment/87776 "2007-03-05T22:35:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pkulak](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/a5b964/32.png) [@pkulak](https://www.ruby-forum.com/u/pkulak)\
**Post date:** [March 5, 2007, 10:35pm UTC](https://www.ruby-forum.com/t/mongrel-cluster-died-only-in-production-environment/87776/1 "2007-03-05T22:35:13Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![pkulak](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/a5b964/32.png) [@pkulak](https://www.ruby-forum.com/u/pkulak)\
**Post date:** [March 5, 2007, 11:34pm UTC](https://www.ruby-forum.com/t/mongrel-cluster-died-only-in-production-environment/87776/2 "2007-03-05T23:34:15Z")

</div>

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.