connection to [uds://tmp/lshttpd/example-site:_.sock] on request #0, error: Connection timed out!
Posted by: alex in ErrorsI 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.
2008-09-30 03:31:09.201 [INFO] Pid: 9242 associated with [Rails:example-site:/]
2008-09-30 03:31:09.201 [INFO] [Rails:example-site:/] pid list size: 0, pid stop list size: 0
2008-09-30 03:31:09.201 [NOTICE] [Rails:example-site:/] stop worker processes
2008-09-30 03:31:09.201 [INFO] [Rails:example-site:/] 1 request being processed, kill external app later.
2008-09-30 03:31:09.201 [INFO] [10.0.0.10:3664-0#example-site] connection to [uds://tmp/lshttpd/example-site:_.sock] on request #0, error: Connection reset by peer!
2008-09-30 03:31:09.203 [INFO] [Rails:example-site:/] add child process pid: 9268
2008-09-30 03:31:09.203 [INFO] [Rails:example-site:/] pid list size: 1
2008-09-30 03:31:19.024 [INFO] [10.0.0.10:3664-0#example-site] No request delivery notification has been received from LSAPI process:-2, possible run away process.
2008-09-30 03:31:19.024 [INFO] [10.0.0.10:3664-0#example-site] connection to [uds://tmp/lshttpd/example-site:_.sock] on request #0, error: Connection timed out!
2008-09-30 03:31:19.025 [NOTICE] [10.0.0.10:3664-0#example-site] oops! 503 Service Unavailable
2008-09-30 03:31:19.025 [NOTICE] [10.0.0.10:3664-0#example-site] Content len: 0, Request line:
After a bit of searching I pinned the issue down to having missed installing one of the ruby gems. If you are in this situation use the “gem list” command to list all of the gems on the server and make sire that you are not trying to load gems that are not installed. Once the missing gem was installed there were no more 503 errors and things were rocking.
Tags: 503, gem, lighttpd, Litespeed, PostgreSQL, rails, Ruby, Service Unavailable, svn
Entries (RSS)