# Mongrel failures but nothing in logs

**URL:** <https://www.ruby-forum.com/t/mongrel-failures-but-nothing-in-logs/195534>\
**Category:** Rails\
**Created:** [September 24, 2010, 5:20pm UTC](https://www.ruby-forum.com/t/mongrel-failures-but-nothing-in-logs/195534 "2010-09-24T17:20:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohits](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/bbe5ce/32.png) [@mohits](https://www.ruby-forum.com/u/mohits)\
**Post date:** [September 24, 2010, 5:20pm UTC](https://www.ruby-forum.com/t/mongrel-failures-but-nothing-in-logs/195534/1 "2010-09-24T17:20:04Z")

</div>

Hi All,

We are having a few strange problems in production.

The Rails 2.3/ Ruby 1.8.6 application is hosted using Apache/ mod\_proxy/  
mongrel\_cluster (managed by monit) running on CentOS. This connects to  
a PostgreSQL instance running on a Windows 2003 server (it’s behind a  
load balancer but the PostgreSQL port is redirected to one machine.

Suddenly, without reason or upgrade, the Rails app is returning 500 and  
nothing is in the Rails log - not in the mongrel logs, not in the  
production log. We seem to be able to safely connect to a static image  
file - so, it should not be the Apache, we think.

We checked a few things:

- mongrel has the rights to folders like tmp and log
- the disk can be written to

Since nothing is in the logs, we are baffled - what could we check?

Thanks,  
Mohit.