Sorry, I wasn't clear. Does it happen on a certain portion of the site or is it pretty random? Also, is it reproducible in development or is it a production issue? If you're at your wits end, you could use before_filter to log any and all hits to controllers and actions. If it your code is OK, then the timeouts are happening on the DB server or there's a communication problem between the app servers and the DB server.
HTH On Sep 11, 5:05 pm, Jack Christensen <[EMAIL PROTECTED]> wrote: > Srdjan Pejic wrote: > > Does it happen on a certain action or when accessing actions in a > > certain controller? > > That's what I'm trying to find out. The request never finishes so > examining the log file is of limited help. > > > > > On Sep 11, 4:17 pm, Jack Christensen <[EMAIL PROTECTED]> wrote: > > >> Occasionally, my server gets nearly completely unresponsive. Nearly the > >> entire CPU usage is spent in IO wait. I'm forced to kill the ruby > >> processes to get the server back up. The log files are not very useful > >> because the request never finishes so I can't simply search for requests > >> that took at least x seconds. Are there any tools are techniques to > >> determine what request is currently in progress? > > >> I'm running Apache 2.2 and Passenger. > > >> Thanks. > > >> -- > >> Jack Christensen > >> [EMAIL PROTECTED] > > -- > Jack Christensen > [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
