For us it turned out we were running out available connection to RDS. We had a similar issue a few weeks ago and again it turned out to be RDS, but this time we ran out of space and the alerts were not properly configured. When you have DB issues on Heroku they can sometimes be hard to identify initially, since the heroku logs often do not show more than just the Error H... It sometime helps to view the Rails app log file itself http://stackoverflow.com/questions/2671454/heroku-how-to-see-all-the-logs
If you are making call to external services make sure you add custom NewRelic watchers to see if those service response times are causing issue. When thing go south and status.heroku.com is in the clear, start checking your external services first. Make sure you DB is good and any external calls are not too slow. On Wednesday, June 27, 2012 9:49:38 AM UTC-5, Sébastien VIAN wrote: > > Hi i'm having the same issue basically. > > Error H12 (Request timeout) -> GET *****.herokuapp.com/ dyno=web.1 queue= > wait= service=30000ms status=503 bytes=0 CRIT > > Random request timeout. Monitoring this in New relic I see that after this > kind of error my app is going down for 1 hour or more and then start work > fine again. > > I must say that I'm on devellopment so I run the app on a single dyno.(I > tried to scale up to 3 but nothing changed). > althought I'm the only visitor (testor) of my app so there is no way that > I drawning my dyno under requests... > > I really don't understand what is going on and the error message are not > helping neither is google.... > > I like heroku very much but this is critical and I'm starting to doubt > wether heroku is a fine solution for production. > > Any kind of help would be very much appreciated. > > > sebastien. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
