similar to: FreeBSD 6.1 mongrel_cluster and procfs message

I''m running FreeBSD 6.1 and installed the 1.0.1.1 mongrel_cluster prerelease. I had a problem with the mongrels not stopping, and it turns out it''s because ps is reporting my processes as just [ruby18] instead of someting more like "mongrel_rails start -d ......." Not sure why it''s doing that, but it is. Any ideas? For the time being I just changed line

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

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

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

Hey folks. Sorry for the SUPER long email but if you''ve been experiencing the same problems with restarting your mongrel cluster with Capistrano, then I have two solutions that have worked for me and I''m pretty sure will for you as well. THE PROBLEM I was having trouble restarting my clusters using Capistrano. I''ve seen this come up before on the mailing list and

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

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

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

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

Hi all, I am having trouble transitioning from fastcgi to Mongrel. I have it all working apart from one small part, I can''t get the service to start on boot. I have followed the instructions and if I call the script directly: i.e. "/etc/init.d/mongrel_cluster start" it works fine, but if I call it using "service mongrel_cluster start" it fails with the

Hi all... Hopefully this is the last prelease. If people on non-linux systems could post back any problems with cluster::status, I''d appreciate it. Install with: gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ Note: This is only an update to mongrel_cluster and not Mongrel or other gems. Details about what''s new (if you missed the first

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:

I''ve installed pen and mongrel with mongrel_cluster (as gems) on Debian sarge. I can run everything from the command line fine including starting from the /etc/init.d/mongrel_cluster script On boot though mongrel_cluster fails with this msg: /usr/local/lib/site_ruby/1.8/rubygems.rb:204:in `report_activate_error'': Could not find RubyGem mongrel_cluster (> 0) (Gem::LoadError)

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

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

It appears the spawner in Rails 1.2 will do Mongrel clustering. I''m curious what this means for mongrel_cluster. They appear to overlap in features quite a bit. I don''t think the spawner uses a config, so that''s one difference. Will they be different enough? I only ask because mongrel_cluster could, theoretically, be made extinct if the spawner script has all the same

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''m able to run a ROR application in a Red Hat Enterprise Linux 4.4 environment, as long as I start my mongrel_cluster via the command line: [chris at localhost ~]$ mongrel_cluster_ctl start I take a look at the two mongrel_rails processes that were just created: [chris at localhost log]$ ps -ef | grep mongrel chris 4781 1 5 05:55 ? 00:00:02 /usr/local/bin/ruby

On one of my development servers mongrel dies when idle for any length of time. Since I''ve not been able to solve that problem I thought I''d route around it by using monit to kick things when necessary. My monitrc contains the following... -------------------------------------------------------------------------------- check process mongrel_8310 with pidfile

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