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

re: CentOS 7.3, vagrant up hangs on SSH step #124

Closed
MJMoody opened this issue Apr 4, 2018 · 8 comments
Closed

re: CentOS 7.3, vagrant up hangs on SSH step #124

MJMoody opened this issue Apr 4, 2018 · 8 comments
Assignees
Labels
Milestone

Comments

@MJMoody
Copy link

MJMoody commented Apr 4, 2018

With setting vm_version=7.3

Run vagrant up --no-provision

The above command hangs completely at the SSH step...

==> ml9-dhf-ml1: Waiting for machine to boot. This may take a few minutes...
    ml9-dhf-ml1: SSH address: 127.0.0.1:2222
    ml9-dhf-ml1: SSH username: vagrant
    ml9-dhf-ml1: SSH auth method: private key

When setting vm_version=7.2, the vagrant up process completes.

I am using the latest versions:

VirtualBox 5.2.8
Vagrant 2.0.3

@grtjn
Copy link
Owner

grtjn commented May 14, 2018

I am aware of 7.3 not working well yet. I think the chef project made changes to how they put together their vm's causing this issue. I'll have a look if they have released a new version of the 7.3 vm, and/or if they released 7.4 and 7.5 versions too..

@grtjn grtjn self-assigned this May 14, 2018
@grtjn grtjn added the bug label May 14, 2018
@grtjn grtjn added this to the 1.0.6 milestone May 14, 2018
@grtjn
Copy link
Owner

grtjn commented May 14, 2018

See also #116

@grtjn
Copy link
Owner

grtjn commented May 14, 2018

i published a more recent 7.3 version, and also a 7.4 one, but neither works. The preview screen in virtual box shows a blinking login screen. It is as if the ssh auth is simply never reached for whatever reason.

@grtjn
Copy link
Owner

grtjn commented May 15, 2018

Still on-going. For the time being I recommend using the centos-7.2 (which is still the default for mlvagrant) for now. You can optionally update the os inside the vm to get it upgraded to 7.5 effectively. There is a properties flag to do so..

@grtjn
Copy link
Owner

grtjn commented May 15, 2018

I think I finally resolved this issue. It seems that re-packaging the bento base boxes messed up with its network config, causing the centos network service to fail, with subsequent timeouts when trying to connect from outside.

I found a fix for the re-packaging (mostly by sheer luck), and have in the meantime uploaded fresh versions of grtjn/centos-7.3 and grtjn/centos-7.4.

I recommend anyone that may have touched those base boxes to check and purge existing ones:

  • vagrant box list (to find out if you have used either before)
  • vagrant box remove grtjn/centos-7.3 (to get rid of it)
  • vagrant box remove grtjn/centos-7.4

This is particularly necessary if you tried those boxes in the past few days, where I have been uploading 2017 and 2018 versions of both, and replacing them with new uploads..

@grtjn
Copy link
Owner

grtjn commented May 15, 2018

@MJMoody, would you be willing to run a test with this, so that I can close this ticket?

@MJMoody
Copy link
Author

MJMoody commented May 21, 2018

This is now working.

I created a new folder for my ml-vagrant project, and specified vm_version=7.3 in the project.properties file. I'm also using MarkLogic 9.0.5 installers.

I then cd to my new ml-vagrant project and run vagrant box update, which updated the grtjn/centos-7.3 box image from 2.3.5 to 2018.22.0.

I then run vagrant up --no-provision, and this completes without the issue -- the ssh step proceeds as expected.

I then run vagrant provision and this completes without issue -- my new ml-vagrant VM is running with 9.0.5.

All good. Thanks Geert!

@grtjn
Copy link
Owner

grtjn commented May 22, 2018

Thnx for reporting back!

@grtjn grtjn closed this as completed May 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants