vagrant box aborted, can not up












0















I got the error message from the command line:



$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/xenial64' is up to date...
==> default: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
==> default: available! You currently have version '20181102.0.0'. The latest is version
==> default: '20181122.1.0'. Run `vagrant box update` to update.
==> default: Clearing any previously set forwarded ports...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "8cb8ae85-050a-4bf2-8f8a-5b53bc002c24", "--natpf1",
"delete", "ssh", "--natpf1", "delete", "tcp3306", "--natpf1", "delete",
"tcp443", "--natpf1", "delete", "tcp5000", "--natpf1", "delete", "tcp6379", "--
natpf1", "delete", "tcp7000", "--natpf1", "delete", "tcp80", "--natpf1",
"delete", "tcp9000"]


Stderr: VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error
(extended info not available)
VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at

line 525 of file VBoxManageModifyVM.cpp



Can you help me ?



Sorry, i just stop the machine in visualbox and restart it . Everything just got right, i still don't know the reason.










share|improve this question





























    0















    I got the error message from the command line:



    $ vagrant up
    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Checking if box 'ubuntu/xenial64' is up to date...
    ==> default: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
    ==> default: available! You currently have version '20181102.0.0'. The latest is version
    ==> default: '20181122.1.0'. Run `vagrant box update` to update.
    ==> default: Clearing any previously set forwarded ports...
    There was an error while executing `VBoxManage`, a CLI used by Vagrant
    for controlling VirtualBox. The command and stderr is shown below.

    Command: ["modifyvm", "8cb8ae85-050a-4bf2-8f8a-5b53bc002c24", "--natpf1",
    "delete", "ssh", "--natpf1", "delete", "tcp3306", "--natpf1", "delete",
    "tcp443", "--natpf1", "delete", "tcp5000", "--natpf1", "delete", "tcp6379", "--
    natpf1", "delete", "tcp7000", "--natpf1", "delete", "tcp80", "--natpf1",
    "delete", "tcp9000"]


    Stderr: VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error
    (extended info not available)
    VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at

    line 525 of file VBoxManageModifyVM.cpp



    Can you help me ?



    Sorry, i just stop the machine in visualbox and restart it . Everything just got right, i still don't know the reason.










    share|improve this question



























      0












      0








      0








      I got the error message from the command line:



      $ vagrant up
      Bringing machine 'default' up with 'virtualbox' provider...
      ==> default: Checking if box 'ubuntu/xenial64' is up to date...
      ==> default: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
      ==> default: available! You currently have version '20181102.0.0'. The latest is version
      ==> default: '20181122.1.0'. Run `vagrant box update` to update.
      ==> default: Clearing any previously set forwarded ports...
      There was an error while executing `VBoxManage`, a CLI used by Vagrant
      for controlling VirtualBox. The command and stderr is shown below.

      Command: ["modifyvm", "8cb8ae85-050a-4bf2-8f8a-5b53bc002c24", "--natpf1",
      "delete", "ssh", "--natpf1", "delete", "tcp3306", "--natpf1", "delete",
      "tcp443", "--natpf1", "delete", "tcp5000", "--natpf1", "delete", "tcp6379", "--
      natpf1", "delete", "tcp7000", "--natpf1", "delete", "tcp80", "--natpf1",
      "delete", "tcp9000"]


      Stderr: VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error
      (extended info not available)
      VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at

      line 525 of file VBoxManageModifyVM.cpp



      Can you help me ?



      Sorry, i just stop the machine in visualbox and restart it . Everything just got right, i still don't know the reason.










      share|improve this question
















      I got the error message from the command line:



      $ vagrant up
      Bringing machine 'default' up with 'virtualbox' provider...
      ==> default: Checking if box 'ubuntu/xenial64' is up to date...
      ==> default: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
      ==> default: available! You currently have version '20181102.0.0'. The latest is version
      ==> default: '20181122.1.0'. Run `vagrant box update` to update.
      ==> default: Clearing any previously set forwarded ports...
      There was an error while executing `VBoxManage`, a CLI used by Vagrant
      for controlling VirtualBox. The command and stderr is shown below.

      Command: ["modifyvm", "8cb8ae85-050a-4bf2-8f8a-5b53bc002c24", "--natpf1",
      "delete", "ssh", "--natpf1", "delete", "tcp3306", "--natpf1", "delete",
      "tcp443", "--natpf1", "delete", "tcp5000", "--natpf1", "delete", "tcp6379", "--
      natpf1", "delete", "tcp7000", "--natpf1", "delete", "tcp80", "--natpf1",
      "delete", "tcp9000"]


      Stderr: VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error
      (extended info not available)
      VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at

      line 525 of file VBoxManageModifyVM.cpp



      Can you help me ?



      Sorry, i just stop the machine in visualbox and restart it . Everything just got right, i still don't know the reason.







      vagrant






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 23 '18 at 2:06







      王肖毅

















      asked Nov 23 '18 at 1:51









      王肖毅王肖毅

      499




      499
























          1 Answer
          1






          active

          oldest

          votes


















          2














          You can get more in depth logs by using $ vagrant up --debug or if you would like to save it to a file $ vagrant up --debug &> vagrant.log. Otherwise I would recommend making sure all VMs are stopped then run $ vagrant reload --provision. Also, the wonderful thing about this is you can just tear it down and start over very easily! :)






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53439792%2fvagrant-box-aborted-can-not-up%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            You can get more in depth logs by using $ vagrant up --debug or if you would like to save it to a file $ vagrant up --debug &> vagrant.log. Otherwise I would recommend making sure all VMs are stopped then run $ vagrant reload --provision. Also, the wonderful thing about this is you can just tear it down and start over very easily! :)






            share|improve this answer




























              2














              You can get more in depth logs by using $ vagrant up --debug or if you would like to save it to a file $ vagrant up --debug &> vagrant.log. Otherwise I would recommend making sure all VMs are stopped then run $ vagrant reload --provision. Also, the wonderful thing about this is you can just tear it down and start over very easily! :)






              share|improve this answer


























                2












                2








                2







                You can get more in depth logs by using $ vagrant up --debug or if you would like to save it to a file $ vagrant up --debug &> vagrant.log. Otherwise I would recommend making sure all VMs are stopped then run $ vagrant reload --provision. Also, the wonderful thing about this is you can just tear it down and start over very easily! :)






                share|improve this answer













                You can get more in depth logs by using $ vagrant up --debug or if you would like to save it to a file $ vagrant up --debug &> vagrant.log. Otherwise I would recommend making sure all VMs are stopped then run $ vagrant reload --provision. Also, the wonderful thing about this is you can just tear it down and start over very easily! :)







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 2 '18 at 18:49









                KevinKevin

                789




                789






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53439792%2fvagrant-box-aborted-can-not-up%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Wiesbaden

                    Marschland

                    Dieringhausen