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 am suspicious that all cannot be well on this setup as monit will send dozens of messages a day, and occasionally hundreds of messages. The worst day was 1400 alerts. Yes, 1400. The bulk comes from there being 3 clusters (staging, beta, production), and 10 mongrels per cluster, and two servers. So, we can reduce the total quantity by these factors, I get that part, but still, there's an aweful lot of "this stopped" and "that does not exist" even factoring the redundancy out. I don't understand the implications of what each of these means. Mongrel keep crashing? Rails crashing? Monit crashing? Thanks for any clues you can offer. Sample messages I get are: -- (A)---------------------------------- Monit instance changed Service [domain snipped] Date: Tue, 08 Jan 2008 14:41:50 -0800 Action: alert Host: [domain snipped] Description: Monit stopped -- (B)---------------------------------- Does not exist Service mongrel-production-8300 Date: Tue, 08 Jan 2008 15:30:04 -0800 Action: restart Host: [domain snipped] Description: 'mongrel-production-8300' process is not running -- (C)---------------------------------- Execution failed Service mongrel-production-8301 Date: Tue, 08 Jan 2008 15:30:34 -0800 Action: alert Host: [domain snipped] Description: 'mongrel-production-8301' failed to start -- Posted via http://www.ruby-forum.com/. _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
