Vagrant halt will force termination instead of normal termination.

Asked 2 years ago, Updated 2 years ago, 170 views

environment
Vagrant 2.2.4
VirtualBox version 5.2.28 r130011 (Qt5.6.3)
VBoxControl version 5.2.28r130011
Host osmac High Sierra 10.13.5
Guest os Ubuntu 14.04

problem
It takes a very long time to finish with vagrant half.

Checking the Command Line

==>default: Attempting graceful shutdown of VM...
==>default: Forcing shutdown of VM...

It seems to be terminated by forcefully.
I think something on ubuntu's side will not finish well and it will work like this, but I don't know the cause.
If you are familiar with it, could you help me?

I think it's good that the program automatically updated when I recently updated it because VBoxControl didn't match the current version, but then it stopped at virtualbox guest additions starting... and forced me to vagrant halt.
However, after that, it started well with vagrantup and SSH was fine. I checked the version with VBoxControl --version and it was updated properly.

I personally think it's here because everything is too long to post.
Vagrant half -- debug details the error, but I don't know what it means.

==>default: Attempting graceful shutdown of VM...
    default —Guest communication could not be established! This is useful because
    default —SSH is not running, the authentication information was changed,
    default —or some other networking issue.Vagrant will force half, if
    default —capable.
==>default: Forcing shutdown of VM...

ERRORwarden: Error occurred: The following SSH command responded with an non-zero exit status.

It says GuestAdditions is not working

DEBUG ssh:Exit status:1
DEBUG vbguest-machine: Current states for VM 'default' are: guest_version=5.2.28:host_version=5.2.28:running=false
 INFO interface:warn: [default] GuestAdditions items to be installed (5.2.28) correctly, but not running.
[default] GuestAdditions items to be installed (5.2.28) correctly, but not running.
 INFO subprocess: Starting process: ["/usr/local/bin/VBoxManage", "showvminfo", "dcad3a13-b345-4ff4-9e5c-fb4dbdcdf169", "--machine ready" ]
DEBUG subprocess: Command not in installer, not touching envvars.
 INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess:Selecting on IO
DEBUG subprocess:stdout:name="ubuntu1404-server_default_1514889379163_78359"

vagrant up--debug and vagrant half--debug end up with the same error

The following SSH command responded with an non-zero exit status.
Vagrant assumes that this means the command failed!

shutdown-now

Stdout from the command:



Stderr from the command:

ubuntu vagrant virtualbox

2022-09-30 21:40

1 Answers

It's common, but how about starting with checking around /var/log/messages?
Are there any other files under /var/log or logs for shutdown in the directory?


2022-09-30 21:40

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.