Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
litespeed_wiki:ruby_debug [2015/07/29 13:51] Michael Alegre removed |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== How to inspect a live Ruby process ====== | ||
| - | |||
| - | Sometime your Rails application might appear to not work well with LiteSpeed. This may or may not the fault of our ruby-lsapi module. Almost always, it's a problem on the application/configuration end. Before we look into the problem, you need to find out exactly what is the root cause of the problem. | ||
| - | |||
| - | To debug a live ruby process, please have a look | ||
| - | [[http://eigenclass.org/hiki.rb?ruby+live+process+introspection|Here]]. | ||
| - | |||
| - | Common problems and solutions: | ||
| - | * More and more ruby processes spawn, hang, and does nothing. | ||
| - | |||
| - | This can be caused by a search query using the ruby-google module. Both http-access and http-access2 can get stuck waiting 'forever' for a google.com (or anywhere) for a response. | ||
| - | The solution was to wrap it, or any operations that can block Ruby, in a Timeout::timeout(5) do() clause. | ||
| - | |||
| - | |||
| - | |||