Re: heroku[router]: Error H12 (Request timeout) causing Application Error
To me it turned out to be the logs. I was hitting my api to get the response and print it out on the log. While it worked perfectly fine for smaller outputs, it raised TimeOut errors for bigger ones. The issue was it took longer than 30 seconds to print the output of request on the logs which railsed the error. So I simply commented the code that prints api output to the logs. Let me know if that Helps :) Best, Pamio Solanky On Wednesday, 18 May 2011 22:30:08 UTC+5:30, joshmckin wrote: Been getting these errors for 2 days now and no reply form Heroku support on the ticket I opened yesterday morning (10 am CST). When I restart the apps the errors subside for a while, but return eventually. Anyone else having this issue? If a heroku employee reads this post PLEASE have someone take action on ticket 23856 its been WAY TOO long of a wait for a response and telling my clients let me try a restart leaves a nasty Windows taste in my mouth. Thanks, -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: heroku[router]: Error H12 (Request timeout) causing Application Error
Hi Sebastien, On our site, we're seeing the same errors without any perceptible cause. Did you find a fix or a cause for the H12 errors you were seeing? Scott On Wednesday, June 27, 2012 10:49:38 AM UTC-4, 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=3ms 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 heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
Re: heroku[router]: Error H12 (Request timeout) causing Application Error
Every single one of these has been a problem with our application. I suggest using NewRelic, which will instrument the requests and show you where you're spending time during those requests that time out. Another idea is to use the https://github.com/kch/rack-timeout gem and set the timeout somewhere at 20 seconds or so. It will raise an exception after 20s of a request and you might get a more useful stack. On Fri, Jan 25, 2013 at 9:39 AM, Scott Messinger sc...@commoncurriculum.com wrote: Hi Sebastien, On our site, we're seeing the same errors without any perceptible cause. Did you find a fix or a cause for the H12 errors you were seeing? Scott On Wednesday, June 27, 2012 10:49:38 AM UTC-4, 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=3ms 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 heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en -- dB. | Moscow - Geneva - Seattle - New York dblock.org http://www.dblock.org - @dblockdotorghttp://twitter.com/#!/dblockdotorg -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
Re: heroku[router]: Error H12 (Request timeout) causing Application Error
Hi Daniel, Thanks for the response. We've been using the rack-timeout gem (timeout of 10 seconds) and have been using NewRelic. We can't find any indication that our app is taking more than 100ms to respond. Granted, this seems odd. However, the logs and new relic tell the same story: a dyno will return a response in 50ms and then, 5 seconds later, heroku will say the dyno has timed out. It's really odd. Any ideas? Scott Scott Messinger *|* Founder, Common Curriculum *|* (360) 904.5947 *|* @scottmessinger *|* www.commoncurriculum.com On Fri, Jan 25, 2013 at 10:01 AM, Daniel Doubrovkine dbl...@dblock.orgwrote: Every single one of these has been a problem with our application. I suggest using NewRelic, which will instrument the requests and show you where you're spending time during those requests that time out. Another idea is to use the https://github.com/kch/rack-timeout gem and set the timeout somewhere at 20 seconds or so. It will raise an exception after 20s of a request and you might get a more useful stack. On Fri, Jan 25, 2013 at 9:39 AM, Scott Messinger sc...@commoncurriculum.com wrote: Hi Sebastien, On our site, we're seeing the same errors without any perceptible cause. Did you find a fix or a cause for the H12 errors you were seeing? Scott On Wednesday, June 27, 2012 10:49:38 AM UTC-4, 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=3ms 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 heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en -- dB. | Moscow - Geneva - Seattle - New York dblock.org http://www.dblock.org - @dblockdotorghttp://twitter.com/#!/dblockdotorg -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
Re: heroku[router]: Error H12 (Request timeout) causing Application Error
Assuming you have more than 1 dyno, the dynos are always up. Then, is this a Rails app? Thin? Unicorn? Heroku round-robins requests, so it's possible that there're 2 requests coming at the same time, and both go to the same dyno. Then your app has a bug where the second request isn't being served, gets stuck, etc? On Fri, Jan 25, 2013 at 10:47 AM, Scott Messinger sc...@commoncurriculum.com wrote: Hi Daniel, Thanks for the response. We've been using the rack-timeout gem (timeout of 10 seconds) and have been using NewRelic. We can't find any indication that our app is taking more than 100ms to respond. Granted, this seems odd. However, the logs and new relic tell the same story: a dyno will return a response in 50ms and then, 5 seconds later, heroku will say the dyno has timed out. It's really odd. Any ideas? Scott Scott Messinger *|* Founder, Common Curriculum *|* (360) 904.5947 *|* @scottmessinger *|* www.commoncurriculum.com On Fri, Jan 25, 2013 at 10:01 AM, Daniel Doubrovkine dbl...@dblock.orgwrote: Every single one of these has been a problem with our application. I suggest using NewRelic, which will instrument the requests and show you where you're spending time during those requests that time out. Another idea is to use the https://github.com/kch/rack-timeout gem and set the timeout somewhere at 20 seconds or so. It will raise an exception after 20s of a request and you might get a more useful stack. On Fri, Jan 25, 2013 at 9:39 AM, Scott Messinger sc...@commoncurriculum.com wrote: Hi Sebastien, On our site, we're seeing the same errors without any perceptible cause. Did you find a fix or a cause for the H12 errors you were seeing? Scott On Wednesday, June 27, 2012 10:49:38 AM UTC-4, 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=3ms 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 heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en -- dB. | Moscow - Geneva - Seattle - New York dblock.org http://www.dblock.org - @dblockdotorghttp://twitter.com/#!/dblockdotorg -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en -- dB. | Moscow - Geneva - Seattle - New York dblock.org http://www.dblock.org - @dblockdotorghttp://twitter.com/#!/dblockdotorg -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
Re: heroku[router]: Error H12 (Request timeout) causing Application Error
Hi i'm having the same issue basically. Error H12 (Request timeout) - GET *.herokuapp.com/ dyno=web.1 queue= wait= service=3ms 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 heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
Re: heroku[router]: Error H12 (Request timeout) causing Application Error
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=3ms 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 heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
Re: heroku[router]: Error H12 (Request timeout) causing Application Error
Usually that error means that, y'know, your app is timing out. As in, something is taking a real long time to run... in your code... not in heroku's. And for whatever reason that is being fixed with a restart. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
