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

Vagrant box broken after sleep/shutdown #1412

Closed
pkruithof opened this issue Mar 12, 2013 · 7 comments
Closed

Vagrant box broken after sleep/shutdown #1412

pkruithof opened this issue Mar 12, 2013 · 7 comments

Comments

@pkruithof
Copy link

This has happened several times now, the scenario is as follows: I create/provision a vagrant box (with puppet). I work on it for some time, a couple of days, sometimes a week. At the end of my day I either close the lid on my MacBook (putting it to sleep), or I shut it down. At a certain point, vagrant up gives an error:

[default] Mounting shared folders...
[default] -- v-root: /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p /vagrant

Provisioning, reloading, halt/up all don't work at this point. I have to destroy and build the box again, which costs some time and becomes very annoying.

I found this post which describes this problem, and states a ntp service should fix it. So I've added that to my puppet config, but the problem still occurs.

Issue #672 looks similar, but I'm running Ubuntu and not CentOS, so it's not the same issue.

The debug log is saved as a gist: https://gist.github.com/pkruithof/5116426

@mitchellh
Copy link
Contributor

This is super weird. I'm unable to reproduce this myself and the debug log isn't telling me much anything useful :( I could use more info here if anyone can get it.

@pkruithof
Copy link
Author

Is there something I can do to provide more debugging information?

@mitchellh
Copy link
Contributor

If you run mkdir -p /vagrant yourself in the box it is fine?

@zyga
Copy link

zyga commented Mar 19, 2013

Could this be related to the issue I've described in this blog post: http://blog.suxx.pl/2013/03/post-mortem-chasing-elusive-bugs.html

@pkruithof
Copy link
Author

@mitchellh I'm not experiencing the issue right now, but I have tried that before and yes, that works. The problem seems to be ssh-related, not the filesystem.

@mitchellh
Copy link
Contributor

I've not been able to reproduce this but I haven't heard of this happening to anyone else, so Im' going to close this until I can get more info or more interest. Sorry!

@pkruithof
Copy link
Author

That's ok, I kind of forgot about the issue. I did experience it again a couple of times since, but I just destroyed and upped the box when it happened. Which is kind of the point of Vagrant I assume 😉

@hashicorp hashicorp locked and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants