Displaying 20 results from an estimated 10000 matches similar to: "Restarting mongrel cluster from other directories"
2007 Aug 10
10
what is the correct way to stop/start a mongrel instance using monit with mongrel cluster
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
2007 Feb 02
1
Monit / mongel_cluster 0.2.2 / mongrel 1.0.1
Hi,
I''ve a few problems with my rails app at the minute, causing mongrels
in a cluster to die, while I debug I''ve setup monit to keep the site
running.
Problem is, whenever monit starts one of my mongrels via mongrel_rails
cluster::start --only 8000 --clean -C /url/to/yml/file I get the
following in my log/mongrel.log:
** Mongrel available at 127.0.0.1:8000
** Writing PID file
2007 Mar 29
4
Machine reboot - monit fails to start mongrels
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
2008 Jan 21
14
properly restarting mongrel instances
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
2007 Mar 26
4
Monit + Mongrel woes
Hello all,
So, I''ve been using monit with mongrel for a while now, since the
0.3.x days (I think it was). It used to work fine, but now I seem to
be having some trouble. I''m currently using mongrel 1.0.1 and I am
using the same monit configuration I''ve always been using, yet
everytime monit should restart mongrel, I get "Execution failed".
For the start
2007 Apr 03
11
monit vs mongrel cluster
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
2007 Aug 26
1
monit not executing start/stop/restart mongrels
Alright, I have googles and read through the docs on monit
I get this error when adding -v starting monit
monit: Cannot connect to the monit daemon. Did you start it with http support?
monit: Cannot connect to the monit daemon. Did you start it with http support?
Am I missing something here?
set daemon 120
set logfile syslog facility log_daemon
set mailserver localhost
set httpd port 28212
2007 Feb 27
3
mongrel_cluster and Monit
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
2006 Nov 05
2
logrotate, mongrel cluster and monit
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
2006 Sep 01
2
Making Mongrel play well with Monit
Hi!
I run a mongrel cluster with 6 mongrels in it. I want to monitor them
individually for process hangs (and then restart them) and this is the
solution I came up with:
Here''s my configuration file for monit (/usr/local/etc/monitrc): [snipped
relevant bits]
------
#check lighttpd process
check process lighttpd with pidfile /var/run/lighttpd.pid
start program =
2009 Feb 04
1
How to hack a mongrel cluster to restart in an alternating manner?
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
2006 Jul 13
3
Mongrel Cluster 0.2.1 prerelease
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
2007 May 08
5
mongrel_cluster 1.0.1.1 does not create /var/run/mongrel_cluster
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:
2007 Jun 15
1
mongrel cluster issues, plain old mongrel OK
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,
2007 Jan 02
10
problems with apache 2.2 proxying to mongrel cluster
Hi all,
I''ve been having problems with the apache 2.2-mod_proxy_balancer-
mongrel setup.
My setup is:
CentOS 4.3
apache 2.2.3 (compiled from source) with mod_proxy_balancer
mysql 4.1
ruby 1.8.4
mongrel 0.3.14 (I know I need to update but I think this problem is
independent of the mongrel version)
mongrel_cluster 0.2.0
rails_machine 0.1.1
I have apache setup as per Coda''s
2006 Aug 03
9
Finding out on which port mongrel is running
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
2008 Jan 03
23
deployment survey
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,
2006 May 01
3
mongrel_cluster-0.1.1: the bird dog (capistrano support!)
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
2006 Nov 08
2
restart - `exec'': Operation not supported
I played around with this some more and when I changed
line 142 of
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails
from "exec cmd" to "system cmd" Mongrel has
successfully restarted every time I''ve tried
("mongrel_rails restart").
Hell if I know why exec doesn''t work -- googling on
"exec Operation not supported ruby"
2008 Dec 10
2
mongrel_cluster : up to 500 MiB memory
Hi everyone,
I''ve got some trouble with my RoR application running with apache
(2.2.9) and mongrel (1.1.5).
The site i manage has about 20''000 visits a day, and we run 14 mongrel
instances switched with mongrel_cluster (1.0.5). The fact is, sometime,
half of my mongrel instances are raising something like 500MiB memory
and don''t seem to work anymore.
The server itself