similar to: ProxyTimeout

CentOS 5 Using Proxy BalanceMember... <Proxy balancer://mongrel_cluster> BalancerMember http://localhost:3000 BalancerMember http://localhost:3001 BalancerMember http://localhost:3002 </Proxy> and I am having problems with a particular process taking longer than 2 minutes at which point the proxy seems to time out and I get an error. I added: 'ProxyTimeout 600' to the

Hi all I got a vps setup amazingly fast using the deprec recipes on Ubuntu edgy, but now I''m having a minor issue where my site loads for the main domain when I only want it accessible from the subdomain. This is a pretty typical setup, apache 2.2.3 -> mongrel_proxy_balancer -> mongrel cluster. I''m sure I''m missing something obvious in the config... I have the

Hi. I am using BackgrounDRb to process thumbnails and upload to S3 - things are hunky-dory in development (thumbs are generated, these are uploaded to S3, the metadata is saved to trhe DB, and I get a nice status page updated by periodic calls via ask_status), but when I tried to deploy to our staging server and stop/start BackgrounDRb via Capistrano, things blew up - well, not exactly,

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

Hi, Not a CentOS specific issue, but I am a bit stuck as where I might ask for help so if anyone has any ideas please share :) I have a site that I want to work behind a reverse proxy (httpd) if using http:// everything works as expected. If using https:// some content is displayed but some content is blocked because of stylesheets and etc being requested via http rather https. I know that the

Hi all, BackgrounDrb was exactly what I needed for a project I''m working on at work. Everyone''s really impressed, and now it''s time to put the system into production. My question is, how do I avoid having to manually run the startup and shutdown scripts (or the rake tasks) for backgroundrb? I tried putting a system "rake backgroundrb:start" in my

Hello everyone, I have a site setup where I need to have svn access and my rails app accessible on the same IP. Right now I can only seem to have one or the other. This is a production environment... I''m running Ubuntu 7.04 server with apache2 and mod_proxy serving rails requests to 2 mongrel servers via mongrel_cluster and it works great to serve the app when I use this httpd.conf file

According to the mongrel_cluster.yml file you provided, you''re starting only 14 mongrels, but in your proxy balancer config you have 30 mongrels listed on ports 21000 - 21029. In this scenario, if apache tries to proxy to any ports higher than 21014 then you''ll get a proxy error as a mongrel doesn''t exist on that port. Or am I missing something? -----Original

On 09/30/2015 08:22 PM, Clint Dilks wrote: > I have a site that I want to work behind a reverse proxy (httpd) if using > http:// everything works as expected. If using https:// some content is > displayed but some content is blocked because of stylesheets and etc being > requested via http rather https. > > I know that the long term solution should be to get all code changed so

I''m newbie to mongrel, I''m not able to config mongrel_cluster in order to host multiple web sites added/remove as apache VirtualHost. I followed codahale http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ mixed with Wiki Radiant (I use Radiant as a rails apps to be deployed, 1 domain 1 radiant sites with its own document tree

Hi all, I am out of my head here... I have a 3 node cluster with 10 mongrels running on each. When I deploy, I break all the mongrels every time. I have tried just about everything. I can restart my mongrels without a hitch manually, it''s only when I use cap deploy. Maybe I am missing something here... so if I can get some help it would be appreciated. The errors are the typical mongrel

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

Craig White <craigwhite at azapple.com> wrote: > On Tue, 2008-10-28 at 16:30 -0500, David Miller wrote: > >> > I have a CentOS 5.2 server running Apache 2.2.3 (yum installed) and >> > drupal 6.5 on ESX 3.5. We're using Name Based Virtual Hosting on it - >> > 2 hosts. The problem is that when I pull up a web page after not >> > having accessed

Ok, So I''m running mongrel_cluster behind a hardware load balancer. I don''t have apache running at all, just mongrel_cluster. Does anyone know how I can get cap disable_web/enable_web to work without Apache. With no apache I can''t just make an .htaccess file change like the docs state. has anyone rewritten disable_web/enable_web to work with just mongrel_cluster and

It appears my http setup is working but I am getting an error when I try to use a web browser to connect. All I have done so far is to change the setting from what was working in httpd.conf and move it to ssl.conf (adding some ssl things) and I am using the same directory/set of files that was working for development. The error... Ruby on Rails application could not be started Phusion Passenger

Hi everybody, I just suscribe to the list because I have a problem using mongrel and mongrel_cluster... I setup a server (debian unstable wich provide apache 2.2.3 as a pakage) but I have an error when I try to access my application : ERROR 403 : Forbidden, You don''t have permission to access / on this server. When I check apache''s logs I found that : [warn] proxy: No

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

First off: Our clusters are LVS balanced Apache 2.2.3 + mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a pgcluster backend. On 2 of our deployed clusters, we are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it

Hello all, For the last couple of days I was trying to get my Apache/mod_proxy/mongrel setup to limit the size of the request body. The setup is as follows: 1.) Apache acts as a reverse proxy by facilitating mod_rewrite and mod_proxy 2.) Requests for non-static files are passed on to a mongrel_cluster 3.) We use mongrel for our Ruby on Rails application Note that due to some restrictions we are

Hi folks, I''ve got some BackgroundRB workers to handle a long running task (triggered by a user) that work very well on my staging server, and I just wanted to check to see if anyone had any advice before I put it into production. When I start the worker (which performs an import), I write a record to my database for each import. The record gets updated by the worker to