Postgres error on Heroku with Resque

Question

I don't know enough Postgres to understand the message.

PG::Error: SSL error: decryption failed or bad record mac : SELECT a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull FROM pg_attribute a LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum WHERE a.attrelid = '"users"'::regclass AND a.attnum > 0 AND NOT a.attisdropped ORDER BY a.attnum

And here is the callstack got from the resque backend

/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/connection_adapters/postgresql_adapter.rb:1139:in `async_exec'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/connection_adapters/postgresql_adapter.rb:1139:in `exec_no_cache'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/connection_adapters/postgresql_adapter.rb:663:in `block in exec_query'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:280:in `block in log'
/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.2/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/connection_adapters/abstract_adapter.rb:275:in `log'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/connection_adapters/postgresql_adapter.rb:662:in `exec_query'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/connection_adapters/postgresql_adapter.rb:1264:in `column_definitions'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/connection_adapters/postgresql_adapter.rb:858:in `columns'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/connection_adapters/schema_cache.rb:12:in `block in initialize'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/model_schema.rb:228:in `yield'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/model_schema.rb:228:in `default'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/model_schema.rb:228:in `columns'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/model_schema.rb:237:in `columns_hash'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/relation/delegation.rb:7:in `columns_hash'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/relation/finder_methods.rb:330:in `find_one'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/relation/finder_methods.rb:311:in `find_with_ids'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/relation/finder_methods.rb:107:in `find'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.2/lib/active_record/querying.rb:5:in `find'
/app/app/workers/compute_worker.rb:5:in `perform'

Explanation: My worker is only doing some writing operations into the databases. Nothing complicated. When I execute the worker's task for the first time, it works, and the second time it fails with the above message. If I restart the worker, it will work only the first time. I already run

heroku pg:restart
heroku db:restart
heroku db:migrate

... without success.

On my local computer(using mysql) it works perfectly. Any idea ?

Take a look at your column types in MySQL. Maybe you have not specified one column. I have had a similar error(long time ago) — Rails beginner
– Rails beginner, Commented Apr 1, 2012 at 1:13
That query is what ActiveRecord uses to figure out the structure of a PostgreSQL table. The error has appeared elsewhere on SO. — mu is too short
– mu is too short, Commented Apr 1, 2012 at 1:31
Thanks for your comments. In fact I don't understand why it works the first time and fails as of the second time. I'm not using taps. Why should I use it ? — Arkan
– Arkan, Commented Apr 1, 2012 at 12:41

Arkan · Accepted Answer · 2012-04-01 13:57:14Z

14

Thanks to the comments of "Rails beginner" and "mu is too short" I found the solution.

I've added this to an initializer and it did the trick!

Resque.after_fork = Proc.new { ActiveRecord::Base.establish_connection }

answered Apr 1, 2012 at 13:57

Arkan

6,2263 gold badges40 silver badges54 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Paul Pettengill Over a year ago

It actually required before_fork for my issue, so my solution ended up like this.

rockusbacchus Over a year ago

Arkan - this solution saved my life. Well, at least my weekend.

Paul Pettengill · Accepted Answer · 2012-04-07 10:58:59Z

7

I had the same issue, but to solve it my app actually required a before_fork and not an after_fork. Hope this helps someone.

Resque.before_fork = Proc.new { ActiveRecord::Base.establish_connection }

answered Apr 7, 2012 at 10:58

Paul Pettengill

4,8651 gold badge31 silver badges34 bronze badges

1 Comment

Bnicholas Over a year ago

This was the case for me on heroku

markquezada · Accepted Answer · 2013-05-09 01:23:11Z

4

This article from heroku explains how to properly connect and disconnect connections for resque:

Resque.before_fork do
  defined?(ActiveRecord::Base) and
    ActiveRecord::Base.connection.disconnect!
end

Resque.after_fork do
  defined?(ActiveRecord::Base) and
    ActiveRecord::Base.establish_connection
end

answered May 9, 2013 at 1:23

markquezada

8,5656 gold badges47 silver badges53 bronze badges

Comments

Stephan · Accepted Answer · 2012-10-22 12:02:00Z

2

Resque.before_fork = Proc.new { 
     ActiveRecord::ActiveRecord::Base.verify_active_connections!
}

would be even nicer

edited Oct 22, 2012 at 12:02

Stephan

43.2k69 gold badges245 silver badges342 bronze badges

answered Oct 22, 2012 at 11:41

Rob

211 bronze badge

1 Comment

MegaTux Over a year ago

#verify_active_connections! was removed . In rails 4 you can use ActiveRecord::Base.clear_active_connections!

Collectives™ on Stack Overflow

Postgres error on Heroku with Resque

4 Answers 4

2 Comments

1 Comment

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

2 Comments

1 Comment

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related