similar to: mongrel_cluster: selective restarts

Hi mongrel users! I just posted a bad-ass capistrano file that automates *everything* for setting up an apache2+mod_proxy_balancer and mongrel+mongrel_cluster -- including apache2 setups. It''s based off Coda Hale''s guide and all Bradley''s work at fluxura and RailsMachine (thanks Coda and Bradley!). It''s, well, bad-ass, if I must say so myself. My favorite

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 currently working on 4 different RoR apps all using mongrel cluster and each with their own config file in /etc/mongrel_cluster. I would like the ability to stop|start|restart a single app. Anyone working on something like this? I''d be happy to code it up and contribute this if there''s a need. Basically I would like this: sudo /etc/init.d/mongrel_cluster restart

Hi Folks, I''m sure tons of people are gonna ruin a whole drawer of their best panties over this one. Rick Olson worked on the mongrel_upload_progress gem, documentation and examples and has almost everything you need to do progress tracked file uploads using just Mongrel to handle the upload. This means that Rails (or any other framework) isn''t blocked while the upload

Hi everyone, Just wanted to tell you a little story. We''ve been enthusiastic puppet users since about a year ago here at the Geographic Institute of the University of Zürich. But we won''t use the zpool type ever again. Its just not worth it. Here''s what happened: . one of our servers lost knowledge about one of its zfs pools . puppet didn''t find the pool

It seems that a recent code cleanup broke --user and --group switch in the trunk. Mongrel essentially ignores these commands. This applies to everyone who has installed gem install mongrel --source=http://mongrel.rubyforge.org/releases/ recently. I have attached a patch to revert to some old working code. best regards, kaspar -------------- next part -------------- An embedded and

Hi list, I have hacked together a small script to generate an ActiveRecord model from a DBDesigner 4 (fabForce.net) model file. Take it apart and feed it to the pigs ;). the article: http://tua.ch/ruby/current.html and the script: http://tua.ch/ruby/dbmodel/compute_model.rb best of whishes for the new year, kaspar code manufacture & ruby lab at http://www.tua.ch/ruby

Hey y''all: I''ve added some new stuff to mongrel_cluster. Give it try and let me know if it works for you. * Added ''--clean'' to cluster::start to force removal of the pidfile before trying to start the cluster member. This is useful for recovering from unexpected process death. * Added ''--only PORT'' to cluster::* to support running a

Hello List, I have a production machine with very low ram (Xen Virtual Server) that runs mysql and lighty->pound->mongrel (2 instances). About once a day, one of the mongrels just locks up, leaving that in its log files: *** glibc detected *** /usr/bin/ruby: free(): invalid next size (fast): 0x0a744780 *** That process (mongrel) will stay locked, not answer any connections anymore and

Hi everyone, I am going crazy over here! :) I just want to be able to use --clean with my mongrel_rails cluster::start command. I''ve upgraded to mongrel_cluster 1.0.1.1 and mongrel_rails 1.0.1. my config file is in /etc/mongrel_rails/config.yml and contains: --- log_file: log/mongrel.log port: 8000 pid_file: /var/run/mongrel_cluster/mongrel.pid servers: 2 address: 127.0.0.1 environment:

Hi, I''m in the process of moving my blog over from lighttpd -> apache 2.2 + mongrel. Everything works fine as long as I don''t reboot :) On reboot apache comes up but mongrel_cluster doesn''t start up the pooches... I have added the mongrel_cluster call to my startup scripts like so: www:/etc/init.d# update-rc.d mongrel_cluster defaults Adding system startup for

I''m running the latest mongrel (1.0.1) and the latest mongrel_cluster (1.0.1.1) on FreeBSD 6.1. When I use capistrano to try to stop or restart my cluster I get this (partial) output: ps: Process environment requires procfs(5) And my Mongrel processes haven''t stopped. Any ideas? Thanks, Jamie

Hello, Apologize if this is a annoying faq but folks here are trying to get a cluster going and something odd is happening. When ''mongrel_rails cluster::start'' is run, the following error is getting returned: ERROR RUNNING ''cluster::start'': Plugin /cluster::start does not exist in category /commands Is this the result of a simple path issue or perhaps a

I wanted to be able to specify in my /etc/rc.conf file whether mongrel_cluster should be enabled and the mongrel_cluster_config file for the init script, so I wrote this simple rc.d style script. Just throw it in /usr/local/etc/rc.d/ and do a chmod +x /usr/local/etc/rc.d/mongrel_cluster.sh To enable the script, add mongrel_cluster_enable="YES" to /etc/rc.conf and optionally add

hi, how to configure mongrel_cluster in windows. mongrel_rails cluster::configure -e development -p 3000 -N 2 i have used this one its configured correctly then if i start the server it is throwing error.if any one knows how to configure help me with regards shiva -- Posted via http://www.ruby-forum.com/.

Hi everyone, I''ve been working with Mongrel, Mongrel_cluster and Apache and it is great. However, I can''t get mongrel_cluster to start at boot time. I followed the instructions from http://mongrel.rubyforge.org/docs/mongrel_cluster.html (On Boot Initialization Setup) and mongrel_cluster does not start after rebooting the machine. I made sure that the shebang line is correct and

Hi, I''m trying to setup my mongrel clusters to start on boot. I have followed the instructions under the "On Boot Initialization Setup" section at http://mongrel.rubyforge.org/docs/mongrel_cluster.html. When I try to start it up, I get the following error: me at mybox.com: sudo /etc/init.d/mongrel_cluster start Starting all mongrel_clusters... !!! Path to log file not

So, Leopard server has been great, most everything I need is here. Thanks to a nice example here: http://www.cyberarmy.net/library/article/1722/ I was even able to sort out using Mongrel with Apache 2. All works out of the box, except mongrel_cluster. The gem just won''t install. I could really use some guidance here. I did try the darwinports mongrel_cluster install from here:

Hi folks, I''d like to run the Mongrel prerelease (0.3.13.4 prerelease) and mongrel_cluster 0.2.1 on my shared host (which doesn''t want to install prerelease software for all to use). I can install the gems in my own directory, and run mongrel 0.3.13.4 with --prefix just fine. However, I think due to the GemPlugin structure, even my new mongrel_rails loads up

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