Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Expired SSL certificate throws some errors on 1.9.3 install #889

Closed
abevoelker opened this Issue Apr 7, 2012 · 7 comments

Comments

Projects
None yet
4 participants

Doing a fresh 1.9.3 install throws up some errors when trying to install yaml-0.1.4.tar.gz. It looks like the issue is the SSL certificate for the rvm website expired today. It does eventually failover to HTTP or FTP after a couple retries and install correctly, but the red error text does look a bit ominous at first glance.

gitlab@abe-PC:~$ rvm install 1.9.3
Fetching yaml-0.1.4.tar.gz to /home/gitlab/.rvm/archives
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
There was an error, please check /home/gitlab/.rvm/log//*.log. Next we'll try to fetch via http.
Trying ftp:// URL instead.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
There was an error, please check /home/gitlab/.rvm/log//*.log
Extracting yaml-0.1.4.tar.gz to /home/gitlab/.rvm/src
Error running 'tar xmzf /home/gitlab/.rvm/archives/yaml-0.1.4.tar.gz -C /home/gitlab/.rvm/src --no-same-owner', please read /home/gitlab/.rvm/log/ruby-1.9.3-p125/yaml/extract.log
/home/gitlab/.rvm/scripts/functions/pkg: line 52: cd: /home/gitlab/.rvm/src/yaml-0.1.4: No such file or directory
Configuring yaml in /home/gitlab/.rvm/src/yaml-0.1.4.
Error running ' ./configure --prefix="/home/gitlab/.rvm/usr"  ', please read /home/gitlab/.rvm/log/ruby-1.9.3-p125/yaml/configure.log
Compiling yaml in /home/gitlab/.rvm/src/yaml-0.1.4.
Error running 'make ', please read /home/gitlab/.rvm/log/ruby-1.9.3-p125/yaml/make.log


Database file /home/gitlab/.rvm/config/packages does not exist.

Installing Ruby from source to: /home/gitlab/.rvm/rubies/ruby-1.9.3-p125, this may take a while depending on your cpu(s)...


ruby-1.9.3-p125 - #fetching 
ruby-1.9.3-p125 - #downloading ruby-1.9.3-p125, this may take a while depending on your connection...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 9505k  100 9505k    0     0  1140k      0  0:00:08  0:00:08 --:--:-- 1899k
ruby-1.9.3-p125 - #extracting ruby-1.9.3-p125 to /home/gitlab/.rvm/src/ruby-1.9.3-p125
ruby-1.9.3-p125 - #extracted to /home/gitlab/.rvm/src/ruby-1.9.3-p125
Applying patch 'xcode-debugopt-fix-r34840' (located at /home/gitlab/.rvm/patches/ruby/1.9.3/p125/xcode-debugopt-fix-r34840.diff)
ruby-1.9.3-p125 - #autoreconf
ruby-1.9.3-p125 - #configuring
ruby-1.9.3-p125 - #compiling 
ruby-1.9.3-p125 - #installing 
Retrieving rubygems-1.8.21
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  250k  100  250k    0     0   578k      0 --:--:-- --:--:-- --:--:--  778k
Extracting rubygems-1.8.21 ...
Removing old Rubygems files...
Installing rubygems-1.8.21 for ruby-1.9.3-p125 ...
Installation of rubygems completed successfully.
ruby-1.9.3-p125 - adjusting #shebangs for (gem irb erb ri rdoc testrb rake).
ruby-1.9.3-p125 - #importing default gemsets (/home/gitlab/.rvm/gemsets/)
Install of ruby-1.9.3-p125 - #complete

@ghost ghost assigned mpapis Apr 8, 2012

Owner

mpapis commented Apr 8, 2012

I'm sorry for the trouble, we had to migrate RVM to shorter domain rvm.io, I have updated all resources and code to point to the new domain, just update RVM:

rvm get head # OR:
rvm get stable

also there is new shorter installer command:

curl -L get.rvm.io | bash -s stable

@mpapis mpapis closed this Apr 8, 2012

No problem, thanks for all your hard work on rvm. Loving the short URL.

Contributor

jcsalterego commented Apr 10, 2012

Are there any plans to renew the wildcard certificate and announce/begin a transition to rvm.io?

Owner

mpapis commented Apr 10, 2012

@wayneeseguin announced it already https://twitter.com/#!/wayneeseguin/status/188634745079468032 we also updated all the references in github repository and on the site, what more could we do ?

as for removing the old domain name https://rvm.beginrescueend.com/ - it costs money, and RVM is opensource project, maybe some donations could help to make that happen - if you feel like it's needed.

Contributor

jcsalterego commented Apr 10, 2012

Ah, I must have an outdated version because rvm get head and rvm get stable didn't work for me. I believe I had 0.10.x.

I didn't see @wayneeseguin's tweet, but it doesn't really explain that the domain change breaks some older installations.

Perhaps there should be a larger announcement or better communication on the rvm.io (and old beginrescueend.com) website regarding the domain transition, how it affects older installations and the upgrade path? Basically the contents of this issue but in a more permanent and visible place.

For the record, it seems I was able to upgrade RVM by running the original curl -L get.rvm.io | bash -s stable again.

Thanks for all the hard work.

I couldn't upgrade from 1.6.20 with the standard rvm get stable due to this (grumble grumble). Thanks to @jcsalterego for pointing out that curl -L get.rvm.io | bash -s stable can upgrade as well as install. I wasn't looking forward to reinstalling everything from scratch just because someone wanted a shorter URL.

Owner

mpapis commented Apr 19, 2012

1.6.20 was not aware of stable the way to update from stable would be:

rvm get head
rvm reload
rvm get stable

or just run the installer:

curl -L get.rvm.io | bash -s stable

there is no need to remove RVM before installing it, installer is used also for updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment