I have this site set up as a Virtual Host, Rails is set up as an External App, LSAPI, with these settings:
Max Connections: 10
Environment: RAILS_ENV=production LSAPI_CHILDREN=10
Initial Request Timeout: 30
Retry Timeout: 30
Persistent Connection: Yes
Connection Keepalive Timeout: 20
Response Buffering: No
Auto Start: Yes
Instances: 2
Run On Start Up: Yes

Under Context: Rails, configuration:
Max Connections: 20

Anyone know what I'm doing wrong??? I need this app to be rock-solid, and not give any errors like this...

Even we've faced tons of 503 issues - but there is just no clear solution and we still face it intermittently. If it continues, we may have to leave litespeed and go to passenger/apache combo

Click to expand...

Surely there's a way to troubleshoot exactly where the 503 is coming from???

When there's an error in the Rails application, and I get a 503, I know it's the rails app because I execute:
# RAILS_ENV=production script/console
from the command line, and I get whatever nasty bug that pops up...

Is there a way for me to get an email notification on these 503 errors, and why they occur? Or see it in some logfile? I'm not seeing them in the logs right now...

please download the 4.0.4 release package and give it try. It should not give 503 errors when LSWS need to start a Rails application on demand.
Just change the version number in the download link to get it.

please download the 4.0.4 release package and give it try. It should not give 503 errors when LSWS need to start a Rails application on demand.
Just change the version number in the download link to get it.