Hi, I've just run into this problem. Will check out the resources you linked to Peter but I am curious about the status of this issue.
I clicked Andrew's link to his support ticket, but was unauthorized by heroku to view it. Thanks - Luke On Tuesday, November 27, 2012 12:24:14 AM UTC-5, Peter van Hardenberg wrote: > > Hi all, > > we're tracking some issues with the new `heroku-postgres` plans that are > affecting a couple of the database clusters. One immediate step you can > take is to implement reconnection logic in your dyno. This is good practice > no matter what your app is doing (and is something we're hoping to see > permanently fixed in Rails 4 -- see this thread > https://github.com/rails/rails/pull/6557 ) There's some discussion of how > to monkeypatch your way around this problem here: > https://github.com/rails/rails/issues/3392 > > Sorry about the inconvenience. We're working on understanding the issue, > but as a note, if you're running a production app, we definitely recommend > a production tier database (crane or above). That said, we do think fixing > this is important, and we're on the case. > > Best, > Peter van Hardenberg > Heroku Postgres > > > On Mon, Nov 26, 2012 at 6:54 PM, Wendy Friedlander < > [email protected] <javascript:>> wrote: > >> Hi Andrew, >> >> Have you had any luck with this? I've had the same problem as well -- >> first error is connection time out and the next is eof detected. The site >> is then down for a while... happened twice today, took 16 min to resolve. >> At least now I know I can do 'heroku restart' I hadn't thought of that. It >> has only happened since the db update as well. >> >> Please let me know what you've learned. Thanks! >> >> -Wendy >> >> >> >> On Wednesday, November 21, 2012 11:20:07 AM UTC-5, Andrew Lorente wrote: >>> >>> I've been having intermittent pg connection problems since my app was >>> migrated to the new database setup. I'll get a pair of exceptions (see >>> below). Sometimes the problem fixes itself in a couple of minutes; other >>> times I have to do a `heroku restart`. >>> >>> The first exception that comes through is a "connection timeout:" >>> >>> A ActiveRecord::StatementInvalid occurred in posts#index: >>> >>> PG::Error: SSL SYSCALL error: Connection timed out >>> : SELECT "posts".* FROM "posts" WHERE (published_at < '2012-11-21 >>> 15:43:06.226910') ORDER BY posts.published_at DESC LIMIT 15 >>> vendor/bundle/ruby/1.9.1/gems/ >>> activerecord-3.2.1/lib/active_**record/connection_adapters/pos**tgresql_adapter.rb:1106:in >>> >>> `async_exec' >>> >>> The second exception is an "EOF Detected:" >>> >>> A ActiveRecord::StatementInvalid occurred in posts#index: >>> >>> PG::Error: SSL SYSCALL error: EOF detected >>> : SELECT "posts".* FROM "posts" WHERE (published_at < '2012-11-21 >>> 15:58:42.070747') ORDER BY posts.published_at DESC LIMIT 15 >>> vendor/bundle/ruby/1.9.1/gems/ >>> activerecord-3.2.1/lib/active_**record/connection_adapters/pos**tgresql_adapter.rb:1106:in >>> >>> `async_exec' >>> >>> They always come in pairs like that (on subsequent requests). >>> >>> I'm not sure what else to look up to help figure this out. Any ideas? >>> >>> Thanks, >>> Andrew >>> >> -- >> You received this message because you are subscribed to the Google >> Groups "Heroku" group. >> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> 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 [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
