chef-client 0.7.16 [BUG] Segmentation fault

Here is what it looked like .. it would start then die within 10 seconds:
jmiller@somerandomname:~$ sudo /etc/init.d/chef-client start
* Starting chef-client chef-client
…done.
jmiller@somerandomname:~$ /usr/lib/ruby/1.8/ohai/plugins/linux/virtualization.rb:58: [BUG] Segmentation fault
ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux]

So I have been having problems on one of my chef boxes for the last week, it only showed up on this one system and it was driving me nuts. After a bit of time messing around it with it seems to be a known ruby issue and a updated ubuntu package finally came out!

http://tickets.opscode.com/browse/CHEF-530

Here is what it looked like .. it would start then die within 10 seconds:
jmiller@somerandomname:~$ sudo /etc/init.d/chef-client start
* Starting chef-client chef-client
…done.
jmiller@somerandomname:~$ /usr/lib/ruby/1.8/ohai/plugins/linux/virtualization.rb:58: [BUG] Segmentation fault
ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux]

Running chef client from the commandline would complete just fine.
jmiller@somerandomname:~$sudo chef-client

But the same segfault would occur when adding daemonize flag and here is a excerpt from the log files

jmiller@somerandomname:~$sudo chef-client -d -l debug

[Thu, 11 Mar 2010 17:05:54 -0800] DEBUG: —- End uname -m STDERR —-
[Thu, 11 Mar 2010 17:05:54 -0800] DEBUG: Ran (uname -m) returned 0
[Thu, 11 Mar 2010 17:05:54 -0800] DEBUG: Loading plugin virtualization
[Thu, 11 Mar 2010 17:05:54 -0800] DEBUG: Loading plugin linux::virtualization

I had to update the following ruby packages:

libmixlib-cli-ruby libmixlib-cli-ruby1.8 libmixlib-config-ruby libmixlib-config-ruby1.8 libmixlib-log-ruby libmixlib-log-ruby1.8 libohai-ruby libohai-ruby1.8

Now life is all good again … man that sucked.

Leave a Reply

Your email address will not be published. Required fields are marked *