At Wed, 9 Jan 2008 01:58:58 +0100, Greg Willits <[EMAIL PROTECTED]> wrote: > > Monit 4.9, Mongrel 1.0.1, Rails 1.2.6, Mac OS X 10.4.11 (PPC) > > I don't know whether this is a mongrel issue or a monit issue. > > I'm trying to poke my way around a system set up by someone else. I have > no more experience w/ mongrel that local Rails dev at this point, and a > conceptual understanding of how monit is working. I have the Deploying > Rails beta book, and I'm muddling my way thru mongrel and monit docs, > but I think some hints as to direction would be useful. > > […]
I have seen a similar situation here. What happened was (more or less, this is from memory) a mongrel instance would be locked up on an HTTP response that would take a long time to complete. Because requests would just queue up behind this one, monit would fail to get a response in a reasonable time, would assume that the process was non-responsive and try to restart it gracefully (using mongrel_rails stop). Mongrel would take a long time to shut down because it was still processing that long running response, so we would get a message that monit couldn't shut it down and it would fail to start (or something like that). Finally the long running rails process would complete, mongrel would restart, and monit would let us know that the process was back up. The solution was to make sure that responses come back in a reasonable amount of time. best, Erik Hetzner ;; Erik Hetzner, California Digital Library ;; gnupg key id: 1024D/01DB07E3
pgpPcVYO0ADIM.pgp
Description: PGP signature
_______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
