[Mongrel] Early morning strange error saying: Status: 500 Internal Server Error
eden.li at gmail.com
Sat Dec 16 06:39:29 EST 2006
How are you handling log rotation? I was encountering really strange,
non-logged 500 errors every week because I used some bad log rotation
advice from the Rails wiki. I don't have the link handy since it
seems the wiki is down right now, but I found this thread:
The jist: Don't let Logger rotate the log.
Instead, let Rails log as much as it wants to into production.log and
rely on some out-of-process log rotation daemon (eg, logrotate). Or,
switch to some ruby-based logging solution that works when more than
one process tries to rotate the same log file. I personally use the
On 12/15/06, Matthew Whittaker <mwhitt89 at gmail.com> wrote:
> So I have updated to the latest mongrel and fastthread and my
> environment is as follows:
> Debian 3.1
> Rails 1.1.6
> Ruby 1.8.5
> Mongrel 0.3.18
> Fastthread 0.4
> Mongrel Cluster 0.2.1
> Apache 2.2.3
> I again woke up this morning to my disappointment of seeing the
> strange Status: 500 Internal Server error. It happens the same every
> morning, I have three mongrels running, two give the error, one
> processes the request successfully.
> This error is not being reported in ANY logs. Apache, Mongrel debug,
> rails, nothing. The only thing I notice while tailing the logs is
> that the request reaches mongrel and is reported in both rails.log
> and threads.log, however the request is NOT being reported in ruby /
> rails production.log. This appears to be craping out in mongrel.
> Again this only happens overnight when there is no activity with the
> site. PLEASE HELP. Is there any way to take a core dump of mongrel?
> How can I get more logs to see what is happening.
> Matt Whittaker
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
More information about the Mongrel-users