[chef] Re: Re: Re: chef client segment fault on lib/chef/mixin/command/unix.rb:190

[Daniel DeLeo < >]

On Monday, December 3, 2012 at 4:49 PM, Steve Bennett wrote:

Hi,

  I'm also getting this segmentation fault:

115.146.84.xxx [2012-12-04T11:01:18+11:00] INFO: Processing cookbook_file[/mnt/data/Microscopy/Biology/mosquito.tif] action create (/var/chef/cache/cookbooks/atom-dataset-provider/recipes/default.rb line 126)

115.146.84.xxx /usr/lib/ruby/1.8/timeout.rb:58: 

115.146.84.xxx [BUG] 

115.146.84.xxx Segmentation fault

115.146.84.xxx 

115.146.84.xxx ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

115.146.84.xxx 

Sorry for the dumb question, but what's the correct way to upgrade Chef or Ruby? This server is built fresh from Ubuntu 12.04, then bootstrapped:

knife bootstrap -d ubuntu12.04-gems ....

So upgrading a component on the VM isn't that straightforward? (I assume from the output that the segfault is happening at the server end, not in the local chef client)

Steve

Your assumption is correct.

What version of Chef do you have on your workstation (e.g., `knife -v`)? Knife will bootstrap nodes to the same version of Chef as itself in order to prevent you from accidentally deploying a major version update.

Also, as mentioned, you can deploy with omnibus to get a newer version of ruby that should fix the segfault issues. Otherwise, you need to create a derivative of the ubuntu12.04-gems bootstrap template that installs a different ruby. I think the ubuntu-provided rubies now use alternatives to select which ruby version to call `ruby` rather than installing ruby 1.9 as `ruby19`, but I haven't payed a lot of attention to that recently.

-- 

Daniel DeLeo