Does 'vagrant <command> --debug' give you an indication where it hangs?

HTH, Torben
Am 11.02.2015 19:58 schrieb "Rodney Young" <[email protected]>:

> Hello all,
> I wonder if someone has a ready solution to this issue. I swear I solved
> it before the last time I played with Vagrant.
>
> Every command I issue vagrant has a pause of about 10 seconds before it
> actually runs. I think it is network related, as the delay correlates with
> the network speed (at home, longer delay, in office, shorter).
>
> I have exported the following:
> env | grep -i vagrant
> VAGRANT_NO_PLUGINS=true
> VAGRANT_CHECKPOINT_DISABLE=1
>
> When the command actually starts, it appears to return quickly.
> ________________________
> time vagrant help
> Usage: vagrant [options] <command> [<args>]
>
>     -v, --version                    Print the version and exit.
>     -h, --help                       Print this help.
>
> Common commands:
>      box             manages boxes: installation, removal, etc.
>      destroy         stops and deletes all traces of the vagrant machine
>      global-status   outputs status Vagrant environments for this user
>      halt            stops the vagrant machine
>      help            shows the help for a subcommand
>      init            initializes a new Vagrant environment by creating a
> Vagrantfile
>      login           log in to HashiCorp's Atlas
>      package         packages a running vagrant environment into a box
>      plugin          manages plugins: install, uninstall, update, etc.
>      provision       provisions the vagrant machine
>      push            deploys code in this environment to a configured
> destination
>      rdp             connects to machine via RDP
>      reload          restarts vagrant machine, loads new Vagrantfile
> configuration
>      resume          resume a suspended vagrant machine
>      ssh             connects to machine via SSH
>      ssh-config      outputs OpenSSH valid configuration to connect to the
> machine
>      status          outputs status of the vagrant machine
>      suspend         suspends the machine
>      up              starts and provisions the vagrant environment
>      version         prints current and latest Vagrant version
>
> For help on any individual command run `vagrant COMMAND -h`
>
> Additional subcommands are available, but are either more advanced
> or not commonly used. To see all subcommands, run the command
> `vagrant list-commands`.
>
>
> real    0m7.872s
> user    0m7.458s
> sys    0m0.414s
> ____________________
> time vagrant version
> Installed Version: 1.7.2
>
> Vagrant was unable to check for the latest version of Vagrant.
> Please check manually at http://www.vagrantup.com
>
> real    0m8.298s
> user    0m7.882s
> sys    0m0.416s
>
> Any thoughts? I didn't see anything in the documentation...any feedback
> greatly appreciated!
>
> --
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to