It appears that part of the problem could be that when logger rolls over the mongrel log file. There is a mutex synchronization issue where the various mongrel instances all try to write to the new log file and block each other. This keeps them in a continual Application 500 Error state. Has anyone run into this problem? With log rotation turned off the problem does not appear.

- Jared Brown
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to