similar to: Status: 500 Internal Server Error

So I have updated to the latest mongrel and fastthread and my environment is as follows: Debian 3.1 Rails 1.1.6 Ruby 1.8.5 Mongrel 0.3.18 Fastthread 0.4 Mongrel Cluster 0.2.1 Apache 2.2.3 I again woke up this morning to my disappointment of seeing the strange Status: 500 Internal Server error. It happens the same every morning, I have three mongrels running, two give the error, one

I''m trying to get a rails app running with this configuration: Mongrel, Apache 2.2, mod_proxy load balancer and Rails 1.1.6 error I have a rails app on another server working with (apparantly) the same configuration and it runs fine so I''m stumped. I''m wondering if anyone has any insight into the error I have pasted below. It seems to be one of those errors that

This release of Instant Rails contains the following major changes: * Upgrades Rails to version 1.1.6 (other components upgraded to current release, also) * SCGI has been replaced by Mongrel (using Apache''s mod_proxy for forward requests). * For the development server, WEBrick has also been replaced by Mongrel. * Automatic RadRails configuration: if

I''m in the process of setting up a mongrel cluster at the moment, and I''m running into a bit of an issue. Even worse is that I''m not sure whether this is a mongrel thing, or an Apache thing. While I''m inclined to think that this might be a balancer thing, I decided there was a higher chance hearing back from mongrel-users than from apache-users, so I''d

This is the final release for Instant Rails 1.4. It corrects the two known problems with the preview1 release (two help menu items caused Instant Rails to crash). Instant Rails 1.4 contains the following major changes: * Upgrades Rails to version 1.1.6 (other components upgraded to current release, also) * SCGI has been replaced by Mongrel (using Apache''s mod_proxy for

Dear all, Does anybody know if there''s problem with ferret running with mongrel ? I got unpredictable segfaults. Everything works well with fastcgi instead of mongrel. I use ruby 1.8.5, apache 2, mod proxy, mongrel 0.3.13.4, ferret 0.10.13 and rails 1.1.6 Thanks, Johan Johan Duflost Analyst Programmer Belgian Biodiversity Platform ( http://www.biodiversity.be) Belgian Federal

Hi mongrel-users, Just a heads up for apache2.2 mod_proxy + mongrel + rails users: If you have a line like this in your source (because you''ve done a poor job maintaining your code and reading the API docs): render ''foo'', :layout => ''bar'' You might expect it to do what it says... but it actually sets deprecated_status and ends up setting

Hi, I have attempted to install radiant on my server using mongrel. I have it working fine using lighttpd on my development box, but as soon as i attempt to run it using mongrel I get the following error: NoMethodError (undefined method `find'' for Status:Class): /app/models/page.rb:49:in `status'' /app/models/page.rb:57:in `published?''

We have a Centos server with a number of virtual hosts, and my rails app runs under one of those virtual hosts using mongrel_rails. The app lives in /home/mydomain/railsapp where /home/mydomain/railsapp/public is the rails root. It runs under mongrel on port 8008, so to get to it users invoke the url http://www.mydomain.com:8008/ - all is fine to this point. Now I have some users whose

Hey again :) I have this weird issue on Windows. I''ve installed mongrel_cluster and friends, and I''m trying to get a cluster up and running. Here''s my mongrel_cluster.yml: ------------ --- port: 8000 environment: production address: 127.0.0.1 pid_file: log/mongrel.pid servers: 10 cwd: c:/railstest docroot: public log_file: log/mongrel.log ------------ I''ve

For some users, request.remote_ip always return nil. According to the RAILS''s help: REMOTE_ADDR is the standard but will fail if the user is behind a proxy. HTTP_CLIENT_IP and/or HTTP_X_FORWARDED_FOR are set by proxies so check for these before falling back to REMOTE_ADDR. HTTP_X_FORWARDED_FOR may be a comma- delimited list in the case of multiple chained proxies; the first is the

FYI: I don''t think this is a very well know. It seems that, on some operating systems, ActionMailer/SMTP crashes when it sends an email with only a ''.'' (aka a ''dot'' or a ''period''). Specifically, you get Net::SMTPSyntaxError (502 Error: command not implemented): Environment Details: $ uname -a Linux private1 2.6.15-26-server #1 SMP

ngw@adreadedsunnyday ~/projects/hotchalk$ script/server ./script/../config/boot.rb:28:Warning: require_gem is obsolete. Use gem instead. /opt/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:606: superclass mismatch for class OrderedOptions (TypeError) from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/ custom_require.rb:27:in `gem_original_require'' from

I am trying to move a Rails application, that uses SSL, from an Apache/FastCGI stack, that works fine, to Apache22 and mongrel working with a single mongrel instance (i.e., not mongrel cluster, yet.) I have a single mongrel instance demonized and working fine on http, on port 3000. Apache/OpenSSL/certs working fine. Here is my test http.conf (deliberately kept as simple as possible):

I just moved from apache2/fcgi to apache2.2/mongrel and everything seems to work great except for 2 issues, one being major and one minor. the major issue i am experiencing is that after a period of time where my rails apps are not used, typically overnight, the mongrel processes become unresponsive. I currently have 3 apps running behind an apache2.2 proxy. every morning when i come in to

Hi Guys, I know this is slightly off topic, but it''d be great to get some feedback from anyone who''s using mod_proxy on Apache 2.2 to redircet to a rails app on mongrel. Everything has been running fine generally but a few days back we started getting a gap in the performance between the Apache port and the mongrel port. accessing through port 80 was averaging ten times longer

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''d like to run the Mongrel prerelease (0.3.13.4 prerelease) and mongrel_cluster 0.2.1 on my shared host (which doesn''t want to install prerelease software for all to use). I can install the gems in my own directory, and run mongrel 0.3.13.4 with --prefix just fine. However, I think due to the GemPlugin structure, even my new mongrel_rails loads up

This is not directly a Rails question but you lot seem the best to ask... I have a strong feeling we will be developing future apps in Rails (Ruby fans are slowly starting to outnumber cynics in my office) so I want a web server plan that will be appropriate for that. We have just bought two new web servers I want to turn into a load-balanced, redundant pair. As well as any Rails

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, I''m using Mongrel in a project and experiencing a strange failure under the following circumstances: I''m running on Debian sarge, using the ruby 1.8.5-3 packages from testing, and Mongrel 0.3.13.4. The application serves a number of flash files that are not in a directory available through the web--they are served by a