Technology Insights

503 Service Unavailable Error After Switching Litespeed Rails Site From Production Mode To Staging Mode

Earlier I switched one of the Litespeed web server virtual hosts from production mode to staging mode and after gracefully restarting rails was receiving a 503 Service Unavailable error. Initially I thought that maybe Litespeed had to be restarted completely instead of just a graceful restart but that produced the same results. Below I describe the errors including errors in the Litespeed logs as well as how to resolve the issue which ended up being a silly mistake on my part.

Technology Insights

Setting Up Redmine: SVN Repositories Timing Out When Attempting to View

When setting up Redmine as a project management system you might run into an issue after configuring the SVN repository for a project. If the SVN project already exists and there are a bunch of commits typically when browsing to the repository for the first time it will time out. Usually when it does time out it will display in your browser as a 503 error. Below I discuss configuring the SVN repository and then running a rake task to resolve the browser time out issue.

First lets set up the SVN repository following the directions below.

  1. Open Redmine Project: After you have created a Redmine project that the SVN repository will belong to browse to that project  in a browser.

Technology Errors

connection to [uds://tmp/lshttpd/example-site:_.sock] on request #0, error: Connection timed out!

I noticed this error during a deployment of numerous servers that were configured with litespeed, postgreSQL, and ruby. The installation process was to install ruby, install ruby gems, install postgreSQL, install litespeed, and then sync up the web directory using SVN. After doing so connect via a browser to the server to test things out. On one server I was getting a “503 Service Unavailable” error. The lshttpd(litespeed) logs looked like the below example.