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

Chronological Thread 
  • From: Jeremiah Snapp < >
  • To:
  • Subject: [chef] Re: Re: Re: chef client segment fault on lib/chef/mixin/command/unix.rb:190
  • Date: Tue, 4 Dec 2012 03:51:05 -0500

I'm not trying to sidestep your original question about the segfault but why are you bootstrapping chef using the gems install?  The default bootstrap template is the omnibus install which is nice and clean, easy to upgrade and might even resolve your original problem.

To install the omnibus chef just don't specify "-d" in your bootstrap command. Then to upgrade later you just run the install/upgrade command found here: http://www.opscode.com/chef/install/

This is the method I use for my Ubuntu 12.04 servers.

On Dec 3, 2012 7:50 PM, "Steve Bennett" < "> > wrote:
  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 ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

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)


On 15 November 2012 06:44, Bryan McLellan < " target="_blank"> > wrote:
On Fri, Nov 9, 2012 at 8:49 PM,  < " target="_blank"> > wrote:
> Is there anybody know about the following segmentation fault? Where is the core
> file located?
> ===>
> /usr/lib/ruby/gems/1.8/gems/chef-0.10.6/bin/../lib/chef/mixin/command/unix.rb:190:
> [BUG] Segmentation fault

We worked around more of these segfaults in 0.10.10. Could you try
upgrading to at least that version?


A newer Chef (with the workaround) or a newer Ruby (with the fix)
should prevent these.


Archive powered by MHonArc 2.6.16.