search for: delaurentis

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 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

Hi guys, I''ve been chasing a problem in my web-stack: Lighttpd -> Mongrel -> Rails, and found a problem with the interaction of Lighttpd and Mongrel. If a request takes more than 5 seconds, Lighty will retry it - and then the requests / responses get mixed up in Lighty and it returns a bad response to the client. Not good. I''m convinced that the problem is

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

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

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

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

Hi guys, I''m looking for a way to pass environment variables to my Rails app via Mongrel. I want to conditionally execute code in environment.rb based on these environment variables. Background: 1. I have some special stuff I want to do when my Rails app first starts 2. So, stuff it in environment.rb in after_initialize, right? 3. Not this time. I have several other background

I''m trying to sent a file to the iphone (which requires byte-range request support) using the rails send_file method. However, this fails, I think because of mongrel. I think so because if I send the iphone a file handled by nginx, it plays it fine. But then when I serve the file with rails the iphone can''t play it. Any ideas? Alex

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, I''m doing development with Mongrel 1.0.1 on Ruby 1.8.4 / OS X 10.4.10, and I''ve found that often when I shut down my server with ^C, it hangs for a while, gobbling up all CPU. Sometimes it stops after a few seconds, sometimes it''s run for several minutes at least. This happens across all the apps I develop on, but it seems to hang longer after

Hi I posted this to the Ruby on Rails Talk group but I thought I''d post it here too as it''s probably a more appropriate group. Hope this is ok. I''m running a 2-instance Mongrel cluster behind Apache 2.2.4 with Rails 1.2.3. If no requests are received by the application for several hours (this usually happens overnight) then Mongrel stops responding and no requests are

> We see this on all of our Mac''s here as well. We''ve tried it with > different versions of Ruby (1.8.4, 1.8.5, and 18.6), and the problem > happens with all of them. > We run macs w/ compiled adaptors on local mysql instances and there are no issues. F -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I just upgraded to Ruby 1.8.6 on my Mac development machine and here''s what I''m seeing when I try to run mongrel (I have the latest version of mongrel + fastthread installed). It seems to be an OS/X thing, because this same combo works fine on our Linux server. Here''s the error, have you guys seen anything like this?: ** Starting Mongrel listening at

...gt; file, :action => upload. Well, the route turned this into "/upload/xxxxxxx", and this didn''t match the path_info "/file/upload". Once I removed the route, the problem was fixed and progress started coming through. -Pete On Feb 22, 2007, at 8:04 AM, Pete DeLaurentis wrote: > Hi guys, > > I''m using mongrel_upload_progress and experiencing an error similar > to what another user hit on the list on Jan 19th. > > For this test, I''m running one mongrel: > > mongrel_rails start -p 3000 -S config/mongrel_upload_progress.c...

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.

At 03:24 PM 11/7/2007, mongrel-users-request at rubyforge.org wrote: > > Thanks for this Kirk. Yep, I was using 14400. I''m switching this > to > > 2 weeks: 1209600 and we''ll see if any further restarts are needed > by > > monit. > >I''ve always wondered why 14400 is the number that is always passed >around when talking about extending

Hello all... I know its been a while since the last one, but a new prerelease is available with a gratuitous increase in version numbers! gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ This one has some new features in it that need to be tested on all unix platforms. Please run --clean and cluster::status on every *nix you can find. I run linux so the rest are up

So here''s a random question: if a (Ruby) multi-threaded rails server could exist (bug free), would it be faster than using a mongrel cluster? (I.e. 10 mongrel processes versus 10 Ruby threads). I''m not sure if it would. RAM it might save, though. Any thoughts? -Roger -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi guys, I had mongrel_upload_progress working very sweetly on my dev machine, where mongrel was acting directly as the webserver. But when I went to production it stopped working. The Problem: On our production server we use Lighttpd, and it looks like lighty is buffering the whole upload and then giving it to Mongrel in a big chunk. This pretty much screws up the whole point of