passenger

I am hosting a Ruby on Rails 2.0.2 application on DreamHost. It is on an Apache 2 server, running on top of Phusion Passenger. The application often returns a 500 error "Rails application failed to start properly", but at random times. It appears to happen when the application is under higher load, though I can't confirm this. It only gets about 2,000 pageviews per day, so I don't think load should really be an issue. The Apache logs correlate these 500 responses with the error: "Premature end of script headers". Just looking at the logs at 9 AM today, the error appears as often as three or

Is there any limit of the POST request size in apache? What is the default value of this limit and is there any way to increase it? If it matters, Rails application is started on this server using passenger. The limit in Apache is set via the LimitRequestBody directive and defaults to 0 : This directive specifies the number of bytes from 0 (meaning unlimited) to 2147483647 (2GB) that are allowed in a request body. Take a look at the full description of Apache's LimitRequestBody directive . Besides that Rails may impose a limit itself (cant't tell though b/c I've never programmed in Ruby). 来源：

I am in the process of setting up a server to run a Ruby on Rails application on Fedora 12, using Passenger. I am at the stage where I've installed Passenger, set it up as prescribed, but get the following errors when I restart Apache: [Wed Jan 13 15:41:38 2010] [notice] caught SIGTERM, shutting down [Wed Jan 13 15:41:40 2010] [notice] SELinux policy enabled; httpd running as context unconfined_u:system_r:httpd_t:s0 [Wed Jan 13 15:41:40 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Jan 13 15:41:40 2010] [error] *** Passenger could not be initialized because of this

I'm in the process of updating a Rails 3 app to use Rails 3.1 and as part of that, am making use of the new asset pipeline. So far, I've got everything working apart from one rather annoying problem I can't solve. The application and all its assets works fine in development, but in production it is deployed to a sub-URI using Passenger ( http://the-host/sub-uri/ ). The problem with this is that the assets are pre-compiled during deployment and one of my CSS (well, it's a .css.scss file) files is making use of the image-url helper from the sass-rails gem. Since during the pre-compilation

Does anyone know a good solution to limit the file upload size when running a Rails application with Passenger/mod_rails. The request should immediately be declined, so that the file doesn't get transferred to the server. The solutions I've found so far all describe how to patch Mongrel to implement a limitation, but I have to use passenger with this application. Or if you're using nginx with passenger, add in the server block: server { client_max_body_size 100M; } http://wiki.nginx.org/NginxHttpCoreModule#client_max_body_size You may cap the upload size via Apache using the LimitRequestBody

i am trying to deploy rails3 apps with the latest phusion passenger 2.2.11 and ruby-enterprise-1.8.7-2010.01. i am using bundler, but passenger seems to not be able to find the .bundle dir. error message: git://github.com/rails/rails.git (at master) is not checked out. Please run `bundle install` (Bundler::PathError) where do i install the .bundle? where do i tell passenger which bundle to use? any hints? thanks! i think the command you are searching for is bundle pack which will move your gems from the .bundle directory to the vendor/cache. see yehuda katz' posting about bundler workflows on