similar to: Mongrel stops responding after period of inactivity

Hi I''m running a 2-instance Mongrel cluster behind Apache 2.2.4 with Rails 1.2.3. If no requests are received by the application for several hours (this usually happens overnight) then Mongrel stops responding and no requests are detected by Rails (at least nothing is in the Rails log). Nothing untoward is in the Mongrel log. If you try and visit the application, the request times out

I''ve posted this to rails-deployment as well. I have to administer a medium size rails app (1''5 million requests each day), recently I''ve switched from lighttpd + fcgi to apache + mongrel. In the following lines I am going to describe the platform: All machines are running Debian Etch, with 4 gb ram and dual core intel32 processors. Web server runs debian''s

Good morning everyone, I am running apache 2.2.3 compiled from source and proxy load balancer as described on the mongrel site. I have a total of three sites, this setup works really well for two of them but for one of them, I keep getting "Forbidden" errors and this error in the apache logs: [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of

If this was in the docs, I''ve missed it. How can I have multiple mongrel clusters on a server? All the documentation that I am seeing seems to assume that I am only running one cluster.

I''m trying to set up several different Rails apps on the same domain, each one running Mongrel. After reading all of the documentation, it''s fairly clear how to use subdomains - create several Apache virtual hosts, each of which has a different ProxyPass and ProxyPassReverse command to redirect from different ports (ie, 3000, 3100), and then have each Mongrel instance (or

Hi all, I''m currently trying to get Mongrel running my app whilst fronted by apache 2.2 in a sub-directory via https. A bit convoluted I''ll grant you but necessitated by existing systems. The pertinent parts of my httpd.conf: <VirtualHost 123.123.123.123:12345> #historic choice of random port number DocumentRoot /var/www/admin ServerName admin.example.com:12345

Hello, I am configuring apache 2.2 to serve my rails app through mongrel at the root of my server. First, I redirect all http traffic to https with the following: ServerName emiliano NameVirtualHost *:80 <VirtualHost *:80> RedirectPermanent / https://emiliano #this server is only accessed internally </VirtualHost> Inside the <VirtualHost *:443> section, I have the following

A question about mongrel, apache and authentication. I''ve got a Rails site with I think a very typical setup: a mongrel cluster behind an Apache proxy. So Apache''s handling the static stuff and it hands off dynamic content to mongrel. I want to put the site temporarily behind Apache''s basic authentication. What I get when I do this is that is a password prompt which

Jeff try adding to your mongrel_cluster.yml :docroot: /var/radiant/domainA.com/public -- Together we can solve any issue.

Hello everyone, I did some initial tests and it seems that mongrel does not support byte-range requests. Is this correct? The reason I ask is that the iPhone requires byte-range requests to work in order to stream audio or video from a web server. Thanks in advance, alan

Hi all, I?m new to the list. I''ve working with mongrel for the last week and have some quetion about mongrel cluster: Is this (being executed from the application folder): # mongrel_rails start -d -p 3001 -e production # mongrel_rails start -d -p 3002 -e production # mongrel_rails start -d -p 3003 -e production the same as: # mongrel_rails cluster::configure -e production -p 3001 -N 3

hi all, i''m working on deploying my app w/ apache and a mongrel cluster. i''ve started by copying the instructions and code from the agile rails book and everything seems to be working fine but apache isn''t forwarding my requests to mongrel the way i expect it should. there''s nothing in the rewrite logs and nothing but 404 errors in the apache error logs.

Rails instances themselves are almost always single-threaded, whereas Mongrel, and it''s acceptor, are multithreaded. In a situation with long-running Rails pages this presents a problem for mod_proxy_balancer. If num_processors is greater than 1 ( default: 950 ), then Mongrel will gladly accept incoming requests and queue them if its rails instance is currently busy. So even

I just finished updating our internal site, which hosts multiple Rails apps, to Apache 2.2.3. It also has a TWiki rewritten into the root, ViewVC mounted on /cvs, and /server-status and /server-info. <VirtualHost *:80> ServerName int.example.com ServerAlias int CustomLog /var/www/logs/int.example.com/access.log combined ErrorLog /var/www/logs/int.example.com/error.log [...]

Apologies, this may be off-topic. I''ve been wrestling with upload issues and Apache 2.2.2 / mod_proxy_balanacer / mongrel_cluster / Mongrel on Mac OS X Server 10.4.5. Typically the first upload would be fine but the next would make the mongrel instance remain running (ps state = "R") essentially locking up that instance. Apache would then eventually do: [Fri Jun 16 16:45:54

Most of my machines have apache+mongrel running but the mongrels are using the localhost. In my production environment, I have 4 boxes. I have setup 2 http servers ( apache 2.2.4 ) and 2 app servers. They are currently using lighttpd+fastcgi. Which I am changing this week. I want to get advice from you guys before I actually do this since this is my production env. I have installed apache on the

I?m knew to rewrites on apache in combination with mongrelcluster. It?s urgend for me, because the server has an loadaverage about 10 :-((((( Ok so I?m using 3 mongrel-server on an mongrelcluster. The Loadbalancer ist apache I think, that my rewrites are not correct. Please can anybody check my rewrites ? That?s in my /etc/apache2/conf.d/rails.proxy_cluster.conf <Proxy

I am followint this article, http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ ...but I keep getting this error in the log...not sure what to try next... ** Daemonized, any open files are closed. Look at log/mongrel.8000.pid and log/mongrel.log for info. ** Starting Mongrel listening at 127.0.0.1:8000

Hi, I''ve configured a rails application on my VPS to run on two mongrels. When I run curl on localhost, the starting page comes up fine. That is, mongrel is serving the app perfectly. The problem arises when trying to access the app on my ip through apache. I get a 403 error. Just to test things out, I''ve set generous permissions on the entire rails directory structure

Hi everybody, We are developing several applications on a single server and I''m looking for a way to use mongrel with each of them. Right now, http://testapp.com/ is being served on that machine through apache and mongrel. Here''s what a part of my apache config looks like: <Proxy balancer balancer://testappcluster> BalancerMember http://127.0.0.1:8000