Mongrel returns Status: 500 Internal Server Error

December 17, 2006

This one stumped me for almost a week now.

SYMPTOM:
Late in the evening all instances of mongrel but one would return a Status: 500 Internal Server Error. One instance would still work fine, strange enough it was always the second instance started that would still be alive. If you ran one instance it was fine. The error would present itself only in a mongrel clustered environment.

Thanks to Eden on the mongrel mailing list, the solution was found:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/218107

SOLUTION:
DO NOT allow the ruby logger to rotate itself in a clustered environment. Have some other external program manage the logs for you.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: