==> homestead: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
/sbin/ifdown 'eth1' || true
/sbin/ip addr flush dev 'eth1'
# Remove any previous network modifications from the interfaces file
sed -e '/^#VAGRANT-BEGIN/,$ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces.pre
sed -ne '/^#VAGRANT-END/,$ p' /etc/network/interfaces | tac | sed -e '/^#VAGRANT-END/,$ d' | tac > /tmp/vagrant-network-interfaces.post
cat \
/tmp/vagrant-network-interfaces.pre \
/tmp/vagrant-network-entry \
/tmp/vagrant-network-interfaces.post \
> /etc/network/interfaces
rm -f /tmp/vagrant-network-interfaces.pre
rm -f /tmp/vagrant-network-entry
rm -f /tmp/vagrant-network-interfaces.post
/sbin/ifup 'eth1'
Stdout from the command:
Stderr from the command:
bash: line 5: /sbin/ifdown: No such file or directory
bash: line 21: /sbin/ifup: No such file or directory
Process finished with exit code 1
Upgrade to the current version of Vagrant.
I'm using 2.1.1 and getting this error:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
/sbin/ip -o -0 addr | grep -v LOOPBACK | awk '{print $2}' | sed 's/://'
Stdout from the command:
Stderr from the command:
But vagrant ssh does work
@lperry65 No idea. We can't debug without seeing all the things from the issue template for your issue. Please open a new issue if you're still having problems.
Fixed it by destroying the instance and provisioning a new vm.
thanks,
Lee.
Most helpful comment
Upgrade to the current version of Vagrant.