Incompatible C libyajl libs -- Chef 12


#1

Greetings,

I am attempting a new Chef Server install on Vagrant 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

apt-get -y update

wget
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
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


#2

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, 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

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 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


#3

Apologies, I forgot to post a link to where we’ve merged the fix. It was just yesterday: 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
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, 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
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 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


#4

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 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,
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

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
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


#5

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, 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 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, 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

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 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


#6

Hi Charles,

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





ERROR: The data in your request was invalid

Response: Field ‘username’ invalid


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
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, 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 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, 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
    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 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

#7

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 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 wrote:

Hi Charles,

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


ERROR: The data in your request was invalid
Response: Field ‘username’ invalid
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
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,
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
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,
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

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
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


#8

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 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 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 wrote:

Hi Charles,

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


ERROR: The data in your request was invalid
Response: Field ‘username’ invalid
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
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,
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
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,
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

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
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


#9

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
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

On Sat, Jan 17, 2015 at 8:08 PM, Charles Betz 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

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
wrote:

Hi Charles,

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


ERROR: The data in your request was invalid
Response: Field ‘username’ invalid
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
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,
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
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,
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

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 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


#10

One other note, I was following the example at

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 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
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

On Sat, Jan 17, 2015 at 8:08 PM, Charles Betz 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

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
wrote:

Hi Charles,

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


ERROR: The data in your request was invalid
Response: Field ‘username’ invalid
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
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,
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
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,
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

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 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


#11

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.
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 wrote:

One other note, I was following the example at

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 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
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

On Sat, Jan 17, 2015 at 8:08 PM, Charles Betz 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

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
wrote:

Hi Charles,

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


ERROR: The data in your request was invalid
Response: Field ‘username’ invalid
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
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,
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

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,
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

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 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