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

Issue with vagrant up #1

Open
lelik9416 opened this issue Feb 17, 2018 · 6 comments
Open

Issue with vagrant up #1

lelik9416 opened this issue Feb 17, 2018 · 6 comments

Comments

@lelik9416
Copy link

Dear Alan,

Thank you for your article!
I wanted to run this example but have some problems with boxes.
I am only new in the topic. Also I tried to solve my problem but without success.
May you give me some direction for fixing or some advice for that? Pretty please!

All the best!

@alanswx
Copy link
Owner

alanswx commented Feb 17, 2018

I installed a new version of vagrant on my mac (my old version didn't work at all). I then did "vagrant up" in the directory. It gave a 404 when it was trying to check for metadata to upgrade the box - but this didn't stop it from booting. I was able to run the script, and see the HRRR tiles in my mac.

Where are you crashing? Can you paste some more information?

@alanswx alanswx closed this as completed Feb 17, 2018
@alanswx alanswx reopened this Feb 17, 2018
@lelik9416
Copy link
Author

Well, I installed Vagrant(1.9.1) and VirtualBox(5.1.30). Also I cloned your directory.
And when I try to run 'vagrant up' from the directory it gives me:
default: Box 'puppetlabs/centos-7.0-64-puppet' could not be found. Attempting to find and install...
The box 'puppetlabs/centos-7.0-64-puppet' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
vagrant login. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/puppetlabs/centos-7.0-64-puppet"]
Error: The requested URL returned error: 404 Not Found

As I see it's the same problem as you had. Right? Probably If I reinstall my version to another one It will work.

Which versions Did you use?

Thank you very much!

@lelik9416 lelik9416 reopened this Feb 18, 2018
@alanswx
Copy link
Owner

alanswx commented Feb 18, 2018

Maybe my box was cached. Try switching to another Centos box. I will take a look later. I switched to a different one but it was missing the virtual box tools.

@alanswx
Copy link
Owner

alanswx commented Feb 18, 2018

http://www.vagrantbox.es

@lelik9416
Copy link
Author

Well, I tried. I added a box. And I've got another mistake.
I suppose I didn't install something or don't have something for good working with that.

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
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.

@alanswx
Copy link
Owner

alanswx commented Feb 19, 2018

I tried again on a different mac (my laptop). My vagrant was all messed up. I had to reinstall it as well. Then I switched to a newer box from puppetlabs (7.2 instead of 7.0) - and did vagrant up. I did see some complaining, but then it created SSH keys and booted. Seems to work. Can you pull the latest version, and try it?

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

2 participants