Passenger with Ruby Enterprise in Production Take 1
Well Passenger had been running on this VPS nicely so why not try it out on a larger site? My server could use a nice decrease in memory usage, simpler Apache config files, and better concurrency.
Using the 06242008 release of Ruby Enterprise and Passenger 2.0.1 I converted over a site with 8 Mongrels that's been running very steady for almost a year now.
Everything seemed to be going well enough for about a day and a half and then while finishing dinner Saturday night I get an alert message that Apache has crapped out. Getting back in front of a computer I see that the load on the box is fine, but Apache logged an error saying that it reached its MaxClients. Considering I have that set to 400, anything over 256 requires some custom tuning, this was surprising.
Apache had been restarted automatically by monit, but that's not what I wanted on a production box. So it's a quick switch back to Mongrel for now!
See the chart below that illustrates the Apache crap-out.
Search Google for mod_rails passenger ruby enterprise ruby-ee
June 30th, 2008
Leave a Reply