如何解决无用的间歇性错误“ SSH响应退出状态为非零”或引导超时错误
大多数情况下,每当我运行vagrant up
时,它就会挂起,然后在几分钟后最终显示如下。这是一个全新安装的无业游民,VirtualBox,Homestead,所以我想知道哪里出了问题,因为这些都是未经修改的。
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mv -f '/tmp/vagrant-network-entry-1602866071' '/etc/netplan/50-vagrant.yaml'
chown root:root '/etc/netplan/50-vagrant.yaml'
chmod 0644 '/etc/netplan/50-vagrant.yaml'
netplan apply
Stdout from the command:
Stderr from the command:
Traceback (most recent call last):
File "/usr/sbin/netplan",line 23,in <module>
netplan.main()
File "/usr/share/netplan/netplan/cli/core.py",line 50,in main
self.run_command()
File "/usr/share/netplan/netplan/cli/utils.py",line 186,in run_command
self.func()
File "/usr/share/netplan/netplan/cli/commands/apply.py",line 46,in run
self.run_command()
File "/usr/share/netplan/netplan/cli/utils.py",line 174,in command_apply
subprocess.check_call(['udevadm','settle'])
File "/usr/lib/python3.6/subprocess.py",line 311,in check_call
raise CalledProcessError(retcode,cmd)
subprocess.CalledProcessError: Command '['udevadm','settle']' returned non-zero exit status 1.
INFO interface: Machine: error-exit ["Vagrant::Errors::VagrantError","The following SSH command responded with a non-zero exit status.\nVagrant assumes that this means the command failed!\n\nmv -f '/tmp/vagrant-network-entry-1602866071' '/etc/netplan/50-vagrant.yaml'\nchown root:root '/etc/netplan/50-vagrant.yaml'\nchmod 0644 '/etc/netplan/50-vagrant.yaml'\nnetplan apply\n\nStdout from the command:\n\n\n\nStderr from the command:\n\nTraceback (most recent call last):\n File \"/usr/sbin/netplan\",in <module>\n netplan.main()\n File \"/usr/share/netplan/netplan/cli/core.py\",in main\n self.run_command()\n File \"/usr/share/netplan/netplan/cli/utils.py\",in run_command\n self.func()\n File \"/usr/share/netplan/netplan/cli/commands/apply.py\",in run\n self.run_command()\n File \"/usr/share/netplan/netplan/cli/utils.py\",in command_apply\n subprocess.check_call(['udevadm','settle'])\n File \"/usr/lib/python3.6/subprocess.py\",in check_call\n raise CalledProcessError(retcode,cmd)\nsubprocess.CalledProcessError: Command '['udevadm','settle']' returned non-zero exit status 1.\n"]
最让我着迷的是,因为有时一切都会正常运行而不会出错,但是由于发生了这种情况,它就像6次或更多次运行。
这是我使用的版本:
Windows 10 Pro
vagrant_2.2.10_x86_64.msi
VirtualBox-6.1.14-140239-Win.exe
此外,有时当我vagrant halt
然后再次运行vagrant up
时,这将显示:
==> homestead: Waiting for machine to boot. This may take a few minutes...
homestead: SSH address: 127.0.0.1:2222
homestead: SSH username: vagrant
homestead: 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.
因此错误不一致。
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。