Thanks for the tips. I've been using god, but when one of the Mongrels gets into this unresponsive state a standard mongrel_rails cluster::restart on the port in question fails to restart the process. I have to shell in and issue a kill with -6 or -9. I can't rely on a restart condition on CPU usage, as usage remains within normal bounds right up until it jumps to 100% and jams.
I've also run strace on the process. While I'm not exactly sure how to interpret it, I'm not seeing any obvious errors (system calls returning -1 for instance.) Naturally this is one of the times when it runs fine for hours, but I'll pastie what I find when it happens next. Any general pointers on what sort of things I should be looking for in there? Thanks, Josh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
