similar to: Mongrel_Cluster unable to access OCI8 library

Hi, I''m trying to start a Mongrel (1.1.3) Server, running as a Windows Service, via mongrel_rails service::install -N FDS_Server_4001 -p 4001 -e production But I get the following error message : ERROR RUNNING ''service::install'': Plugin /service::install does not exist in category /commands I never had this problem before (Win XP, Vista), until I tried installing on

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

Hi, Does anyone know why gem can''t find activerecord-oracle-adapter? C:\>rails --version Rails 2.0.1 C:\>gem install activerecord-oracle-adapter ERROR: While executing gem ... (Gem::GemNotFoundException) Could not find activerecord-oracle-adapter (> 0) in any repository It all started when I tried to run Mongrel on a Win32 box: C:\web\FDS_Server>mongrel_rails start

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

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 successfully installed a RoR/Flex/Oracle application in a Windows environment and am now in the process of trying the same in Linux. Unfortunately, when I get to the part where I start Mongrel, I get the following error message: [root@localhost FDS_Server]# mongrel_rails start -e production -p 4001 /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in

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

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

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

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 have developed a rails application for my company. It will be used by upto 3o people at a time. I have just read that Mongrel will only process 1 request at a time (rails is only in 1 controller at a time). Does this mean that to get good performance i need to run mongrel many times on different ports? How many different instances of mongrel is recommended? If this is true then it

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

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

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

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

Hi list, I have tried to reach Bradley (author of mongrel_cluster) by mail, but have not gotten a response. So I''ll try trough this channel: I have ''developed''[1] a small extension to mongrel_cluster that allows selective restart of any one listener in a configuration that contains more than one listener by using a command like mongrel_rails

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