Skip to content
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

Authentication issue on "vagrant up" #47

Open
reliztrent opened this issue May 25, 2016 · 5 comments
Open

Authentication issue on "vagrant up" #47

reliztrent opened this issue May 25, 2016 · 5 comments

Comments

@reliztrent
Copy link

reliztrent commented May 25, 2016

Running into what may be an ssh authentication issue on installation when running "vagrant up."

Environment:

  • Ubuntu 14.04 host
  • Vagrant 1.8.1
  • VirtualBox 4.3.36_Ubuntur105129

Steps:

  1. Install vagrant and virtualbox, versions above.
  2. cloned git repo
  3. cd to fcrepo4-vagrant
  4. Update ports in Vagrantfile to avoid collisions
  5. vagrant up

Result:
$ sudo vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
. . .
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2200
default: SSH username: vagrant
default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

Attempted fixes:

  • Increase timeout limit in Vagrantfile with config.vm.boot_timeout
  • Uninstalling and reinstalling Vagrant and VirtualBox
  • Turn off and remove all other Vagrant boxes
@ruebot
Copy link

ruebot commented May 25, 2016

Hey @reliztrent, are you running Ubuntu? If so, what release?

@ruebot
Copy link

ruebot commented May 25, 2016

@reliztrent nevermind, you have that in your ticket 😄

Can you try installing a more recent version of VirtualBox? I'm 5.0.14_Ubuntu r105127 locally, and that seems to be working.

@dnapier
Copy link

dnapier commented Feb 24, 2017

I am also running into this issue with CentOS 7, do you want me to open another issue?

CentOS 7
VBox 5.4.14r112924
Vagrant 1.9.1

@awoods
Copy link

awoods commented Feb 26, 2017

@dnapier : Have you tried the suggestions mentioned here?

@dnapier
Copy link

dnapier commented Feb 27, 2017

@awoods : I did, same result unfortunately. We're going to use one of the other build methods for now. If that doesn't work out I'll revisit this thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants