New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble with openssl and RHEL 6.3 #126
Comments
It would appear that ruby 2.1.0 requires a newer version of OpenSSL, than what RHEL 6.3 provides. |
Perhaps, but that doesn't explain why I can install Ruby 1.9.3 with RVM but not with ruby-install. Ruby 1.9.3 is all I need at the moment. Ruby 2.1.0 was just a curiosity test. Every install of Ruby I have tried with ruby-install either fails or compiles ossl with many warnings that always leads to an openssl error:
|
@juanitogan what is odd, is that the output of ruby-install shows 1.9.3 successfully compiling openssl; albeit with some warnings. |
Yes, very odd. Not just warnings though, but also threats: The RVM solution to openssl was to force a reinstall after initial install, such as:
I'll keep digging as to why this was needed but similar options have not worked with ruby-install yet. I might put a similar question to Stack Overflow as well. I don't yet understand what files are needed by openssl and why. Why does RVM install its own version? Why does ruby-install seem to be installing/updating a version in /usr/bin as well as extra stuff in /opt/rubies? Etc. |
I am also beginning to wonder about the value of yum here. On one hand it is nice that ruby-install uses yum to automatically install required packages. On the other hand, our users currently do not have sudo rights to yum (no idea if this is best practice or not) and therefore cannot execute ruby-install for local installs. Furthermore, it appears yum caused an unwanted upgrade from openssl 1.0.1c to 1.0.1e and I have no idea yet if this is part of the problem. |
If the users need to install additional software, you should either have root do it or give sudo access to them. You can also disable the installation of dependencies with the |
Thanks for the help, I'll take a look at I have to switch to another task for a week or so, so I may go quiet on this. |
I am closing this because I have learned that this is not specific to ruby-install but, rather, applies to all installers. Still, others might need to know what I found so I will briefly describe it here. After far too many hours of research, and learning far more about Linux than I ever cared to, I have narrowed the problem to basic peculiarities of RHEL and OpenSSL and an incorrect assumption made by Ruby (extconf.rb) during installation. The following sites gave me some good clues as to what to look at but I found nothing that put it all together like what I needed. http://www.openssl.org/support/faq.html#BUILD8 ...and not much thanks to a whole bunch of red herrings involving Ruby patches and EC2M. Also, RVM needs to correct their optimism that they have accounted for this with autolibs and should reinstate their previous openssl page. Basic rulesRule 1The install of OpenSSL (1.0.1e) created and maintained by yum in Rule 2I found two old versions (0.9.8) of OpenSSL in
The new Ruby install should now work with OpenSSL properly. As a quick check, I restart my sudo session and then (assuming using chruby):
Rule 3Installing OpenSSL anywhere besides
The new Ruby install should now work with OpenSSL properly. As a quick check, I restart my sudo session and then (assuming using chruby):
Perhaps I'll add more later as I refine our install procedure. This much, thus far, is the result of perhaps a hundred trials of Ruby and OpenSSL installs under various conditions and switches. If anyone has more answers, please share. Time to get back to real life. |
@juanitogan you should consider submitting a bug about openssl's extconf.rb to https://bugs.ruby-lang.org/ |
Openssl does not appear to be compiling correctly when installing any version of Ruby on our RHEL 6.3 system. I have been trying to leave user installs of RVM behind and replace them with root installs via ruby-install. Openssl works fine in our RVM user installs (with the prescribed RVM fix) as well as in the built-in system install of Ruby 1.8.7 in /usr/bin.
Openssl is broken in each Ruby version I have tried with ruby-install: 1.9.3-p392 (our prod version), 1.9 latest, and 2.1.0 current. I have tried every openssl fix/workaround I can find, such as the --with-openssl-dir config pointing to various openssl folders, but nothing works for me. I feel like I'm missing something basic but can't see it not being a Linux guru.
Here are some relevant messages from a few of my many attempts:
Note all the ossl warnings above.
Restart session.
Test system Ruby 1.8.7 openssl: Works.
Test ruby-install Ruby 1.9.3 openssl: Fails.
Test RVM Ruby 1.9.3 openssl in user home: Works.
The text was updated successfully, but these errors were encountered: