FCGID timeout causing Rails 500 errors

The default timeout for FCGID is pretty low I think (maybe 5-10 seconds). This was causing me SO much grief that I was just about to lose it. I found these posts out there that helped a lot:

http://wiki.rubyonrails.org/rails/pages/Debian+mod_fastcgi+Notes

http://weblog.rubyonrails.com/2005/01/03/watch-for-huge-requests-on-default-fcgi

Of course Ubuntu uses different config locations and such for FCGID, but the configuration names are the same.

I set my timeouts to 2 minutes just to be safe. Besides for an admin application, I could wait for a long time without thinking things were amiss. Anyways, help that helps prevent some folks from losing their minds.

3 thoughts on “FCGID timeout causing Rails 500 errors

  1. psst…use mongrel – fastcgi is painful enogh to configure, and (for me at least) it was dog slow compared to running a mongrel cluster.

    Took a look and since I’m going to be adding SSL, Mongrel looks just as hard to configure as FastCGI. I still have to use Apache, plus starting up a number of Mongrel instances, and mod balancer. Am I missing something? Or is the goal speed? Is Mongrel like uber fast?

    Like

  2. He’s not using mod_fastcgi–he’s using mod_fcgid, a completely different beast, which happens to be much more stable and more scalable (than both fastcgi and mongrel, in my experience.)

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s