Thanks for the ideas so far. I'll look into the latest monit. Message (A) is starting to look like a monit crash to me. It is always followed by a bunch of similar messages that monit maybe stopping/starting all the mongrels.
looks like the logs have little or no date/time stamps, so they're semi-useless in trying to correlate to the email alerts. I do have some requests that can take a while to process (depends on response time from external services), so that's a valid lead. Evan Weaver wrote: > Make sure your Monit check interval (not sure abou the default) is > greater than your Mongrel request timeout interval (default 60 > seconds). I have looked everywhere I can think of, and I don't see any mention of this timeout value anywhere in Mongrel docs. This page (http://mongrel.rubyforge.org/docs/howto.html) mentions a -t (timeout), but the description doesn't match what you're referring to. It looks like a delay between the end of responding to request A and starting to handle request B, not when to give up on A. I guess I'll assume the 60 secs, and play with monit accordingly. -- gw -- Posted via http://www.ruby-forum.com/. _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
