Hi. I'm deploying a Rails app via a mongrel cluster. I have some confusion about logging in a mongrel environment.
Some of my mongrels seem to be dying unexpectedly. The .pid file is still there, but the process isn't. However, when I look at the mongrel.pid.log file for a mongrel that is no longer running--there's nothing there to indicate why it died. I'm confused as to what output ends up in the mongrel.pid.log vs what ends up in production.log? Can anyone clear up how this works? When I look at the production.log -- I'm not sure if there's anything there to indicate why the mongrel died. There's a whole lot of cruft in the production log! In particular, there seem to be entries for every single HTTP request, along with timing numbers. Is this actually useful to have? Is there any way to turn that kind of logging off? Do I want to? My own logger.info(message) or logger.debug(message) seem to be in production.log too, instead of the mongrel.pid.log. That's to be expected? I sort of expected that logger.info wouldn't be output in a production environment at all! And Rails-produced error messages and deprecation warnings seem to end up in the mongrel.pid.log--why do my own log messages end up in production.log instead? What controls what goes where? Are there ways to fine-tune this more usefully? And in addition to my logging questions, does anyone have any idea why my mongrels might be silently dying? Thanks for any advice, Jonathan -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
