Rails - Aug 2011 - FYI: Heroku Cedar, pg, openssl, omniauth, troubles and a solution

Hi guys,

I found a really nasty issue that affects people running on Heroku''s
cedar
stack. We are using Rails 3.1.rc5, pg 11, omniauth 2.6. Ruby is 1.9.2.180p

Basically there is an incompatibility between the http, pg  and OpenSSL
modules which segfaults when making https calls, for example to log in
through twitter. Now pg is a required gem when using Heroku cedar stack so
leaving that one out is not an option. What fixed this was to add the
following to my config.ru at the top:

require ''pg''
require ''openssl''

This ensures that pg is required before openssl and all is good now.

Hope this helps others in similar situations.

Best
Martin

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.

FWIW, I ran into this back on (I think) rc1 and had the problem locally as well.
There was a bug noted somewhere on the ruby bug tracker relating to it - sorry I
don''t have the url offhand. Thanks very much for the fix - good to
know!

Best Wishes,
Peter

On Aug 3, 2011, at 3:13 AM, Martin Wawrusch wrote:
> Hi guys,
> 
> I found a really nasty issue that affects people running on
Heroku''s cedar stack. We are using Rails 3.1.rc5, pg 11, omniauth 2.6.
Ruby is 1.9.2.180p
> 
> Basically there is an incompatibility between the http, pg  and OpenSSL
modules which segfaults when making https calls, for example to log in through
twitter. Now pg is a required gem when using Heroku cedar stack so leaving that
one out is not an option. What fixed this was to add the following to my
config.ru at the top:
> 
> require ''pg''
> require ''openssl''
> 
> This ensures that pg is required before openssl and all is good now.
> 
> Hope this helps others in similar situations.
> 
> Best
> Martin
> 
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
> To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.

On Wed, Aug 3, 2011 at 12:13 AM, Martin Wawrusch
<martin-qs6+VQBngv1Wk0Htik3J/w@public.gmane.org>wrote:
> Hi guys,
>
> I found a really nasty issue that affects people running on
Heroku''s cedar
> stack. We are using Rails 3.1.rc5, pg 11, omniauth 2.6. Ruby is 1.9.2.180p
>
> Basically there is an incompatibility between the http, pg  and OpenSSL
> modules which segfaults when making https calls, for example to log in
> through twitter. Now pg is a required gem when using Heroku cedar stack so
> leaving that one out is not an option. What fixed this was to add the
> following to my config.ru at the top:
>
> require ''pg''
> require ''openssl''
>
> This ensures that pg is required before openssl and all is good now.
>
> Hope this helps others in similar situations.
>
>

 MARTIN!!


 Thank you - this is exactly the kind of thing that our mailing list is for.
Thank you for demonstrating exemplarily citizenship.

 Graciously yours,
 Curtis

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.