Re: [FIXED] Vagrant up returns "The following SSH command responded with a non-zero exit status....mkdir -p /vagrant"

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: [FIXED] Vagrant up returns "The following SSH command responded with a non-zero exit status....mkdir -p /vagrant"

David Busby

Having this issue with CentOS 6.3, fixed by adding the following via visudo:

---
Defaults    env_keep += "SSH_AUTH_SOCK"
%admin ALL=NOPASSWD: ALL
Defaults:vagrant !requiretty
---

Note the addition of the !requiretty and SSH_AUTH_SOCK env_keep line. Source: http://www.practicalweb.co.uk/blog/12/10/16/how-build-centos-6-base-box-vagrant



On Monday, August 20, 2012 2:55:17 PM UTC+1, Andrew Sledge wrote:
This was a problem on my end. The postinstall.sh (using veewee) script ran some unsuspected changed on /etc/sudoers which was not formatted properly to handle vagrant using the NOPASSWD option.

On Sunday, August 19, 2012 12:31:59 PM UTC-4, Andrew Sledge wrote:
andrew@lin:~/work/personal-blog/vm$ vagrant up
[default] VM already created. Booting if it's not already running...
[default] Clearing any previously set forwarded ports...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[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

Running with DEBUG turned on reveals: http://pastebin.com/vM6UmzXL

Any ideas?

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.