similar to: can not delete pid fils when stopping mongrel_cluster

Hey y''all: mongrel_cluster provides management tools for running Mongrel behind a reverse-proxy/load balancer. It is an extraction from Rails Machine, a deployment service and Ruby library that simplifies Rails application deployment. This release fixes bugs and adds a Capistrano task library. Changes: -changed pid file format to include port -only write configuration options

Hi, I''m calling restart from my Capistrano task. I have this in my deploy.rb file: # until mongrel_cluster updates to cap2... namespace :deploy do task :start, :roles => :app do start_mongrel_cluster end task :stop, :roles => :app do stop_mongrel_cluster end task :restart, :roles => :app do restart_mongrel_cluster end end (What''s the scoop on

Hi y''all, An prerelase of mongrel_cluster 0.1.3 is available for testing with the Mongrel 0.3.13 prerelease. This release contains bug fixes and adds a Ruby script for managing all applications on a server with a single command. To install: gem install mongrel_cluster --source=http:// railsmachine.rubyforge.org/releases/ Changes: * Suppress output from mongrel_rails. * Added

Hi y''all, A prerelease of mongrel_cluster 0.1.3 is available for testing with the Mongrel 0.3.13 prerelease. This release contains bug fixes and adds a Ruby script for managing all applications on a server with a single command. To install: gem install mongrel_cluster --source=http:// railsmachine.rubyforge.org/releases/ Changes: * Suppress output from mongrel_rails. * Added a

I''m playing with the mongrel clustering, and am having a problem getting 2 mongrels to start up reliably. This should be a pretty simple cluster, with just 2 instances running. My mongrel config (mongrel_cluster.yml) looks like: cwd: /deployment/installed/myapp/current log_file: log/mongrel.log port: "8000" environment: production address: 127.0.0.1 pid_file:

Hi -- I have been reading documentation and googling around to find the correct way to do this but I have found many ways that seem to not work, or the documentation makes no reference to. I am using mongrel cluster with 10 mongrels for each server. Recently I installed monit but which lead me to find the correct way to start/stop mongrel instances one pid at a time. I am assuming one pid at a

Hello, I''ve install ror/mongrel etc, etc on a linux server (rhes). As i''m not root, all package startinf from ruby have been install into ~/gconf/usr ruby-1.8.6 and all of this gem package: -r-xr--r-- 1 dimnce dba 168448 Aug 9 14:53 rails-1.2.3.gem -r-xr--r-- 1 dimnce dba 84480 Aug 9 14:56 rake-0.7.3.gem -r-xr--r-- 1 dimnce dba 217088

Hi, I just did a clean install of Ruby 1.8.5 Rubygems 0.9.0 and the Mongrel and Mongrel_Cluster gems. I used only the Debian Etch package manager, nothing compiled myself. Now, on a testapp when I do a script/server, I get the: ** Ruby version is not up-to-date; loading cgi_multipart_eof_fix warning. But it''s not serving my app. Ruby is immediately on 100% CPU load (and 0.7%

Hi After having updated some GEMS I get `load_missing_constant'': uninitialized constant ActiveSupport::Cache (NameError) on starting the server of a freshly generated rails project. Before, I already had Rails 2.3.2 projects succesfully running, now all of them generate this error. These are my GEMS: actionmailer (2.3.2, 2.2.2, 2.1.2, 2.1.1, 2.1.0) actionpack (2.3.2, 2.2.2, 2.1.2,

I''ve noticed that the copy of Mongrel installed by the camping-omnibus gem doesn''t work with Ruby 1.8.6. Or to be more specific, cgi_multipart_eof_fix (which Mongrel is dependent upon) doesn''t work: > $ sudo gem install mongrel --source http://code.whytheluckystiff.net > > ERROR: Error installing mongrel: > cgi_multipart_eof_fix requires Ruby version

Hello, Thank you for your development of Mongrel, great job. :) I am using mongrel_cluster, but I have a problem where my rails application name includes a "." such as mydomain.com, which causes an error when generating the PID file for mongrel. I have attached below a diff of the current working copy in the trunk and the changes I made to overcome this problem. I kept your

Like most people, I''ve got two machines: one for development and one for production. I''ve done everything I can to make sure the ruby/rails environments are the same, but of course they''re not identical (I''ll get into that in a moment). The error that I''m getting happens when I call a method in a background task controller on the production machine; I

I have a Fedora Core 6 system on which I have built ruby 1.8.6 and rubygems 1.1.1 from source, and installed rails 2.0.2 using rubygems. When I create a new rails app, I get lots of errors that look like they''re coming from internal ruby libraries. Lots of methods redefined, as if I have some duplicate code somewhere. I also get errors when generating a simple model (see below.) I

Hello, I''m trying to deploy my application with Capistrano using Mongrel recipes. Since I''ve installed Ruby from source code, mongrel scripts are found in /usr/local/bin. But the recipes can''t find mongrel_rails : "bash: mongrel_rails: command not found". The path of the user account used to deploy is OK. For sure, I can redefine

This is important so please read this message very carefully. There is a DoS for Ruby''s cgi.rb that is easily exploitable. The attack involves sending a malformed multipart MIME body in an HTTP request. The full explanation of the attack as well as how to fix it RIGHT NOW is given below. Most of the work was done by Jeremy Kemper and Jamis Buck. They did all the work of building the

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

Hopefully that gets everyone''s attention. Evan Weaver has whined enough to make me do a release to change the requirements on the Mongrel gem so that it doesn''t need the cgi_multipart_eof_fix anymore. *************************** THIS ALSO MEANS THAT MONGREL WILL HAVE TO REQUIRE RUBY 1.8.6 OR GREATER! NO EXCEPTIONS! *************************** I know Debian guys like to hack

Hello, I am new to Rails and the Linux world coming from 12 years of advanced VB programming. I am writing to try and clear up some confusion on my part about installing Mongrel. Please don''t take this as a rant, I do appreciate the effort that y''all put into the community, but as a newbie, I was, and still am confused. I want to learn about Mongrel, so it found

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,

It''s time again for your monthly cgi.rb DOS vulnerability. This latest vulnerability is different from the one that cgi_multipart_eof_fix.gem fixed. This one is related to the boundary taken from the web client being used incorrectly. You can read about the vulnerability: http://www.ruby-lang.org/en/news/2006/12/04/another-dos-vulnerability-in-cgi-library The applicable PATCH is