similar to: Mongrel not allowing URIs > 512 chars

I transferred a site from Lighty+SCGI to Lighty+Mongrel, and now I''m having problems with it becoming unresponsive. It works fine for about 10-15 minutes, but then attempts to access the site just stall forever. Nothing is written in any of lighty''s or mongrel''s logs. Here''s my lighty config: $HTTP["host"] =~ "www.xyz.com" {

Hello all, I''m using Lighty-Win32 and Mongrel. I have one rails app working against http://hostname/. I want to know how to route lighty and my app to http://hostname/appname1. I have multiple apps that I would eventually want to route with http://hostname/appname2, http://hostname/appname3, etc. I am not trying to "productize", these are separate distinct apps that

Hi guys, I''ve been chasing a problem in my web-stack: Lighttpd -> Mongrel -> Rails, and found a problem with the interaction of Lighttpd and Mongrel. If a request takes more than 5 seconds, Lighty will retry it - and then the requests / responses get mixed up in Lighty and it returns a bad response to the client. Not good. I''m convinced that the problem is

I need to graft some rails apps onto a website running apache 1.3 and I must be missing something very obvious because I cannot get things working properly. Here is what I need: 1) The server must be running apache 1.3. A very large body of PHP content is currently vended by the server through 5 vhosts and I have neither the time nor resources to replace apache1 with apache2 or lighttpd. Maybe

On httpd I use ProxyPass and ProxyPassReverse to forward requests to webrick and mongrel. How can I do this same thing using Lighty and Mongrel? Thanks, Joe -- Posted via http://www.ruby-forum.com/.

I''m not sure if it''s due to setting up multiple mongrel servers and proxying them with lighty, but something is keeping postgres connections around. I only have a couple Rails apps running on a new server, with not a whole lot of traffic, yet today I actually maxed out my connection limit of 100 for postgres. How do I turn off persistent connections in Mongrel? Joe --

I was about to write a long post about how I couldn''t get request.ssl?to work in Rails behind Pound and Mongrel, but then I figured it out. In your pound.cfg file, just add: HTTPSHeaders 1 "X-Forwarded-Proto: https" Assuming you''ve got Pound working correctly with SSL, this will giveRails the header it''s looking for. If there''s any interest in a Debian

If I do this GET request: GET /comments/new?description_id=1 HTTP/1.1 what ends up in request.request_uri is different for mongrel and webrick: Mongrel: "/comments/new" Webrick: "/comments/new?description_id=1" The mongrel behaviour breaks my app because I''m storing the uri to redirect to it later. Mongrel even logs the request as: 127.0.0.1 - [Mon, 17 Jul 2006

Is anyone using the setup described at the Rails blog? http://weblog.rubyonrails.org/2006/7/3/pound-makes-lighty-and-mongrel- play-nice I''m using it in production, and the only problem I have is the same as people have described in the comments over there, namely that Rails thinks all requests come from localhost. See http://isabont.com/requestinfo for the headers. Any

Just so you know, I''ve read the manual :) http://mongrel.rubyforge.org/docs/choosing_deployment.html No php or ssl needed - that is me - simple. So I should be good to go but thought I''d ask. BTW, sorry about the stupid subject. Listening to BNL, you know ;) On 6/27/06, mongrel-users-request at rubyforge.org <mongrel-users-request at rubyforge.org> wrote: > Send

Hi All, I want to know thoughts on if I am being to paranoid/security conscious. CentOS 5.6, Apache, MySQL, running an Firewall in front of everything and obviously the built-in firewall on the box. I have ssh on a different port and starting to use Keys instead of password authentication. I host an intensive website and I am getting about 150 unique visitors per day. What I am seeing is

I have an action which requests another URL from the same site (for testing purposes), but it keeps timing out. If I use an off-site URL, the action works fine. I also notice that I''m only able to request one page at a time from my server - the rest just spin until the previous requests complete. Is this some setting in Lighty, Mongrel, or my browser (Firefox - I played around with

Has anyone ever experienced this problem? Every 12-24 hours *one of* my mongrel processes gets a TERM signal and quits. There is all I get in my mongrel log.. ** Mongrel available at 0.0.0.0:8003 ** TERM signal received. And my rails-log is silent too. No request starting. Just the end of a successful request and then nothingness. The other processes are doing just fine and stay up for good.

I have an existing rails application on lighttpd and I am trrying to upgrade to mongrel for the enhanced scalability it offers. I am running mongrel 1.1.1, rails 1.2.5, lighttpd 1.4.13 and ruby 1.8.5 Everything is working great except request.remote_ip returns 127.0.0.1 or 192.168.0.102 (the internal network address of the server running lighty). I''ve seen some older posts about

I''m wondering if anyone has built a Capistrano task that will deploy mongrel either standalone or along with a rails app. I''ve been looking at possibilities for doing this but still new to using both having switched from using FCGI+Lighty and deploying by hand. Thanks, Curtis

I am running mongrel-0.3.13.1. Have used lighty and fcgi in the past, and I must say that apache-2.0.x proxying to mongrel is much nicer to deal with! I am having this problem, however. If I am in root''s homedirectory, and start mongrel with this command: --------- mongrel_rails start -a 127.0.0.1 -e production -c /home/www/rails/myapp -l log/mongrel.log --user mongrel --group mongrel

Hi, I''m attempting to migrate an app from Apache+FCGI to Apache+Mongrel. I''m using Apache 2.0 with the latest Mongrel release. I''m having an issue with the Mint stats package and Mongrel not picking up the following url: /mint/?js Basically inside the /mint folder there is an index.php, so the url /mint/?js should really be going to /mint/index.php?js When I had my

Hi Everyone, I was setting up Lighty+Fcgi on our server for last *couple* ( read zillion ) of hours. I had posted my problems in my previous email. But all in vain.. So, for time being, I switched to Mongrel. And the performance seemed quite good. This is the first time ever I''m using mongrel ( Awesome stuff ZedShaw..Thanks! ). I''m wondering if there are many people around

Hi all. I''m trying to skip the Rails page cache if the user is logged in: --- # Rewrite index to check for static RewriteCond %{HTTP_COOKIE} !^.*logged_in=yes.*$ RewriteRule ^/$ /index.html [QSA] # Rewrite to check for Rails cached page RewriteCond %{HTTP_COOKIE} !^.*logged_in=yes.*$ RewriteRule ^([^.]+)$ $1.html [QSA] # Redirect all non-static requests to cluster RewriteCond

Hello Zed ! I''ve experimented a simple but limited performance tweak in the mongrel rails loader. With the following apache 2.2 mod proxy loadbalancer setup : # Redirect all non-static requests to cluster RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L] We can assume that mongrel is called only when the