search

schubergphilis / vagrant-chef-zero

Vagrant Plugin for Chef Zero
Apache License 2.0
91 stars 42 forks source link

chef-zero segfaulting on start #36

Closed eherot closed 10 years ago

eherot commented 10 years ago

Not sure if chef-zero itself is to blame, but...

This is with vagrant 1.4.3 and vagrant-chef-zero 0.6.0

$ vagrant up Bringing machine 'default' up with 'virtualbox' provider... [default] Importing base box 'precise64'... [default] Matching MAC address for NAT networking... [default] Setting the name of the VM... [default] Clearing any previously set forwarded ports... [Chef Zero] Starting Chef Zero at http://172.16.64.3:4000 sh: line 1: 95695 Abort trap: 6 /Users/eherot/.vagrant.d/gems/gems/chef-zero-1.7.3/bin/chef-zero --host 172.16.64.3 --port 4000 2>&1 > /dev/null [Chef Zero] Waiting for Chef Zero to start [Chef Zero] Waiting for Chef Zero to start [Chef Zero] Waiting for Chef Zero to start ...

And you can see the full trace by calling the Vagrant ruby directly:

https://gist.github.com/eherot/8589770

Chef-zero issue? Vagrant issue? Or Ruby issue? Currently chef-zero is the only thing on my machine showing symptoms.

eherot commented 10 years ago

Turns out this is actually a Ruby bug. Nevermind!

https://bugs.ruby-lang.org/issues/9200

andrewgross commented 10 years ago

Haha every time I see a segfault I assume a ruby bug. Thanks for letting me know and following up.