similar to: Mongrel Logging

I just got the fire to clean up how our app is deployed and upgrading mongrel. Currently, our app is being deployed in a user''s home directory. This has caused some problems regards to user/group permissions... We decided we were going to move everything to /var/www/app which led me to the whole general layout of our deployment and some questions. ENV Ruby 1.8.5p12 Rails 1.2.3 Mongrel

I just created a test rails app, and am having very wierd issues with mongrel cluster. Here''s what I''m doing: rails test sudo chown -R mongrel:mongrel test cd test sudo mongrel_rails \ cluster::configure -e production \ -p 8000 -N 3 -a 127.0.0.1 --user mongrel \ --group mongrel It correctly writes the mongrel_cluster.yml file to the config directory. Now,

I was hoping that someone can help me with this, which have been driving me nuts -- I have had my mongrel cluster dying daily. And yes, I have gone through the check list of possible causes: I don''t do log rotating I use active_record for session storage I don''t use SQLite and Berkeley DB The MySQL timeout is set to 3600 I am using only 10% of the memory. I am using RedHat

Hi. I have mongrel 1.0.1 running a really simple application and found to lock up (rarely, but still). There''s nothing in the logs, it just stops responding. When I mongrel_rails stop it, I get lots of entries like: Waiting for 3 requests to finish, could take 60 seconds /usr/lib64/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:675:in `process''

Thanks for the help Sean. I managed to get the install fixed, but I''m still having problems. When I do mongrel_rails start, the process just gets stuck and never completes. If I interrupt it I get the following... ** Ruby version is not up-to-date; loading cgi_multipart_eof_fix /usr/lib/ruby/1.8/rubygems/source_index.rb:186:in `search'': Interrupt from

First off: Our clusters are LVS balanced Apache 2.2.3 + mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a pgcluster backend. On 2 of our deployed clusters, we are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it

This might just have affected my particular setup but thought it might be worth noting for others. >gem -v 0.9.2 >gem list --local cgi_multipart_eof_fix (1.0.0) Fix an exploitable bug in CGI multipart parsing which affects Ruby <= 1.8.5. mongrel (1.0.1, 1.0, 0.3.20, 0.3.18, 0.3.13.4) A small fast HTTP library and server that runs Rails, Camping, Nitro and Iowa apps.

Sorry if this is the wrong place to ask, but when I run mongrel evented using swiftiply and then send it the USR2 signal to restart it, it dies. Without eventing, USR2 restarts mongrel as expected. Anyone else seen this? Here''s a dump: $ EVENT=1 mongrel_rails start -d -P /tmp/m.pid -p 4321 Using Evented Mongrel ** Ruby version is up-to-date; cgi_multipart_eof_fix was not loaded $ kill

Hi all, I''m getting a strange, intermittent Thread deadlock in production: deadlock 0x2a988d7008: sleep:F(3) - /opt/ruby/default/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723 CPU usage spikes to a full core and Apache 502''s on requests that got handed to that particular listener each time. I tried attaching with gdb, and gdb twisted itself into a knot. Anyone have

hi. apologies if this has been asked before... my configs: ruby -v 1.8.5 mongrel 1.0.1 rails 1.2.3 i do a mongrel_rails start -e production -p 4000 -d it''ll say: ''** Ruby version is not up-to-date; loading cgi_multipart_eof_fix'' but that shouldn''t be the problems, since i see that all the time and my clusters work.. ( oh yeah, does it matter i have other

Hi all... When I start Mongrel I get a LoadError. I use the command > sudo mongrel_rails cluster::start -C /path/to/mongrel_cluster.yml and it says > Starting 2 Mongrel servers... but in the log I see this error: ** Starting Rails with production environment... /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'': no such file to load --

Hey all: When using capistrano and/or manually restarting mongrel clusters we encounter errors when restarting that states: ** !!! PID file log/mongrel.8010.pid already exists. Mongrel could be running already. Check your log/mongrel.log for errors. ** !!! Exiting with error. You must stop mongrel and clear the .pid before I''ll attempt a start. ** !!! PID file log/mongrel.8011.pid

On 1/23/07, mongrel-users-request at rubyforge.org < mongrel-users-request at rubyforge.org> wrote: > > > Date: Mon, 22 Jan 2007 21:48:21 -0800 > From: "Zed A. Shaw" <zedshaw at zedshaw.com> > Subject: [Mongrel] [ANN] Mongrel 1.0.1 Officially Released > To: mongrel-users at rubyforge.org > Message-ID: <20070122214821.4804e941.zedshaw at zedshaw.com>

I''m working on upgrading to rails 1.2.2 from 1.1.6 and getting the mongrel error below in development mode. Now things seem to work fine with 1.1.6and 1.2.2 (in prod mode). Any ideas what might cause this? Googling gave me very little to work with. This was the closest thing i found http://dev.rubyonrails.org/ticket/6716 I''m running Ubuntu with mongrel 1.0.1 and fastthread

Hi all, I''m using Boxroom (http://boxroom.rubyforge.org/) and trying to get upload progress working. I''ve also been testing the sample code at http://itblog.mcgeecorp.com/2007/5/15/mongrel-upload-progress-demo/. I run a Mongrel cluster, and so am using drb (as per http://mongrel.rubyforge.org/docs/upload_progress.html). Starting up rails, I get lots of useful-sounding output:

Hello mongrel list Does somebody know the answer to this problem when using mongrel_rails: /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__'': no such file to load -- http11 (LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require'' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:11 from

I have a fresh installation of Ruby, Rails and Mongrel. Unfortunately the server doesn''t start. Any ideas ? => Booting Mongrel (use ''script/server webrick'' to force WEBrick) => Rails application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with

We have a development environment that every morning requires a restart because Mongrel just stops responding. I noticed this older thread...but I still experience the problem http://rubyforge.org/pipermail/mongrel-users/2006-August/000950.html We are running nginx..but I also have the mongrel ports open to our IPs..both going through nginx proxy and directly through mongrel fails...then

I want to restart my Mongrels from crontab periodically to free up memory. I tried this: [admin at mudcrapce ~]$ mongrel_rails cluster::restart -C /var/www/apps/mudcrapce/current/config/mongrel_cluster.yml Restarting 5 Mongrel servers... mongrel_rails restart -P log/mongrel.3040.pid !!! PID file log/mongrel.3040.pid does not exist. Not running? mongrel::restart reported an error. Use

Hi, I''m trying to make my Rails app auto-install my required gems, by invoking the gem installation in boot.rb. I''ll use the ActionMailer gem as an example: ... system "sudo gem install actionmailer --version=1.2.5 -y" ... Problem is that this fails on the first invocation of Mongrel - it can''t find the gem. However, if I kill and restart mongrel (with the