similar to: Mongrel: Config File Q

Hello Folks, This is the big release of Mongrel that''s been in the works for a while now (well, like a week). It is chock full of changes and features, but mostly it syncs up the Win32 side of things, and validates that Edge Rails works without problems. It also features a more extensive and useful example of the GemPlugins called mongrel_config. First the usual stuff for people

I am not sure what i am doing wrong here, but no matter what i try i get no output from mongrel_config: $ mongrel_rails configtool $ telnet localhost 3001 Trying 127.0.0.1... Connected to localhost. Escape character is ''^]''. GET /config/ HTTP/1.1 HTTP/1.1 200 OK Connection: close Date: Tue, 19 Dec 2006 05:33:16 GMT Content-Type: text/html Content-Length: 0 Connection closed by

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

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,

Hello Mongrels, Building on the last messages about Fastthread, can we get a detailed survey of the different ways people are deploying their applications? It will help with near-future Mongrel development. Please include the following things: * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...) * Mongrel version * Mongrel handlers used (rails, dirhandler, camping,

Hello Folks, This is the big release of Mongrel that''s been in the works for a while now (well, like a week). It is chock full of changes and features, but mostly it syncs up the Win32 side of things, and validates that Edge Rails works without problems. It also features a more extensive and useful example of the GemPlugins called mongrel_config. First the usual stuff for people

Hello all. I''ve recently installed the 0.2.2 pre-release of mongrel_cluster to try out the new --clean option. However, after installing, when I give a simple "mongrel_rails" command, the cluster::status command is not listed. The error I receive when I do try and run the full "mongrel_rails cluster::status" is... ERROR RUNNING

Hi Y''all, Just a quick note announce an update to mongrel_cluster. Changes: - ''mongrel_rails cluster::restart'' now calls ''mongrel_rails stop'' and ''mongrel_rails start''. ''cluster::restart'' now accepts the ''force'' argument instead of ''soft''. - Added ''.conf'' as

Hi, I use Mongrel to serve my Rails applications on my server, but how can I serve more than one application with one mongrel server? Thanks. -jec -- Best regards / Salutations. Jean-Eric Cuendet Senior developer / Technical support Riskpro Technologies SA Av. Louis-Ruchonnet 2 CH-1003 Lausanne Switzerland Direct : +41 21 637 0123 Principal : +41 21 637 0110 Fax : +41 21 637 0111

Hello, I''ve been trying (unsuccessfully) to hack my mongrel_cluster to re-ststart in an alternating manner. Specifically, this soluiton: http://blog.carlmercier.com/2007/09/07/a-better-approach-to-restarting-a-mongrel-cluster/#content Which means I an call to mongrel_rails cluster::restart to do this: mongrel_rails start 8001 mongrel_rails stop 8001 mongrel_rails start 8002

Hi, I''m running CentOS 4.3 and the latest Mongrel (0.3.13.3) and mongrel_cluster (0.2.0). I have set up a cluster, following the instructions at http://mongrel.rubyforge.org/docs/mongrel_cluster.html . I created a symbolic link in the directory /etc/mongrel_cluster . When I run mongrel_rails cluster::start -c test.yml, the mongrel servers start up. But at boot, the command

Is there anything mongrel cluster gives you that monit doesn''t? I''ll be using monit to monitor a number of other services anyways, so it seems logical to just use it for everything including mongrel. Chris

I have installed mongrel and mongrel_cluster fine and have them running great with my app. I tried using the init.d script provided with mongrel_cluster 2.1 to start it up on boot but it doesn''t. mongrel_cluster_ctl works fine for me by hand and so does /etc/init.d./mongrel_cluster start. I am on Debian so I installed the service links with sudo update-rc.d mongrel_cluster defaults. And

I don''t think there''s a way to do that other than using a proxy (ISAPI_REWRITE) or just a server-side redirect. I''d love to be proven wrong though. -----Original Message----- From: rails-bounces@lists.rubyonrails.org [mailto:rails-bounces@lists.rubyonrails.org] On Behalf Of frazer horn Sent: Wednesday, March 15, 2006 9:13 AM To: rails@lists.rubyonrails.org Subject:

Hi list, I have a problem with Mongrel which is really bugging me. I would really appreciate any help that anyone can provide to help me in solving this problem. 1. My setup: Apache front_end with mod_proxy_balancer in front of 4 mongrel/rails instances of my application. Rails 1.2.5 Ruby 1.8.6 Mongrel 1.1.1 2. I noticed that the CPU consumption on my server was 100% being consumed by ruby so I

Hello all, So, I''ve been using monit with mongrel for a while now, since the 0.3.x days (I think it was). It used to work fine, but now I seem to be having some trouble. I''m currently using mongrel 1.0.1 and I am using the same monit configuration I''ve always been using, yet everytime monit should restart mongrel, I get "Execution failed". For the start

I''ve done a clean install of Ubuntu 7.04 server in 2 different machines and everytime I reboot the machine or manually run /etc/ init.d/mongrel_cluster restart/start the mongrels won''t start correctly. I have to manually start them by using mongrel_rails cluster::start from each app folder. I''ve been searching around and it looks like mongrel has some problems

Hi y''all; A quick note to announce the release of mongrel_cluster, a gem_plugin for Mongrel. This plugin provides commands for managing multiple Mongrel processes behind a reverse-proxy server and load balancer. To install: gem install mongrel_cluster Configure (use -h to options): mongrel_rails cluster::configure Start: mongrel_rails cluster::start I''ve posted a quick

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 all, Forgive me if this has been asked before, but is there a reason mongrel_rails cluster::restart stops all ports and then restarts them again? Wouldn''t it be better to restart each port one-by-one in series so that upstream proxy servers can fail over while the restart is occurring, or am I missing something? Thanks, eden