similar to: Do i need multiple mongrel instances for good performance?

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

Hello all, I''ve gone through a lot of extra effort trying to get Mongrel to place nice with Ubuntu. Since I''m at my wit''s end trying to get it to work on this distro, I was wondering if anyone could suggest a distribution that makes it easy to set up. Any thoughts? Thanks, Will --------------------------------- Love cheap thrills? Enjoy PC-to-Phone calls to 30+

Hello list! I have mongrel service 0.1.0 working on my current production machine. Upgrading to a new server and also moving to mongrel service 0.3.1 has not worked yet. I am hoping someone will have an idea as to why. I have mongrel installed properly (I think): C:\rails\igacc>gem list --local *** LOCAL GEMS *** ... mongrel (1.0.1) A small fast HTTP library and server that runs

Hi *, What''s the best way to find out on which port mongrel is running from within Rails? I have a cluster of mongrels behind a balancer (Pen) behind a webserver (Apache). In Rails, request.port return 80 and request.env[''SERVER_PORT''] returns 3000 (the port of Pen) Any ideas? Cheers, Max

Hello all. Hope this doesn''t appear as spam... I am trying to run Mongrel on Win XP (SP2) for a web site (just one at the moment). For some reason it is giving me this error: E:\web\app2>mongrel_rails start -p 4001 -d ** WARNING: Win32 does not support daemon mode. ** Daemonized, any open files are closed. Look at log/mongrel.pid and log/mongr el.log for info. ** Starting Mongrel

Hi all Environment: Windows 7 64 bit Ruby 1.9.2.p0 Rails 3 I am getting the following error when I run the following command mongrel_rails service::install -N MyTestApp_4001 -p 4001 -e production: "Msvcrt-ruby18.dll is missing" Thanks in advance Gerhard -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi folks. Using mongrel_rails and the mongrel_cluster capistrano recipes, I often encounter a situation where some of the mongrel processes don''t die in time to be restarted. The output of capistrano will tell me something like "mongrel on port 8001 is already up", but that''s only because capistrano/mongrel_rails failed to take it down in the first place. The solution

Hello Folks, This release of Mongrel should make the win32 folks go crazy. Thanks to Luis Lavena it supports a full service system for installing any Rails app as a service. This lets you start your rails apps from either the command line or the Service console. Stopping is still a bit problematic but we hope to have that solved in the next release. You win32 folks should probably send Luis

All, I am in need of some help. I''ve run into a problem that I am not able to fix or even troubleshoot. I am trying to run Mongrel as a service on Win32. Basically, my problem is that running Mongrel as a service works fine. Fine until I change the configuration (using service::remove and service::install) to use --prefix. I must have this as I am running multiple webapps and app

Hey Folks, I''ve been holding off the official 0.3.13 release so that Luis can get the win32 side very nice and clean. We fixed a major problem last night so it''s only a short time before we get it out. Luis is working really hard on it, so just be patient. In the meantime, I''ve been doing a code audit of the Mongrel code as it is now and fixing any little things I

Hi -- I have been reading documentation and googling around to find the correct way to do this but I have found many ways that seem to not work, or the documentation makes no reference to. I am using mongrel cluster with 10 mongrels for each server. Recently I installed monit but which lead me to find the correct way to start/stop mongrel instances one pid at a time. I am assuming one pid at a

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

I''m running a site that gets ~30k to 40k page hits per day. In the last 4 days my mongrel processes have been jumping into high CPU usage a couple of times a day to the point where my site becomes unresponsive (database on a diff machine with no load). The only way for me to resolve the problem and reduce load on the machine is to delete my rails cache directory (I have plenty of space

Hi, I have mongrel 0.3.14, with ruby 1.8.5, rails 1.1.6 and mongrel cluster 0.2.1, on debian sage 3.1 with apache 2.0, and fastthread 0.6.1. I am load balancing 3 mongrel processes using the random port trick. When I start mongrel the processes have about 60MB, but after some hour of usage the memory ballons upto more than 180MB and the site becomes terribly slow. Forcing me to restart mongrel

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 guys, I''ve been running mongrel for a while now with Ruby 1.8.4, and last week upgraded to 1.8.6. Since upgrading, each morning when I wake up there''s a big problem: 1. Accessing the site returns a "500 Internal Server Error" 2. All the mongrel_rails processes are still running, but none of them are active (when I run top) 3. Lighttpd and pound are still

Hello world, I''m having some problems setting up a new Debian deployment box...just installed the rails stack, mongrel, etc... When I go to start mongrel I''m getting a weird error I can''t figure out. Some help please? -> mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000

Hi, I am working on deplying my Rail app to QA and then move to production. Since on our QA servers, there is no internet access and also for production servers, internet access is strictly prohibited. As a result, there is no way to install mongrel by use "gem install mongrel" command. The first option I tried is to put mongrel and all other gems under the vendor directly in my app,

I want to restart my Mongrels from crontab periodically to free up memory. I tried this: [admin at mudcrapce ~]$ mongrel_rails cluster::restart -C /var/www/apps/mudcrapce/current/config/mongrel_cluster.yml Restarting 5 Mongrel servers... mongrel_rails restart -P log/mongrel.3040.pid !!! PID file log/mongrel.3040.pid does not exist. Not running? mongrel::restart reported an error. Use

While I could figure this out, I''m asking here first to see if anyone has already dealt with/created this. I''m running a mongrel cluster, running 4 mongrels on ports 8001-4. I''m using capistrano to deploy. And I''d like to use monit to check to make sure everything is running nice. I''d like to have monit restart only single mongrels if they fail, and