# Incompatible C libyajl libs -- Chef 12

**URL:** <https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177>\
**Category:** Chef Infra (archive)\
**Created:** [January 18, 2015, 3:10am UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177 "2015-01-18T03:10:37Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Charles\_Betz](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@Charles\_Betz](https://discourse.chef.io/u/Charles_Betz)\
**Post date:** [January 18, 2015, 3:10am UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/1 "2015-01-18T03:10:37Z")

</div>

Greetings,

I am attempting a new Chef Server install on Vagrant Trusty64  
[https://atlas.hashicorp.com/ubuntu/boxes/trusty64](https://atlas.hashicorp.com/ubuntu/boxes/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](http://piernas.calavera.biz)

apt-get -y update

wget  
[https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)

dpkg -i chef-server-core\_12.0.1-1\_amd64.deb

chef-server-ctl reconfigure

chef-server-ctl user-create CharlesTBetz Charles Betz [char@erp4it.com](mailto:char@erp4it.com)  
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](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

---

<div class="post-metadata">

**Author:** ![sdelano](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/sdelano/32/35_2.png) [@sdelano](https://discourse.chef.io/u/sdelano)\
**Post date:** [January 18, 2015, 3:17am UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/2 "2015-01-18T03:17:51Z")

</div>

Hi Charles,

The libyajl warning is a know issues and is fixed on the master branch of the Chef Server.

This is simply a warning and, as far as we know, doesn’t cause any errors in the operation of the Chef Server.

Is the output that you posted the complete output of the script you have run?

—  
Stephen Delano - Engineering Lead, Chef

On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com), wrote:  
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](http://piernas.calavera.biz)

apt-get -y update

wget [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)

dpkg -i chef-server-core\_12.0.1-1\_amd64.deb

chef-server-ctl reconfigure

chef-server-ctl user-create CharlesTBetz Charles Betz [char@erp4it.com](mailto:char@erp4it.com) 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](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

---

<div class="post-metadata">

**Author:** ![sdelano](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/sdelano/32/35_2.png) [@sdelano](https://discourse.chef.io/u/sdelano)\
**Post date:** [January 18, 2015, 3:19am UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/3 "2015-01-18T03:19:23Z")

</div>

Apologies, I forgot to post a link to where we’ve merged the fix. It was just yesterday: [Bump chef-gem to 11.18.0. by tylercloke · Pull Request #667 · chef-boneyard/opscode-omnibus · GitHub](https://github.com/opscode/opscode-omnibus/pull/667/files)

Cheers!

—  
Stephen Delano - Engineering Lead, Chef

On Sat, Jan 17, 2015 at 7:17 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
wrote:

> # Hi Charles, The libyajl warning is a know issues and is fixed on the master branch of the Chef Server. This is simply a warning and, as far as we know, doesn’t cause any errors in the operation of the Chef Server. Is the output that you posted the complete output of the script you have run? — Stephen Delano - Engineering Lead, Chef On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com), wrote: 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 wget [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb) dpkg -i chef-server-core\_12.0.1-1\_amd64.deb chef-server-ctl reconfigure chef-server-ctl user-create CharlesTBetz Charles Betz [char@erp4it.com](mailto:char@erp4it.com) 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 [Install the Chef Infra Server](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

---

<div class="post-metadata">

**Author:** ![Charles\_Betz](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@Charles\_Betz](https://discourse.chef.io/u/Charles_Betz)\
**Post date:** [January 18, 2015, 3:24am UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/4 "2015-01-18T03:24:46Z")

</div>

Hi Stephen, I appreciate the quick response.

No, that output is quite lengthy of course, as is noted in the instructions  
"Because the Chef server is composed of many different services that work  
together to create a functioning system, this step may take a few minutes  
to complete." I do not see any obvious errors in that output.

However, I am still puzzled why the security credential files are  
apparently not being generated.

Based on your response, my plan would be to leave the error as is until a  
new package is released, rather than compiling on my own.

-ctb

On Sat, Jan 17, 2015 at 9:17 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com) wrote:

> Hi Charles,
> 
> The libyajl warning is a know issues and is fixed on the master branch of  
> the Chef Server.
> 
> This is simply a warning and, as far as we know, doesn’t cause any errors  
> in the operation of the Chef Server.
> 
> Is the output that you posted the complete output of the script you have  
> run?
> 
> —  
> Stephen Delano - Engineering Lead, Chef
> 
> On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> wrote:
> 
> > 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
> > 
> > wget  
> > [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)
> > 
> > dpkg -i chef-server-core\_12.0.1-1\_amd64.deb
> > 
> > chef-server-ctl reconfigure
> > 
> > chef-server-ctl user-create CharlesTBetz Charles Betz [char@erp4it.com](mailto:char@erp4it.com)  
> > 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  
> > [Install the Chef Infra Server](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

---

<div class="post-metadata">

**Author:** ![sdelano](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/sdelano/32/35_2.png) [@sdelano](https://discourse.chef.io/u/sdelano)\
**Post date:** [January 18, 2015, 3:35am UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/5 "2015-01-18T03:35:55Z")

</div>

Can you run a `chef-server-ctl user-list` and also a `chef-server-ctl org-list` to verify that the users and organizations were created like you expected. There are a few things from your script that might cause problems, and I’ll double-check locally once I get a server up and running shortly:

1. The username might not allow uppercase characters

2. Same for the organization name, and the long-form name especially needs to be contained in quotes for it to be recognized as a single command line argument.

—  
Stephen Delano - Engineering Lead, Chef

On Saturday, Jan 17, 2015 at 7:24 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com), wrote:

Hi Stephen, I appreciate the quick response.

No, that output is quite lengthy of course, as is noted in the instructions “Because the Chef server is composed of many different services that work together to create a functioning system, this step may take a few minutes to complete.” I do not see any obvious errors in that output.

However, I am still puzzled why the security credential files are apparently not being generated.

Based on your response, my plan would be to leave the error as is until a new package is released, rather than compiling on my own.

-ctb

On Sat, Jan 17, 2015 at 9:17 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com) wrote:

Hi Charles,

The libyajl warning is a know issues and is fixed on the master branch of the Chef Server.

This is simply a warning and, as far as we know, doesn’t cause any errors in the operation of the Chef Server.

Is the output that you posted the complete output of the script you have run?

—  
Stephen Delano - Engineering Lead, Chef

On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com), wrote:

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](http://piernas.calavera.biz)

apt-get -y update

wget [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)

dpkg -i chef-server-core\_12.0.1-1\_amd64.deb

chef-server-ctl reconfigure

chef-server-ctl user-create CharlesTBetz Charles Betz [char@erp4it.com](mailto:char@erp4it.com) 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](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

---

<div class="post-metadata">

**Author:** ![sdelano](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/sdelano/32/35_2.png) [@sdelano](https://discourse.chef.io/u/sdelano)\
**Post date:** [January 18, 2015, 3:49am UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/6 "2015-01-18T03:49:53Z")

</div>

Hi Charles,

Here’s the output that I get when running those two commands:

```auto

ERROR: The data in your request was invalid

Response: Field ‘username’ invalid

```

```auto

ERROR: Chef::Exceptions::ValidationFailed: Option name’s value DMA does not match regular expression /^[a-z0-9\-_]+$/

```

I excluded the yajl warning output, which probably helped obscure the actual error for you. Hope that helps! I’ll also file an issue with the chef-server project because it appears that when these commands fail they still return 0.

—  
Stephen Delano - Engineering Lead, Chef

On Sat, Jan 17, 2015 at 7:35 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
wrote:

> Can you run a `chef-server-ctl user-list` and also a `chef-server-ctl org-list` to verify that the users and organizations were created like you expected. There are a few things from your script that might cause problems, and I’ll double-check locally once I get a server up and running shortly:
> 
> 1. The username might not allow uppercase characters
> 2. Same for the organization name, and the long-form name especially needs to be contained in quotes for it to be recognized as a single command line argument.  
> —  
> Stephen Delano - Engineering Lead, Chef  
> On Saturday, Jan 17, 2015 at 7:24 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com), wrote:  
> Hi Stephen, I appreciate the quick response.  
> No, that output is quite lengthy of course, as is noted in the instructions "Because the Chef server is composed of many different services that work together to create a functioning system, this step may take a few minutes to complete." I do not see any obvious errors in that output.  
> However, I am still puzzled why the security credential files are apparently not being generated.  
> Based on your response, my plan would be to leave the error as is until a new package is released, rather than compiling on my own.  
> -ctb  
> On Sat, Jan 17, 2015 at 9:17 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com) wrote:  
> Hi Charles,  
> The libyajl warning is a know issues and is fixed on the master branch of the Chef Server.  
> This is simply a warning and, as far as we know, doesn’t cause any errors in the operation of the Chef Server.  
> Is the output that you posted the complete output of the script you have run?  
> —  
> Stephen Delano - Engineering Lead, Chef  
> On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com), wrote:  
> 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  
> wget [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)  
> dpkg -i chef-server-core\_12.0.1-1\_amd64.deb  
> chef-server-ctl reconfigure  
> chef-server-ctl user-create CharlesTBetz Charles Betz [char@erp4it.com](mailto:char@erp4it.com) 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 [Install the Chef Infra Server](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

---

<div class="post-metadata">

**Author:** ![Charles\_Betz](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@Charles\_Betz](https://discourse.chef.io/u/Charles_Betz)\
**Post date:** [January 18, 2015, 4:07am UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/7 "2015-01-18T04:07:25Z")

</div>

Excluding the yajl warning output, I don't get a string validation error as  
you suggest above. However, when I try to run the user-create command again  
with:

# chef-server-ctl user-create charb Charles Betz [char@erp4it.com](mailto:char@erp4it.com) testPass

--filename /vagrant/char-chef-cred

I get a new error:

ERROR: Specified config file /etc/opscode/pivotal.rb does not exist!

Hadn't seen this in previous output IIRC.

If I run chef-server-ctl user-list I get the same error and no other  
output.

-ctb

On Sat, Jan 17, 2015 at 9:49 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com) wrote:

> Hi Charles,
> 
> Here’s the output that I get when running those two commands:
> 
> ```auto
> 
> ERROR: The data in your request was invalid
> Response: Field ‘username’ invalid
> 
> ```
> 
> ```auto
> ERROR: Chef::Exceptions::ValidationFailed: Option name’s value DMA does
> not match regular expression /^[a-z0-9\-_]+$/
> 
> ```
> 
> I excluded the yajl warning output, which probably helped obscure the  
> actual error for you. Hope that helps! I’ll also file an issue with the  
> chef-server project because it appears that when these commands fail they  
> still return 0.
> 
> —  
> Stephen Delano - Engineering Lead, Chef
> 
> On Sat, Jan 17, 2015 at 7:35 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> wrote:
> 
> > Can you run a `chef-server-ctl user-list` and also a `chef-server-ctl org-list` to verify that the users and organizations were created like you  
> > expected. There are a few things from your script that might cause  
> > problems, and I’ll double-check locally once I get a server up and running  
> > shortly:
> > 
> > 1. The username might not allow uppercase characters
> > 2. Same for the organization name, and the long-form name especially  
> > needs to be contained in quotes for it to be recognized as a single command  
> > line argument.
> > 
> > —  
> > Stephen Delano - Engineering Lead, Chef
> > 
> > On Saturday, Jan 17, 2015 at 7:24 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > wrote:
> > 
> > > Hi Stephen, I appreciate the quick response.
> > > 
> > > No, that output is quite lengthy of course, as is noted in the  
> > > instructions "Because the Chef server is composed of many different  
> > > services that work together to create a functioning system, this step may  
> > > take a few minutes to complete." I do not see any obvious errors in  
> > > that output.
> > > 
> > > However, I am still puzzled why the security credential files are  
> > > apparently not being generated.
> > > 
> > > Based on your response, my plan would be to leave the error as is until  
> > > a new package is released, rather than compiling on my own.
> > > 
> > > -ctb
> > > 
> > > On Sat, Jan 17, 2015 at 9:17 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > > wrote:
> > > 
> > > > Hi Charles,
> > > > 
> > > > The libyajl warning is a know issues and is fixed on the master branch  
> > > > of the Chef Server.
> > > > 
> > > > This is simply a warning and, as far as we know, doesn’t cause any  
> > > > errors in the operation of the Chef Server.
> > > > 
> > > > Is the output that you posted the complete output of the script you  
> > > > have run?
> > > > 
> > > > —  
> > > > Stephen Delano - Engineering Lead, Chef
> > > > 
> > > > On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > > > wrote:
> > > > 
> > > > > 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
> > > > > 
> > > > > wget  
> > > > > [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)
> > > > > 
> > > > > dpkg -i chef-server-core\_12.0.1-1\_amd64.deb
> > > > > 
> > > > > chef-server-ctl reconfigure
> > > > > 
> > > > > chef-server-ctl user-create CharlesTBetz Charles Betz [char@erp4it.com](mailto:char@erp4it.com)  
> > > > > 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  
> > > > > [Install the Chef Infra Server](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

---

<div class="post-metadata">

**Author:** ![sdelano](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/sdelano/32/35_2.png) [@sdelano](https://discourse.chef.io/u/sdelano)\
**Post date:** [January 18, 2015, 6:03am UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/8 "2015-01-18T06:03:37Z")

</div>

Are you running the command as root, or as a user that has access to the /etc/opscode directory? That keyhole should have been created during the initial chef-server-ctl reconfigure.

—  
Sent from Mailbox

On Sat, Jan 17, 2015 at 8:08 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com) wrote:

> Excluding the yajl warning output, I don't get a string validation error as  
> you suggest above. However, when I try to run the user-create command again  
> with:
> 
> # chef-server-ctl user-create charb Charles Betz [char@erp4it.com](mailto:char@erp4it.com) testPass
> 
> --filename /vagrant/char-chef-cred  
> I get a new error:  
> ERROR: Specified config file /etc/opscode/pivotal.rb does not exist!  
> Hadn't seen this in previous output IIRC.  
> If I run chef-server-ctl user-list I get the same error and no other  
> output.  
> -ctb  
> On Sat, Jan 17, 2015 at 9:49 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com) wrote:
> 
> > Hi Charles,
> > 
> > Here’s the output that I get when running those two commands:
> > 
> > ```auto
> > 
> > ERROR: The data in your request was invalid
> > Response: Field ‘username’ invalid
> > 
> > ```
> > 
> > ```auto
> > ERROR: Chef::Exceptions::ValidationFailed: Option name’s value DMA does
> > not match regular expression /^[a-z0-9\-_]+$/
> > 
> > ```
> > 
> > I excluded the yajl warning output, which probably helped obscure the  
> > actual error for you. Hope that helps! I’ll also file an issue with the  
> > chef-server project because it appears that when these commands fail they  
> > still return 0.
> > 
> > —  
> > Stephen Delano - Engineering Lead, Chef
> > 
> > On Sat, Jan 17, 2015 at 7:35 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > wrote:
> > 
> > > Can you run a `chef-server-ctl user-list` and also a `chef-server-ctl org-list` to verify that the users and organizations were created like you  
> > > expected. There are a few things from your script that might cause  
> > > problems, and I’ll double-check locally once I get a server up and running  
> > > shortly:
> > > 
> > > 1. The username might not allow uppercase characters
> > > 2. Same for the organization name, and the long-form name especially  
> > > needs to be contained in quotes for it to be recognized as a single command  
> > > line argument.
> > > 
> > > —  
> > > Stephen Delano - Engineering Lead, Chef
> > > 
> > > On Saturday, Jan 17, 2015 at 7:24 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > > wrote:
> > > 
> > > > Hi Stephen, I appreciate the quick response.
> > > > 
> > > > No, that output is quite lengthy of course, as is noted in the  
> > > > instructions "Because the Chef server is composed of many different  
> > > > services that work together to create a functioning system, this step may  
> > > > take a few minutes to complete." I do not see any obvious errors in  
> > > > that output.
> > > > 
> > > > However, I am still puzzled why the security credential files are  
> > > > apparently not being generated.
> > > > 
> > > > Based on your response, my plan would be to leave the error as is until  
> > > > a new package is released, rather than compiling on my own.
> > > > 
> > > > -ctb
> > > > 
> > > > On Sat, Jan 17, 2015 at 9:17 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > > > wrote:
> > > > 
> > > > > Hi Charles,
> > > > > 
> > > > > The libyajl warning is a know issues and is fixed on the master branch  
> > > > > of the Chef Server.
> > > > > 
> > > > > This is simply a warning and, as far as we know, doesn’t cause any  
> > > > > errors in the operation of the Chef Server.
> > > > > 
> > > > > Is the output that you posted the complete output of the script you  
> > > > > have run?
> > > > > 
> > > > > —  
> > > > > Stephen Delano - Engineering Lead, Chef
> > > > > 
> > > > > On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > > > > wrote:
> > > > > 
> > > > > > 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
> > > > > > 
> > > > > > wget  
> > > > > > [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)
> > > > > > 
> > > > > > dpkg -i chef-server-core\_12.0.1-1\_amd64.deb
> > > > > > 
> > > > > > chef-server-ctl reconfigure
> > > > > > 
> > > > > > chef-server-ctl user-create CharlesTBetz Charles Betz [char@erp4it.com](mailto:char@erp4it.com)  
> > > > > > 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  
> > > > > > [Install the Chef Infra Server](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

---

<div class="post-metadata">

**Author:** ![Charles\_Betz](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@Charles\_Betz](https://discourse.chef.io/u/Charles_Betz)\
**Post date:** [January 18, 2015, 2:18pm UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/9 "2015-01-18T14:18:12Z")

</div>

Running it as root. The file does not appear to be on the system (find /  
-name pivotal.rb returns nothing)

On Sun, Jan 18, 2015 at 12:03 AM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
wrote:

> Are you running the command as root, or as a user that has access to the  
> /etc/opscode directory? That keyhole should have been created during the  
> initial chef-server-ctl reconfigure.
> 
> —  
> Sent from Mailbox [https://www.dropbox.com/mailbox](https://www.dropbox.com/mailbox)
> 
> On Sat, Jan 17, 2015 at 8:08 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com) wrote:
> 
> > Excluding the yajl warning output, I don't get a string validation error  
> > as you suggest above. However, when I try to run the user-create command  
> > again with:
> > 
> > # chef-server-ctl user-create charb Charles Betz [char@erp4it.com](mailto:char@erp4it.com)
> > 
> > testPass --filename /vagrant/char-chef-cred
> > 
> > I get a new error:
> > 
> > ERROR: Specified config file /etc/opscode/pivotal.rb does not exist!
> > 
> > Hadn't seen this in previous output IIRC.
> > 
> > If I run chef-server-ctl user-list I get the same error and no other  
> > output.
> > 
> > -ctb
> > 
> > On Sat, Jan 17, 2015 at 9:49 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > wrote:
> > 
> > > Hi Charles,
> > > 
> > > Here’s the output that I get when running those two commands:
> > > 
> > > ```auto
> > > 
> > > ERROR: The data in your request was invalid
> > > Response: Field ‘username’ invalid
> > > 
> > > ```
> > > 
> > > ```auto
> > > ERROR: Chef::Exceptions::ValidationFailed: Option name’s value DMA does
> > > not match regular expression /^[a-z0-9\-_]+$/
> > > 
> > > ```
> > > 
> > > I excluded the yajl warning output, which probably helped obscure the  
> > > actual error for you. Hope that helps! I’ll also file an issue with the  
> > > chef-server project because it appears that when these commands fail they  
> > > still return 0.
> > > 
> > > —  
> > > Stephen Delano - Engineering Lead, Chef
> > > 
> > > On Sat, Jan 17, 2015 at 7:35 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > > wrote:
> > > 
> > > > Can you run a `chef-server-ctl user-list` and also a `chef-server-ctl org-list` to verify that the users and organizations were created like you  
> > > > expected. There are a few things from your script that might cause  
> > > > problems, and I’ll double-check locally once I get a server up and running  
> > > > shortly:
> > > > 
> > > > 1. The username might not allow uppercase characters
> > > > 2. Same for the organization name, and the long-form name especially  
> > > > needs to be contained in quotes for it to be recognized as a single command  
> > > > line argument.
> > > > 
> > > > —  
> > > > Stephen Delano - Engineering Lead, Chef
> > > > 
> > > > On Saturday, Jan 17, 2015 at 7:24 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > > > wrote:
> > > > 
> > > > > Hi Stephen, I appreciate the quick response.
> > > > > 
> > > > > No, that output is quite lengthy of course, as is noted in the  
> > > > > instructions "Because the Chef server is composed of many different  
> > > > > services that work together to create a functioning system, this step may  
> > > > > take a few minutes to complete." I do not see any obvious errors in  
> > > > > that output.
> > > > > 
> > > > > However, I am still puzzled why the security credential files are  
> > > > > apparently not being generated.
> > > > > 
> > > > > Based on your response, my plan would be to leave the error as is  
> > > > > until a new package is released, rather than compiling on my own.
> > > > > 
> > > > > -ctb
> > > > > 
> > > > > On Sat, Jan 17, 2015 at 9:17 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > > > > wrote:
> > > > > 
> > > > > > Hi Charles,
> > > > > > 
> > > > > > The libyajl warning is a know issues and is fixed on the master  
> > > > > > branch of the Chef Server.
> > > > > > 
> > > > > > This is simply a warning and, as far as we know, doesn’t cause any  
> > > > > > errors in the operation of the Chef Server.
> > > > > > 
> > > > > > Is the output that you posted the complete output of the script you  
> > > > > > have run?
> > > > > > 
> > > > > > —  
> > > > > > Stephen Delano - Engineering Lead, Chef
> > > > > > 
> > > > > > On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > > > > > wrote:
> > > > > > 
> > > > > > > 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
> > > > > > > 
> > > > > > > wget  
> > > > > > > [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)
> > > > > > > 
> > > > > > > dpkg -i chef-server-core\_12.0.1-1\_amd64.deb
> > > > > > > 
> > > > > > > chef-server-ctl reconfigure
> > > > > > > 
> > > > > > > chef-server-ctl user-create CharlesTBetz Charles Betz  
> > > > > > > [char@erp4it.com](mailto:char@erp4it.com) 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  
> > > > > > > [Install the Chef Infra Server](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

---

<div class="post-metadata">

**Author:** ![Charles\_Betz](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@Charles\_Betz](https://discourse.chef.io/u/Charles_Betz)\
**Post date:** [January 18, 2015, 2:26pm UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/10 "2015-01-18T14:26:05Z")

</div>

One other note, I was following the example at

> **[Install the Chef Infra Server](https://docs.chef.io/server/install_server/)**
>
> There are three configuration scenarios for the Chef Infra Server:
> Standalone (everything on a single machine) High availability (machines configured for front-end and back-end, allowing for failover on the back-end and load-balancing on the...

which suggests

chef-server-ctl org-create chef Chef Software, Inc. --association\_user  
stevedanno --filename /path/to/file.key

I noted that "Chef Software, Inc." was not quoted at the time and found it  
unusual. You may want to fix the web page.

Thanks again for your responsiveness.

Charlie

On Sun, Jan 18, 2015 at 8:18 AM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com) wrote:

> Running it as root. The file does not appear to be on the system (find /  
> -name pivotal.rb returns nothing)
> 
> On Sun, Jan 18, 2015 at 12:03 AM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> wrote:
> 
> > Are you running the command as root, or as a user that has access to the  
> > /etc/opscode directory? That keyhole should have been created during the  
> > initial chef-server-ctl reconfigure.
> > 
> > —  
> > Sent from Mailbox [https://www.dropbox.com/mailbox](https://www.dropbox.com/mailbox)
> > 
> > On Sat, Jan 17, 2015 at 8:08 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com) wrote:
> > 
> > > Excluding the yajl warning output, I don't get a string validation error  
> > > as you suggest above. However, when I try to run the user-create command  
> > > again with:
> > > 
> > > # chef-server-ctl user-create charb Charles Betz [char@erp4it.com](mailto:char@erp4it.com)
> > > 
> > > testPass --filename /vagrant/char-chef-cred
> > > 
> > > I get a new error:
> > > 
> > > ERROR: Specified config file /etc/opscode/pivotal.rb does not exist!
> > > 
> > > Hadn't seen this in previous output IIRC.
> > > 
> > > If I run chef-server-ctl user-list I get the same error and no other  
> > > output.
> > > 
> > > -ctb
> > > 
> > > On Sat, Jan 17, 2015 at 9:49 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > > wrote:
> > > 
> > > > Hi Charles,
> > > > 
> > > > Here’s the output that I get when running those two commands:
> > > > 
> > > > ```auto
> > > > 
> > > > ERROR: The data in your request was invalid
> > > > Response: Field ‘username’ invalid
> > > > 
> > > > ```
> > > > 
> > > > ```auto
> > > > ERROR: Chef::Exceptions::ValidationFailed: Option name’s value DMA does
> > > > not match regular expression /^[a-z0-9\-_]+$/
> > > > 
> > > > ```
> > > > 
> > > > I excluded the yajl warning output, which probably helped obscure the  
> > > > actual error for you. Hope that helps! I’ll also file an issue with the  
> > > > chef-server project because it appears that when these commands fail they  
> > > > still return 0.
> > > > 
> > > > —  
> > > > Stephen Delano - Engineering Lead, Chef
> > > > 
> > > > On Sat, Jan 17, 2015 at 7:35 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > > > wrote:
> > > > 
> > > > > Can you run a `chef-server-ctl user-list` and also a `chef-server-ctl org-list` to verify that the users and organizations were created like you  
> > > > > expected. There are a few things from your script that might cause  
> > > > > problems, and I’ll double-check locally once I get a server up and running  
> > > > > shortly:
> > > > > 
> > > > > 1. The username might not allow uppercase characters
> > > > > 2. Same for the organization name, and the long-form name especially  
> > > > > needs to be contained in quotes for it to be recognized as a single command  
> > > > > line argument.
> > > > > 
> > > > > —  
> > > > > Stephen Delano - Engineering Lead, Chef
> > > > > 
> > > > > On Saturday, Jan 17, 2015 at 7:24 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > > > > wrote:
> > > > > 
> > > > > > Hi Stephen, I appreciate the quick response.
> > > > > > 
> > > > > > No, that output is quite lengthy of course, as is noted in the  
> > > > > > instructions "Because the Chef server is composed of many different  
> > > > > > services that work together to create a functioning system, this step may  
> > > > > > take a few minutes to complete." I do not see any obvious errors in  
> > > > > > that output.
> > > > > > 
> > > > > > However, I am still puzzled why the security credential files are  
> > > > > > apparently not being generated.
> > > > > > 
> > > > > > Based on your response, my plan would be to leave the error as is  
> > > > > > until a new package is released, rather than compiling on my own.
> > > > > > 
> > > > > > -ctb
> > > > > > 
> > > > > > On Sat, Jan 17, 2015 at 9:17 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > > > > > wrote:
> > > > > > 
> > > > > > > Hi Charles,
> > > > > > > 
> > > > > > > The libyajl warning is a know issues and is fixed on the master  
> > > > > > > branch of the Chef Server.
> > > > > > > 
> > > > > > > This is simply a warning and, as far as we know, doesn’t cause any  
> > > > > > > errors in the operation of the Chef Server.
> > > > > > > 
> > > > > > > Is the output that you posted the complete output of the script you  
> > > > > > > have run?
> > > > > > > 
> > > > > > > —  
> > > > > > > Stephen Delano - Engineering Lead, Chef
> > > > > > > 
> > > > > > > On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > > > > > > wrote:
> > > > > > > 
> > > > > > > > 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
> > > > > > > > 
> > > > > > > > wget  
> > > > > > > > [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)
> > > > > > > > 
> > > > > > > > dpkg -i chef-server-core\_12.0.1-1\_amd64.deb
> > > > > > > > 
> > > > > > > > chef-server-ctl reconfigure
> > > > > > > > 
> > > > > > > > chef-server-ctl user-create CharlesTBetz Charles Betz  
> > > > > > > > [char@erp4it.com](mailto:char@erp4it.com) 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  
> > > > > > > > [Install the Chef Infra Server](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

---

<div class="post-metadata">

**Author:** ![Charles\_Betz](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@Charles\_Betz](https://discourse.chef.io/u/Charles_Betz)\
**Post date:** [January 18, 2015, 3:17pm UTC](https://discourse.chef.io/t/incompatible-c-libyajl-libs-chef-12/6177/11 "2015-01-18T15:17:31Z")

</div>

The missing pivotal.rb file and failure of the org-create command seem  
related to the sizing of the VM.

I apologize for not doing this correctly initially per the recommendations.  
[System Requirements](https://docs.chef.io/chef_system_requirements.html). I had assumed that a  
bare sandbox install did not require the full specification - my bad.

I'd consider this thread closed for now. Thanks again for the help.

On Sun, Jan 18, 2015 at 8:26 AM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com) wrote:

> One other note, I was following the example at
> 
> [Install the Chef Infra Server](http://docs.chef.io/server/install_server.html)
> 
> which suggests
> 
> chef-server-ctl org-create chef Chef Software, Inc. --association\_user  
> stevedanno --filename /path/to/file.key
> 
> I noted that "Chef Software, Inc." was not quoted at the time and found it  
> unusual. You may want to fix the web page.
> 
> Thanks again for your responsiveness.
> 
> Charlie
> 
> On Sun, Jan 18, 2015 at 8:18 AM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com) wrote:
> 
> > Running it as root. The file does not appear to be on the system (find /  
> > -name pivotal.rb returns nothing)
> > 
> > On Sun, Jan 18, 2015 at 12:03 AM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > wrote:
> > 
> > > Are you running the command as root, or as a user that has access to the  
> > > /etc/opscode directory? That keyhole should have been created during the  
> > > initial chef-server-ctl reconfigure.
> > > 
> > > —  
> > > Sent from Mailbox [https://www.dropbox.com/mailbox](https://www.dropbox.com/mailbox)
> > > 
> > > On Sat, Jan 17, 2015 at 8:08 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com) wrote:
> > > 
> > > > Excluding the yajl warning output, I don't get a string validation  
> > > > error as you suggest above. However, when I try to run the user-create  
> > > > command again with:
> > > > 
> > > > # chef-server-ctl user-create charb Charles Betz [char@erp4it.com](mailto:char@erp4it.com)
> > > > 
> > > > testPass --filename /vagrant/char-chef-cred
> > > > 
> > > > I get a new error:
> > > > 
> > > > ERROR: Specified config file /etc/opscode/pivotal.rb does not exist!
> > > > 
> > > > Hadn't seen this in previous output IIRC.
> > > > 
> > > > If I run chef-server-ctl user-list I get the same error and no other  
> > > > output.
> > > > 
> > > > -ctb
> > > > 
> > > > On Sat, Jan 17, 2015 at 9:49 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > > > wrote:
> > > > 
> > > > > Hi Charles,
> > > > > 
> > > > > Here’s the output that I get when running those two commands:
> > > > > 
> > > > > ```auto
> > > > > 
> > > > > ERROR: The data in your request was invalid
> > > > > Response: Field ‘username’ invalid
> > > > > 
> > > > > ```
> > > > > 
> > > > > ```auto
> > > > > ERROR: Chef::Exceptions::ValidationFailed: Option name’s value DMA
> > > > > does not match regular expression /^[a-z0-9\-_]+$/
> > > > > 
> > > > > ```
> > > > > 
> > > > > I excluded the yajl warning output, which probably helped obscure the  
> > > > > actual error for you. Hope that helps! I’ll also file an issue with the  
> > > > > chef-server project because it appears that when these commands fail they  
> > > > > still return 0.
> > > > > 
> > > > > —  
> > > > > Stephen Delano - Engineering Lead, Chef
> > > > > 
> > > > > On Sat, Jan 17, 2015 at 7:35 PM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com)  
> > > > > wrote:
> > > > > 
> > > > > > Can you run a `chef-server-ctl user-list` and also a `chef-server-ctl org-list` to verify that the users and organizations were created like you  
> > > > > > expected. There are a few things from your script that might cause  
> > > > > > problems, and I’ll double-check locally once I get a server up and running  
> > > > > > shortly:
> > > > > > 
> > > > > > 1. The username might not allow uppercase characters
> > > > > > 2. Same for the organization name, and the long-form name especially  
> > > > > > needs to be contained in quotes for it to be recognized as a single command  
> > > > > > line argument.
> > > > > > 
> > > > > > —  
> > > > > > Stephen Delano - Engineering Lead, Chef
> > > > > > 
> > > > > > On Saturday, Jan 17, 2015 at 7:24 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > > > > > wrote:
> > > > > > 
> > > > > > > Hi Stephen, I appreciate the quick response.
> > > > > > > 
> > > > > > > No, that output is quite lengthy of course, as is noted in the  
> > > > > > > instructions "Because the Chef server is composed of many different  
> > > > > > > services that work together to create a functioning system, this step may  
> > > > > > > take a few minutes to complete." I do not see any obvious errors in  
> > > > > > > that output.
> > > > > > > 
> > > > > > > However, I am still puzzled why the security credential files are  
> > > > > > > apparently not being generated.
> > > > > > > 
> > > > > > > Based on your response, my plan would be to leave the error as is  
> > > > > > > until a new package is released, rather than compiling on my own.
> > > > > > > 
> > > > > > > -ctb
> > > > > > > 
> > > > > > > On Sat, Jan 17, 2015 at 9:17 PM, Stephen Delano \<[stephen@opscode.com](mailto:stephen@opscode.com)
> > > > > > > 
> > > > > > > > wrote:
> > > > > > > 
> > > > > > > > Hi Charles,
> > > > > > > > 
> > > > > > > > The libyajl warning is a know issues and is fixed on the master  
> > > > > > > > branch of the Chef Server.
> > > > > > > > 
> > > > > > > > This is simply a warning and, as far as we know, doesn’t cause any  
> > > > > > > > errors in the operation of the Chef Server.
> > > > > > > > 
> > > > > > > > Is the output that you posted the complete output of the script you  
> > > > > > > > have run?
> > > > > > > > 
> > > > > > > > —  
> > > > > > > > Stephen Delano - Engineering Lead, Chef
> > > > > > > > 
> > > > > > > > On Saturday, Jan 17, 2015 at 7:10 PM, Charles Betz [char@erp4it.com](mailto:char@erp4it.com),  
> > > > > > > > wrote:
> > > > > > > > 
> > > > > > > > > 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
> > > > > > > > > 
> > > > > > > > > wget  
> > > > > > > > > [https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core\_12.0.1-1\_amd64.deb](https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.0.1-1_amd64.deb)
> > > > > > > > > 
> > > > > > > > > dpkg -i chef-server-core\_12.0.1-1\_amd64.deb
> > > > > > > > > 
> > > > > > > > > chef-server-ctl reconfigure
> > > > > > > > > 
> > > > > > > > > chef-server-ctl user-create CharlesTBetz Charles Betz  
> > > > > > > > > [char@erp4it.com](mailto:char@erp4it.com) 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  
> > > > > > > > > [Install the Chef Infra Server](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