Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

First vagrant up works but then ruby error after halt/up

Tags:

ruby

vagrant

I have installed ruby 2.1.6, vagrant 1.7.2 abd virtual box 4.3.28.

The first vagrant up works fine and box is downloaded and server works, but when I run halt and then try another vagrant up I get the ruby error message below

C:/Users/Mike/.vagrant.d/gems/gems/childprocess-0.5.6/lib/childprocess/windows/lib.rb:308: [BUG] Segmentation fault
ruby 2.0.0p353 (2013-11-22) [i386-mingw32]

// lots of output listing ruby files

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

The total output is lengthy so I had to upload it separately here:

I have tried uninstalling everything and re-installing but the same thing always happens. Can anyone make sense of this error message for me and give me some advice for fixing it?

The vagrant project is running on my desktop machine fine, this issue is just happening with my laptop.

like image 713
Guerrilla Avatar asked Jun 29 '15 01:06

Guerrilla


2 Answers

I got the same issue since yesterday and I was able to find a workaround through this commands

> vagrant plugin install ffi
> vagrant plugin uninstall ffi && vagrant plugin install ffi --plugin-version 1.9.8

After that, you should be able to do vagrant up without any problem. The cause was the latest ffi gem released the other day (I think this only affects windows user), so for someone who just installed or updated vagrant, we need to downgrade the ffi to 1.9.8 for now.

Source: https://github.com/mitchellh/vagrant/issues/5869

like image 148
Chris Laconsay Avatar answered Sep 29 '22 01:09

Chris Laconsay


Facing the same issue today (It was working last friday). After reinstall/uninstall/restart countless time I am able to solved this issue by doing the following:

  1. Go to the .vagrant.d\ folder
  2. Delete both plugins.json and the entire gems
  3. My existing Vagrantfile had a code to install plugin if not exist. I had to remove it too.

This basically removed all plugins to make it work. I only used vagrant-cachier so not a big deal for me.

like image 32
shinshenjs Avatar answered Sep 29 '22 01:09

shinshenjs