I've seen this problem on a few of my app's on Heroku; caused by a long running request (in my case twitter omni auth callbacks) which Heroku times out raising a H12 Timeout error, and cut's the processes off from the real world.
The issue (for me) is the dyno(s) don't get killed but can never complete the request, so Heroku thinks you have no dyno(s) ready to serve and just keeps timing out new requests. I've had to work round it with the rack timeout exception too. Jon Rowe ----------------------------- [email protected] jonrowe.co.uk On Thursday, 6 December 2012 at 13:03, Iain Beeston wrote: > Lately we've had problems with the web-server processes in our rails 3.1 app > intermittently stop responding. We haven't been able to work out why (no > exceptions, high cpu or memory usage or networking calls) - it just seems > like every few days one them just randomly hangs and never recovers. The > process is still there, but not responding to requests and everything sent to > it times out. We're using heroku so our logging options are limited. > > So, I was wondering - what do people use to keep their servers responsive? > (Especially on "hands-off" platforms like heroku) How common is it to > routinely restart processes? (Sounds like the wrong solution to me, but some > people recommend it) > > > Iain Beeston > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
