question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Errors with RVM during vagrant up, following the quick start

See original GitHub issue

I’ve tried three times to follow the Quick Start to eval the snowplow platform. Each time, there’s an error during ruby-rvm provisioning, which causes the entire process to abort. I’m not entirely certain what the issue is here, but given that I just wanted to quickly evaluate the platform, it’s a disincentive to continuing.

Here’s the latest error.

==> default: ===================
==> default: CONFIGURING ANSIBLE
==> default: -------------------
==> default: ... done
==> default: ==========================================
==> default: RUNNING PLAYBOOKS WITH ANSIBLE*
==> default: * no output while each playbook is running
==> default: ------------------------------------------
==> default: Setting up Ansible to run out of checkout...
==> default: PATH=/vagrant/vagrant/ansible/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
==> default: PYTHONPATH=/vagrant/vagrant/ansible/lib:
==> default: ANSIBLE_LIBRARY=/vagrant/vagrant/ansible/library:/usr/share/ansible/
==> default: MANPATH=/vagrant/vagrant/ansible/docs/man:
==> default: Remember, you may wish to specify your host file with -i
==> default: Done!
==> default: 
==> default: PLAY [vagrant] **************************************************************** 
==> default: 
==> default: GATHERING FACTS *************************************************************** 
==> default: ok: [127.0.0.1]
==> default: 
==> default: TASK: [base | Update apt cache] *********************************************** 
==> default: ok: [127.0.0.1]
==> default: 
==> default: TASK: [base | Update all packages] ******************************************** 
==> default: ok: [127.0.0.1]
==> default: 
==> default: TASK: [base | install basic packages] ***************************************** 
==> default: changed: [127.0.0.1] => (item=curl,vim,libxslt1-dev,libxml2-dev,zip,libssl-dev,unzip,python-pip,python-psycopg2,apg,mercurial,git,python-dev)
==> default: 
==> default: TASK: [base | Ensure that ansible_cache_dir directory exists] ***************** 
==> default: changed: [127.0.0.1]
==> default: 
==> default: TASK: [base | Add Google DNS nameserver] ************************************** 
==> default: changed: [127.0.0.1]
==> default: 
==> default: TASK: [base | Update nameserver list] ***************************************** 
==> default: changed: [127.0.0.1]
==> default: 
==> default: TASK: [ruby-rvm | Prepare | Get the current users name] *********************** 
==> default: changed: [127.0.0.1]
==> default: 
==> default: TASK: [ruby-rvm | Prepare | Get the current users group] ********************** 
==> default: changed: [127.0.0.1]
==> default: 
==> default: TASK: [ruby-rvm | Install | Ensure dependencies installed] ******************** 
==> default: changed: [127.0.0.1] => (item=curl,libpq-dev,ruby-dev)
==> default: 
==> default: TASK: [ruby-rvm | Install | Ensure RVM signature is installed] **************** 
==> default: failed: [127.0.0.1] => {"changed": true, "cmd": "gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 ", "delta": "0:00:01.195965", "end": "2017-08-10 14:50:09.236836", "rc": 2, "start": "2017-08-10 14:50:08.040871"}
==> default: stderr: gpg: directory `/home/vagrant/.gnupg' created
==> default: gpg: new configuration file `/home/vagrant/.gnupg/gpg.conf' created
==> default: gpg: WARNING: options in `/home/vagrant/.gnupg/gpg.conf' are not yet active during this run
==> default: gpg: keyring `/home/vagrant/.gnupg/secring.gpg' created
==> default: gpg: keyring `/home/vagrant/.gnupg/pubring.gpg' created
==> default: gpg: requesting key D39DC0E3 from hkp server keys.gnupg.net
==> default: gpg: no valid OpenPGP data found.
==> default: gpg: Total number processed: 0
==> default: stdout: ?: keys.gnupg.net: Host not found
==> default: gpgkeys: HTTP fetch error 7: couldn't connect: Success
==> default: 
==> default: FATAL: all hosts have already failed -- aborting
==> default: 
==> default: PLAY RECAP ******************************************************************** 
==> default:            to retry, use: --limit @/home/vagrant/ruby-rvm.retry
==> default: 
==> default: 127.0.0.1                  : ok=10   changed=7    unreachable=0    failed=1   
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
mpapiscommented, Sep 9, 2017

Please use GPG v2 for downloading the keys, RVM itself will work fine with both GPG v1 and v2.

0reactions
BenFradetcommented, Feb 20, 2019

no more vagrant, closing

Read more comments on GitHub >

github_iconTop Results From Across the Web

Vagrant / Chef-solo not working after running recipe rvm
on my node, chef-solo is installed at /usr/local/bin/chef-solo, and setting it's path as you're showing in the Vagrantfile isn't working, either. Darn, it...
Read more >
Ruby Version Manager - RVM Best Practices
The following is a collection of tips and best practices that have proven to be effective in making development easier while using rvm....
Read more >
How to troubleshoot RubyGems and Bundler TLS/SSL Issues
To troubleshoot protocol connection errors, start by running the automatic SSL check, and follow the instructions. You might need to update Bundler, update ......
Read more >
Vagrant Provisioning with ruby and node commands
The set up allows the provisioner to even run bundle install or npm ... Even with this option, installing rvm is easy, but...
Read more >
Errors with Vagrant and Ubuntu 12.10 with RVM
But your error message indicates that when you run vagrant it is trying to use a version of Ruby (and its Gems) that...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found