similar to: mongrel_rails not starting

os x 10.4.10 used gem to install mongrel 1.0.1. seemed to go w/o errors. "mongrel_rails start -d" spits out this error /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/http11.bundle: Failed to load /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/http11.bundle (LoadError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `require''

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

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,

Sorry for the newbie question but I''m stumped: I have an app that requires sudo to run mongrel_rails. For my capistrano recipe is do it like this: sudo "mongrel_rails start -e production -p #{application_port} -d -c #{current_path}" Which works famously. Now I have tried several things for my restart task. Here they are: sudo "cd #{current_path} && sudo

Hi Guys, I?m getting this error with mongrel_cluster. I am able to start mongrel through mongrel_rails start but the cluster is not working. Initially mongrel_rails wouldn?t work but after I added $ORACLE_HOME and $PD_LIBRARY_PATH variables it worked but mongrel_cluster isn?t working still. The mongrel log file looks like below. Any help is appreciated. Thanks. -----------begin

Thanks Bill for the answer ! In fact, my application is working well with webrick and also with a single mongrel instance lunched via the command : mongrel_rails start When I check what is the difference in the gem loaded in both cases (mongrel_rails start and mongrel_rails cluster::start) it seems that mongrel_rails cluster::start does not load all the gems that the first command is loading. So

mongrel_rails cluster::start doesn''t seem to pay attention to whether or not the processes exist or not. If you run it twice, the first set of processes are created, then then second run will overwrite the log/{pidfiles} files with the new process numbers. Problem is that the second group of processes are gone, since the first ones had the port open. I''d think that the right

I updated to ruby 1.8.6p111 last night and updated some gems and now mongrel doesn''t work: MacOS 10.4.10 $ ruby --version ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin8.10.1] $ gem list rails *** LOCAL GEMS *** rails (1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2.0, 1.1.6) Here''s a simple test: $ rails test5 create ... $ cd test5 $ script/server => Booting

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:

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

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

hi all I''m running background tasks using BJ 1.0.1 (gem version). On some requests, the tasks are executed as expected. On others, I get the following error: RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/ script", "/bin", "/usr/bin", "/sbin", "/usr/sbin"]): when it runs, it runs fine but does anyone know what

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,

Hi all... When I start Mongrel I get a LoadError. I use the command > sudo mongrel_rails cluster::start -C /path/to/mongrel_cluster.yml and it says > Starting 2 Mongrel servers... but in the log I see this error: ** Starting Rails with production environment... /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'': no such file to load --

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

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:

Greetings - I dug around a bit and I couldn''t find a definitive answer to this question, apologies if it''s been covered before. A box running a apache 2.2 -> mongrel cluster for a rails app got power cycled at my ISP. Unfortunately monit couldn''t start the mongrel processes because the pid files were still there. Here is my monit config (for each mongrel

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/.

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