similar to: Memory Leaks with Rails 1.2?

Hi, I have mongrel 0.3.14, with ruby 1.8.5, rails 1.1.6 and mongrel cluster 0.2.1, on debian sage 3.1 with apache 2.0, and fastthread 0.6.1. I am load balancing 3 mongrel processes using the random port trick. When I start mongrel the processes have about 60MB, but after some hour of usage the memory ballons upto more than 180MB and the site becomes terribly slow. Forcing me to restart mongrel

Hi, Are there any recommendations as to what is currently the most stable setup is for mongrel & apache? I read somewhere (probably here) that you should avoid using PStore for sessions. Are there any more of such recommendations? Also, what is currently the safest version of mongrel to use in production? Jeroen

Time for some all time pimpage folks. Me and Matt Pelletier wrote a small PDF book on Mongrel entitled: "Mongrel: Serving, Deploying, and Extending Your Ruby Applications" since we really wanted you to know what it was about. It''s published by Addison Wesley Professional, has just over 100 pages of goodness, and is available for $14.99 at: http://safari.oreilly.com/0321483502

Hi. I''m a fairly new mongrel user and have a scenario that I wanted to run by you all, see if anyone''s synapses connect -- mine def. aren''t! I''m running a fairly simple rails app through a mongrel cluster (2 mongrels). This site is consistently sloooow -- memory on the server is regularly paging (and shouldn''t be). ssh-ing in and running top shows

What''s a rule of thumb for guesstimating how many Mongrels to use in a cluster for an app? I have an app that gets about 5000 unique visitors per day. I figured I''d give it plenty of Mongrels -- twenty to be specific. After running out of memory and hitting the swap periodically, I scaled it back to five and it still seems to serve up visitors fine. So, is there some super-secret

I know that Zed has made mention of the fact that using RMagick with mongrel and rails is a bad thing. I''m currently using FlexImage (which in turn uses RMagick) on my application and really haven''t had too many problems. We get a restart for memory usage every 8-10 hours on one mongrel of twelve running, but I''m not sure if that''s an RMagick issue. Either way,

We have a site that is running Mongrel and is down. Below is the Mongrel log file information. The server is a Linux server with 2gb of RAM. EV1 (hosting site) says that since this is a Linux server that the RAM is cached and that there is plenty of free memory available. Can anyone make sense of this error and have some suggestion of options that I may take to correct this issue and get

Hi all, My environment is ruby-1.8.4, rails 1.2.2, mongrel 1.0.1, linux 2.6. Now, i have a problem on memory leaks with mongrel. My site is running 5 mongrel processes on a 2G RAM machine, the memory of each process grows from about 20M to about 250M, but it never recover to the initial 20M, so i had to restart the mongrel processes once per day. The load is about 1M hits per day. Waiting for

Hi One of the two mongrel processes has died in the middle of the night four times in the past 9 days, and I need help debugging this. Each time the symptoms are the same: * Each time I can restart the process via cap -a restart_app. * Before the restart, there is nothing unusual in production.log or mongrel.log. * During the restart, about 100 repetitions of an error message are generated in

Calling All Mongrel Minions! I wanna have some fun and would like this as a Christmas present. The site http://www.workingwithrails.com/ has this lame popularity system that''s kind of irking some of the main Ruby contributors. I think it''s kind of funny, but would like to demonstrate what an army of motivated people can do to these kinds of popularity contests. So, as a

I see that Brian McCallister did some benchmarks recently, showing Apache, Mongrel, Jetty and TwisteWeb: http://kasparov.skife.org/blog/src/ruby/silly-micro-benchmarks.html Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received

Hi guys, I''ve been running mongrel for a while now with Ruby 1.8.4, and last week upgraded to 1.8.6. Since upgrading, each morning when I wake up there''s a big problem: 1. Accessing the site returns a "500 Internal Server Error" 2. All the mongrel_rails processes are still running, but none of them are active (when I run top) 3. Lighttpd and pound are still

Hi ! My mongrel just starting spitting out these nice lines: The error occured while evaluating nil.accept. TELL ZED HE''S A MORON. !!!!!! UNHANDLED EXCEPTION! You have a nil object when you didn''t expect it! Not sure what happened or why, but just FYI: Zed, you are a moron :-) Happy holidays! Gitte Wange

Hi We''re running mongrel on CentOS 4.2 with Apache httpd 2.2 mod_proxy_balancer, mongrel_cluster-0.2.0, Rails 1.1.6, Ruby 1.8.4, Pg 8.1.4 backend. We are on the verge of going live with our site and I am stress testing the server. What we are seeing is under heavy loads, our mongrels will seg fault and die one by one. Following the advice in a previous thread (http://www.mail-

Hi folks, I took a break from Mongrel today and instead whipped up an Atom feed generator for my site. People who love or utterly hate my essays will lover or utterly hate to subscribe to it. http://www.zedshaw.com/feed.atom Let me know if it isn''t working well in your favorite feed reader. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/

Hi, Thanks Zed - this is very interesting. One item in particular caught my eye: Does anyone on this list have any comments or validation that Rails 1.2.1 is 2-4 times as slow as Rails 1.1.6? Topfunky provided a link that purports what looks like really horrible performance and memory characteristics for Rails 1.2.1, even v. 1.1.6:

Hi everybody, I just suscribe to the list because I have a problem using mongrel and mongrel_cluster... I setup a server (debian unstable wich provide apache 2.2.3 as a pakage) but I have an error when I try to access my application : ERROR 403 : Forbidden, You don''t have permission to access / on this server. When I check apache''s logs I found that : [warn] proxy: No

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

I''ve been trying to track down the culprit of erratic behaviour and crashes on my production server (which is split into a number of Xen instances), so set up a staging server so that I could really try to get to the bottom of it. The staging server (also split with Xen) is set up pretty much identically as far as the mongrel_cluster server is concerned (the production box has two

Hey guys, I''m running the mongrel server that comes with rails-1.2rc1 for development on a winxp box, anticipating taking it into production on a win2k3 box in the next few weeks. I''ve had a couple of crashes occur during development that give me pause, however. I made a ticket for the last one here: http://dev.rubyonrails.org/ticket/6841 I know, or at least believe, that