[amaltemara]

Originally Posted by pguy

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

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...