"Unable to find binary extension, was hitimes installed correctly" after installing v1.8.1

[maxandersen]

I updated from a working 1.7.4 to a now broken 1.8.1 via osx package on vagrantup.com.

When I run vagrant --version I get "Vagrant 1.8.1", but running any other command gives me:

Vagrant failed to initialize at a very early stage:

The plugins failed to load properly. The error message given is
shown below.

Unable to find binary extension, was hitimes installed correctly?

Any pointers ? I'm running El Capitain if that matters.

[aequitas]

Same here, running plugin related commands does work:

$ vagrant --version
Vagrant 1.8.1

$ vagrant plugin list
landrush (0.18.0)
vagrant-aws (0.6.0)
vagrant-share (1.1.5, system)
vagrant-vbguest (0.11.0)
vagrant-vbox-snapshot (0.0.10)

[aequitas]

Uninstalling and reinstalling plugins solved the problem for me.

[maxandersen]

a full removal of vagrant made this work again for me.

uninstalling/reinstalling plugins was not enough.

[sethvargo]

Hi everyone,

Thank you for opening and commenting on this issue, and I am sorry the upgrade process has not been smooth. Unfortunately I am not able to reproduce this issue, but I am glad you were able to get it fixed by uninstalling plugins or re-installing Vagrant.

It is possible that the .vagrant.d directory was somehow put in a bad state. However, without a reproduction, it's really hard for us to fix it 😦

I am going to go ahead and close this issue, but if someone is able to provide a reproducible way, we can definitely get this fixed in core. Thanks! 😄

[cswingler]

I seem to be able to reliably reproduce this:

https://gist.github.com/cswingler/cb3bbfb8d873d5f88c4e

[sethvargo]

@cswingler that error is coming from the berkshelf plugin, not Vagrant

[simonsparks]

I managed to get past this problem by uninstalling just one plugin (landrush in my case as it was first on the list).

[mario-areias]

@sethvargo I am exactly same situation as described by @maxandersen. Do you want me to get any specific logs so you can investigate?

[mario-areias]

I don't have the berkshelf plugin, btw.

[mario-areias]

This log is when I try to reload a machine with --debug enabled

DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/synced_folders/smb/plugin.rb
 INFO manager: Registered plugin: SMB synced folders
 INFO global: Loading plugins!
 INFO manager: Registered plugin: vagrant-share
 INFO manager: Registered plugin: vagrant-vbguest
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::PluginLoadError: The plugins failed to load properly. The error message given is
shown below.

Unable to find binary extension, was hitimes installed correctly?>
ERROR vagrant: The plugins failed to load properly. The error message given is
shown below.

Unable to find binary extension, was hitimes installed correctly?
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant.rb:293:in `rescue in <top (required)>'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant.rb:289:in `<top (required)>'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.1/bin/vagrant:105:in `require'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.1/bin/vagrant:105:in `<main>'
Vagrant failed to initialize at a very early stage:

The plugins failed to load properly. The error message given is
shown below.

Unable to find binary extension, was hitimes installed correctly?

[duocgit]

Uninstalling hitimes plugin worked for me

[dentarg]

Same here uninstall of landrush solved it (only plugin I had installed myself, vagrant plugin list listed vagrant-share too)

[marsmensch]

Same issue here. After upgrading a fully functional Vagrant 1.7.4 with landrush plugin (0.18.0), i got the error message experienced by @maxandersen @aequitas and @mario-areias.

Uninstalling landrush and reinstalling helped to work around the problem.

[mikegreiling]

So, is landrush incompatible with 1.8.1 or is this merely an upgrade process issue?

[marsmensch]

landrush works perfectly after reinstalling it. i guess it is some existing
landrush configuration that messes things up.

On Fri, Feb 5, 2016, 21:11 Mike Greiling notifications@github.com wrote:

So, is landrush incompatible with 1.8.1 or is this merely an upgrade
process issue?

—
Reply to this email directly or view it on GitHub
#6801 (comment).

[davsclaus]

Yeah I had that too in a 1.7.4 -> 1.8.1 upgrade on osx. To resolve I trashed my ~/.vagrant.d dir, and then installed landrush again, and it now works.

[petems]

Uninstalling landrush and reinstalling fixed for me 👍

[pbattino]

Same as petems! I had landrush 0.18.0, now it's 0.19.0
Thank you guys

[pbattino]

Correction: it SEEMED to work, but it didn't. I needed to empty ~/.vagrant.d/data/landrush and reinstall landrush.

[cfont]

I ran into this same issue and resolved it like @petems by simply uninstalling and reinstalling landrush. In my case I did not need to empty .vagrant.d dir but instead only reinstall landrush. I am using a Mac 10.10.4 and originally installed vagrant using homebrew in case that should be important at all.

Something else that may be important is that I don't have hitimes plugin installed before or after upgrading vagrant.