[chef] incompatible C libyajl libs -- Chef 12


Chronological Thread 
  • From: Charles Betz < >
  • To:
  • Subject: [chef] incompatible C libyajl libs -- Chef 12
  • Date: Sat, 17 Jan 2015 21:10:37 -0600

Greetings,

I am attempting a new Chef Server install on Vagrant Trusty64 (14.04) and am getting on every invocation of chef-server-ctl:

=========

   the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and should not be loaded in the same Ruby VM
   falling back to ffi which might work (or might not, no promises)
   ffi-yajl/json_gem is deprecated, these monkeypatches will be dropped shortly
      the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and should not be loaded in the same Ruby VM
   falling back to ffi which might work (or might not, no promises)

=========

Here is the provisioning script i have written to be run by Vagrant:

=========

   hostname piernas.calavera.biz

   apt-get -y update

   dpkg -i chef-server-core_12.0.1-1_amd64.deb

   chef-server-ctl reconfigure

   chef-server-ctl user-create CharlesTBetz Charles Betz ">  testPass --filename /vagrant/char-chef-cred

   chef-server-ctl org-create DMA Digital Management Academy --association_user CharlesTBetz --filename      /vagrant/dma-chef-cred

===========


This is on a clean, vanilla VirtualBox with only apt-get update run, and then following the instructions at http://docs.chef.io/server/install_server.html.

I am running this on a late model Mac Air and have concerns about the capacity, but this would not seem to be a capacity error.

I have fully qualified the hostname. 

I also notice that I do not see the security files created (char-chef-cred, dma-chef-cred)

Thoughts? Apologies if this is a total noob error. I see other server requirements (ntp, smtp, etc) that would also not seem relevant on an initial sandbox install. 

Thanks for any assistance. This is to enable a simulation for a Masters course in software engineering. 

Charles Betz



Archive powered by MHonArc 2.6.16.

§