similar to: Mongrel_Cluster PID File Creation Error.

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 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:

Hello all... I know its been a while since the last one, but a new prerelease is available with a gratuitous increase in version numbers! gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ This one has some new features in it that need to be tested on all unix platforms. Please run --clean and cluster::status on every *nix you can find. I run linux so the rest are up

Hello, I have a DB model that has many columns and I would like to separate the input from the user into web forms on many pages to not overburden the user with entering a lot of info on one page. However, I can''t figure out how to handle the validation of the user''s input... I would like to validate each piece of data on each form page before the user is allowed to move

Hi, I have an application which is dying horrible deaths (i.e. segmentation faults) in mid-flight, in production... And of course, I should fix it. But while I find and fix the bugs, I found something I think should be different - I can work on submitting a patch, as it is quite simple, but I might be losing something on my rationale. When Mongrel segfaults, it does not -obviously- get to clean

Hi there, I''m using Mongrel (0.3.13 prerelease, installed today) to serve up some Rails apps in production. Everything works fine if I give all the appropriate options on the command line, such as: $ mongrel_rails start -c /home/mcornick/rails/mcornick.org/current -P log/mongrel.pid -l log/mongrel.log -e production -d -a 127.0.0.1 -p 6833 So, having accomplished that, I thought it

nfsmount doesnt work anymore for me. This patch fixes at least udp nfs mounts. tcp does still hang. client and server is 2.6. --- /dev/shm/bindresvport.c 2003-12-08 02:33:24.000000000 +0100 +++ klibc/inet/bindresvport.c 2004-01-06 21:05:02.283779072 +0100 @@ -23,7 +23,7 @@ int bindresvport(int sd, struct sockaddr if (sin == NULL) { sin = &me;

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

I''m newbie to mongrel, I''m not able to config mongrel_cluster in order to host multiple web sites added/remove as apache VirtualHost. I followed codahale http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ mixed with Wiki Radiant (I use Radiant as a rails apps to be deployed, 1 domain 1 radiant sites with its own document tree

I wanted to show a Rails site to someone so I set up Mongrel and it ran fine, This is my mongrel_cluster.yml, port: ?80" environment: production pid_file: log/mongrel.pid servers: 4 Now, after going back to Apache/Tomcat I can''t get the Mongrel site up and running again...? Any suggestions? (When I run Mongrel, I stop Apache first) Jim

Info: Apache 2.2 mongrel 1.0.1 mongrel_cluster 0.2.1 I''ve had everything working with a bunch of applications like this when the the rails app is the document root, but a client just asked to move the app to a subdirectory, leaving he rest of their site alone. However, I can''t seem to get it to work. Let''s make the assumption that the Apache document root for the

Hi ! I''m using Mongrel 1.0.1 with --pid and --user/--group. The PID files are correctly owned by the user/group, but their permissions is 0666. Is that normal ? Shouldn''t it be something like 0664 ? Just curious to know if I''m wrong. Configurator has this (line 77): # Writes the PID file but only if we''re on windows. def write_pid_file if

I posted this to the rails list before by mistake, and only later realized that there is a specific mongrel list. Uff, I got lost. I had mongrel_cluster 0.1working fine, even with capistrano (my own hack). Then came mongrel_cluster 0.1.1 and I tried to set it up, but somehow I messed up things and nothing worked anymore. So here is what I did: on production machine: (debian linux, rails 1.1)

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

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''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, I am out of my head here... I have a 3 node cluster with 10 mongrels running on each. When I deploy, I break all the mongrels every time. I have tried just about everything. I can restart my mongrels without a hitch manually, it''s only when I use cap deploy. Maybe I am missing something here... so if I can get some help it would be appreciated. The errors are the typical mongrel

Hi everybody, I have installed mongrel and mongrel cluster in a new linux box .... at the end of the day I was able to lunch mongrel (mongrel_rails start -e production) and all is working fine with. However, when I tried to set a mongrel cluster the command mongrel_rails cluster::start get the following output : starting port 8000 starting port 8001 starting port 8002 But when I lunched the

Hi, I noticed one small possible error in the openssh-2.3.0p1/contrib/redhat/sshd.init script. In the stop option: stop) echo -n "Shutting down sshd: " if [ -f $PID_FILE ] ; then killproc sshd [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/sshd fi echo

Hi all I got a vps setup amazingly fast using the deprec recipes on Ubuntu edgy, but now I''m having a minor issue where my site loads for the main domain when I only want it accessible from the subdomain. This is a pretty typical setup, apache 2.2.3 -> mongrel_proxy_balancer -> mongrel cluster. I''m sure I''m missing something obvious in the config... I have the