When I run vagrant I get multiple "Ignoring ... because its extensions are not built." errors

[Greg]

Hi:

When I run Vagrant I get the following errors:

Ignoring ffi-1.9.10 because its extensions are not built.  Try: gem pristine ffi --version 1.9.10
Ignoring nokogiri-1.6.3.1 because its extensions are not built.  Try: gem pristine nokogiri --version 1.6.3.1
Ignoring unf_ext-0.0.7.1 because its extensions are not built.  Try: gem pristine unf_ext --version 0.0.7.1

OS X 10.11.6
Vagrant 1.9.1
ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]

Is this a serious problem? If so how can I fix it?

The VM is running, but I'm also having problems with it (php isn't working with apache); I used puphpet for that. Could that problem be related to the errors I'm seeing?

Thanks!
Greg

[Alvaro Miranda Aguilera]

Hello,

Not sure from where the error is comming from.

Can you test renaming ~/.vagrant.d to ~/.vagrant.d.old and trying again?

If message still persists, I would suggest uninstall vagrant (the installer give you the option) and then delete ~/.vagrant.d and /opt/vagrant

And then run:

sudo find / | grep -i vagrant

and see if there is any leftover around.

With that you will ensure a new clean install.

Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/eeda0ed6-5200-4a8f-a844-29aa24b5720d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Greg]

Hi, Alvaro:

Thanks for replying.


$ mv ~/.vagrant.d ~/.vagrant.d.old
$ cd VirtualBox-VMs/
.
.
.
$ vagrant up

Ignoring ffi-1.9.10 because its extensions are not built.  Try: gem pristine ffi --version 1.9.10
Ignoring nokogiri-1.6.3.1 because its extensions are not built.  Try: gem pristine nokogiri --version 1.6.3.1
Ignoring unf_ext-0.0.7.1 because its extensions are not built.  Try: gem pristine unf_ext --version 0.0.7.1

Moving on to uninstalling vagrant, using uninstall.tool. In addition:
$ rm -rf .vagrant.d
$ rm -rf .vagrant.d.old/
$ sudo rm /usr/bin/vagrant

I opted NOT to remove /private/var/db/receipts/com.vagrant.vagrant.bom and /private/var/db/receipts/com.vagrant.vagrant.plist because dire warnings from web land about deleting anything from /private/var.

There are lots of other references to vagrant in my VM directory, etc. They seem like they're supposed to be there.

Re-downloaded vagrant 1.9.1 and installed it. And...

...that appears to have worked!

One other thing that I came across was some files that grepped positive for 'vagrant' files in my Trash from an uninstalled version of WebStorm. Perhaps WebStorm did something?

In any case, I'm good again.

Thanks a bunch!
Greg

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/eeda0ed6-5200-4a8f-a844-29aa24b5720d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Alvaro Miranda Aguilera]

Some projects use (abuse?) that Vagrant is ruby, and they run/use ruby code, install gems, etc.

So if this start happening again, keep an eye on the project, and have a look in the Vagrantfile.

for some people that is Ruby programer, feels  natural just have a good Vagrantifle, but for non-ruby programers is hard to maintain.

Not saying is good or wrong, but if thats cause problems, the best is move to create your own box/project.

Any question, or help, just let us know.

Alvaro.

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c0c1edde-a65c-4770-bcdb-f1060ca56734%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Sam Anthony]

Please use caution when messing around with .vagrant.d folder. In my situation I have many different virtual boxes (several Gigabytes). It seems .vagrant.d/boxes stores the original boxes downloaded. So if you do a vagrant destroy, and then a vagrant up on any other vagrantfile, it will need to download the original box again (Some download very slowly in my experience).

[Alvaro Miranda Aguilera]

hello sam

boxes downloaded are in ~/.vagrant/d/boxes

you can copy this before blowing away .vagrant.d and put t back after reinstall and the template boxes will remain.

alvaro