similar to: Mongrel hangs, consumes all CPU on shutdown

Hello, I''m running a Rails application which must sort and manipulate a lot of data which are loaded in memory. The Rails app runs on 2 mongrel processes. When I first load the app, both are 32Mb in memory. After some days, both are between 200Mb and 300Mb. My question is : is there some kind of garbage collector in Mongrel? I never see the two Mongrel processes memory footprint

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, I''m trying to use mongrel 0.3.13 with Rail 1.0 Believe it or not, on OS/X it works well for weeks at a time. On linux I''m getting Input/output errors after anything from a few hours to days, never more than a week. Once they start they don''t stop. The only pattern I''ve seen is that it always (seems) to happen while rendering an rhtml file.

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for

Hi, I''m sure I''m doing something dumb, but... I have an application that dynamically produces UTF8 encoded html exclusively. This application works using webrick without a problem. When using Mongrel 3.12.4 it looks as though the encoding is lost and garbage appears on the string. I suppose this could also be a double encoding, but personally, I can''t tell the

Hello, I''m running mongrel behind apache via proxypass. Every now and then, a spammer tries to proxy traffic through apache, and for some reason, apache forwards the request to mongrel, even though it''s not a site being hosted by me. At times this seems to cause mongrel to become unresponsive, and all requests to the site then fail with a proxy error until mongrel is

Hi guys, Does anyone know if mongrel has a built-in timeout for requests that take too long? If so, how do you increase it? I''ve found that some server requests are timing out. Complicated requests are already being farmed out to asynchronous processes. But some of the more basic requests are timing out when we have our peak server load in the mornings (the bottleneck is the

Are there any XML databinding frameworks available for Ruby / Rails, such as Castor or JaXB for Java? Also are there framework such as Apache Axis for WebServices for Rails or Ruby? Regards, Harm de Laat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060310/3cf0cfd3/attachment.html

Skipped content of type multipart/related-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://wrath.rubyonrails.org/pipermail/rails/attachments/20060525/eac5b0af/attachment.bin

After reading the digital shortcut and the documentation on the web site I''m confused. Which one should I use? pen, balance or nginx ? I don''t want to use a behemoth like appache and ssl is not needed so it reduces my choice to those three only.... What are the pros and cons of each? I don''t have much money, so the less ressources I use the better it is for me.... As

I have a magical proposal for the anti-magic web framework. Controller methods do not use arguments and yet expect arguments. This is handled through this params hash because we don''t know in advance what parameters a client could pass to Merb. But in almost every instance, it is too much to know all the query parameters - one doesn''t care if the user threw in an extraneous

Hi, was wondering if anyone else had a similar problem and knows why or a solution. basically my mongrels seems to work fine. i am running three clusters all which are monitored by monit. monit has the ability to restart a mongrel if it doesn''t pass a port connection test. so the problem is that after some time. aprox. 6hrs. to 20hrs. after clusters are started, the mongrels get

Hi, I''ve listened in to this mail list for quite a while now but not doing anything with Ferret until I was ready to incorporate it. I''ve used Lucene for years, but not Ferret. I downloaded and installed the ''bleeding edge'' version (lets call it 0.10.9.1). There appears to be a significant re-working of the API happening. It all looks good. But there

Has anyone ever experienced this problem? Every 12-24 hours *one of* my mongrel processes gets a TERM signal and quits. There is all I get in my mongrel log.. ** Mongrel available at 0.0.0.0:8003 ** TERM signal received. And my rails-log is silent too. No request starting. Just the end of a successful request and then nothingness. The other processes are doing just fine and stay up for good.

Hello, I am running mongrel 1.1 in production mode behind a lighttpd with mod_proxy. At first everything works fine, however, after a few days, the mongrel servers stop answering at all, even if I try to connect to them directly. I have checked logs but there is no sign of anything at all, and even when there was not a single request for a few days, it did freeze, and that on repeated occasions.

All, In the production log I have entries like: Processing OpportunityController#new (for 68.213.19.251 at 2006-05-11 10:18:36) [GET] Session ID: 345b455a2a36af8814081c388d8726f1 Parameters: {"action"=>"new", "controller"=>"opportunity"} Rendering within layouts/opportunity Rendering opportunity/new Completed in 0.02281 (43 reqs/sec) |

Hi, I''m using backgroundrb 0.2.1 in a production environment and for most parts I''m very happy. We are using it to do some heavy video editing on the server side and it works great except that under, what seems heavy load the below problem happens intermittently. The problem has only happened 5 times out of over 500 runs by our backgroundrb worker. This is the code in our

Morning Folks, As most of you know there were a few people who had the following three bugs: * CLOSE_WAIT: Lots of sockets in CLOSE_WAIT state. * 99% CPU: Mongrel''s getting "stuck" pegged at 99% CPU. * LEAK: Memory leak. I''ve successfully fixed these bugs or attributed them to one main cause: pstore. First, the memory leak was because of a bug in how the GC in Ruby

I really like the idea of using Mongrel. But reading the FAQ, I noticed something that might be an issue. It stated: "Ruby on Rails is not thread safe so there is a synchronized block around the calls to Dispatcher.dispatch. This means that everything is threaded right before and right after Rails runs. While Rails is running there is only one controller in operation at a time." So

Anybody seen this message before? I see it over and over in one of my mongrel processes log files. I''ve never seen it before today. /usr/local/bin/mongrel_rails:16Mon May 14 20:44:30 +0000 2007: Error calling Dispatcher.dispatch #<Mongrel::TimeoutError: Mongrel timed out this thread: shutdown>Thread #<Thread:0x2ae6288dbc40 sleep> is too old, killing. Thanks, Pete