Chef Server incompatible C libyajl libs


#1

I just downloaded chef-server-core_12.0.1-1_amd64.deb. I have Ubuntu 14.04
(with current updates), and that’s the download I got when I clicked
’Ubuntu 14.04’ on the chef web site.

When attempting to start chef-server…

root@chefserver-001:/etc/init.d# chef-server-ctl start
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

Apparently, it does not work. The server does not start. A status returns
the same result.

What’s going on? Solution?

Doug


#2

Hi Douglas,

The yajl warnings are a known issue
(https://github.com/opscode/chef-server/issues/53). However, I don’t
think they should be preventing your Chef server from working.
chef-server-ctl status should output the warning followed by the
status of each service. Is it doing that? If so, which services are
down? It is likely that your server is not starting for a reason
unrelated to these warnings.

Sincerely,

Steven

On Thu, Jan 15, 2015 at 5:50 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

I just downloaded chef-server-core_12.0.1-1_amd64.deb. I have Ubuntu 14.04
(with current updates), and that’s the download I got when I clicked ‘Ubuntu
14.04’ on the chef web site.

When attempting to start chef-server…

root@chefserver-001:/etc/init.d# chef-server-ctl start
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

Apparently, it does not work. The server does not start. A status returns
the same result.

What’s going on? Solution?

Doug


#3

Steven,

It’s not starting, or even reporting a status (ie not started).

root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# chef-server-ctl status
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
root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# ps -ef | grep chef
root 2173 2148 0 18:39 pts/2 00:00:00 grep --color=auto chef

Nothing is logged anywhere that I can see.

root@chefserver-001:~# find /var/log -name “chef
/var/log/chef
root@chefserver-001:~# ls -l /var/log/chef
total 4
-rw-r–r-- 1 root root 972 Jan 15 17:19 client-initial.log

That client-initial.log file is unrelated.

So, it’s not starting, reporting it’s status when not started, or even
creating any log files that I can see. This is Ubuntu 14.04 with OS updates
as of a few days ago. Very current, clean install.

Douglas.

On Thu, Jan 15, 2015 at 10:28 AM, Steven Danna steve@chef.io wrote:

Hi Douglas,

The yajl warnings are a known issue
(https://github.com/opscode/chef-server/issues/53). However, I don’t
think they should be preventing your Chef server from working.
chef-server-ctl status should output the warning followed by the
status of each service. Is it doing that? If so, which services are
down? It is likely that your server is not starting for a reason
unrelated to these warnings.

Sincerely,

Steven

On Thu, Jan 15, 2015 at 5:50 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

I just downloaded chef-server-core_12.0.1-1_amd64.deb. I have Ubuntu
14.04
(with current updates), and that’s the download I got when I clicked
’Ubuntu
14.04’ on the chef web site.

When attempting to start chef-server…

root@chefserver-001:/etc/init.d# chef-server-ctl start
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

Apparently, it does not work. The server does not start. A status returns
the same result.

What’s going on? Solution?

Doug


Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garstang@gmail.com
Cell: +1-805-340-5627


#4

The logs are in /var/log/opscode for chef server 12

I am sure there is some other issue as this warning also exists for me and
I am running on the same platform.

Does ’ chef-server-ctl service-list’ show any running chef services

On Thu, Jan 15, 2015 at 10:42 AM, Douglas Garstang doug.garstang@gmail.com
wrote:

Steven,

It’s not starting, or even reporting a status (ie not started).

root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# chef-server-ctl status
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
root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# ps -ef | grep chef
root 2173 2148 0 18:39 pts/2 00:00:00 grep --color=auto chef

Nothing is logged anywhere that I can see.

root@chefserver-001:~# find /var/log -name “chef
/var/log/chef
root@chefserver-001:~# ls -l /var/log/chef
total 4
-rw-r–r-- 1 root root 972 Jan 15 17:19 client-initial.log

That client-initial.log file is unrelated.

So, it’s not starting, reporting it’s status when not started, or even
creating any log files that I can see. This is Ubuntu 14.04 with OS updates
as of a few days ago. Very current, clean install.

Douglas.

On Thu, Jan 15, 2015 at 10:28 AM, Steven Danna steve@chef.io wrote:

Hi Douglas,

The yajl warnings are a known issue
(https://github.com/opscode/chef-server/issues/53). However, I don’t
think they should be preventing your Chef server from working.
chef-server-ctl status should output the warning followed by the
status of each service. Is it doing that? If so, which services are
down? It is likely that your server is not starting for a reason
unrelated to these warnings.

Sincerely,

Steven

On Thu, Jan 15, 2015 at 5:50 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

I just downloaded chef-server-core_12.0.1-1_amd64.deb. I have Ubuntu
14.04
(with current updates), and that’s the download I got when I clicked
’Ubuntu
14.04’ on the chef web site.

When attempting to start chef-server…

root@chefserver-001:/etc/init.d# chef-server-ctl start
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

Apparently, it does not work. The server does not start. A status
returns
the same result.

What’s going on? Solution?

Doug


Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garstang@gmail.com
Cell: +1-805-340-5627


#5

Hi Douglas,

Did you run chef-server-ctl reconfigure after the package installation?

Sincerely,

Steven

On Thu, Jan 15, 2015 at 6:42 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

Steven,

It’s not starting, or even reporting a status (ie not started).

root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# chef-server-ctl status
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
root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# ps -ef | grep chef
root 2173 2148 0 18:39 pts/2 00:00:00 grep --color=auto chef

Nothing is logged anywhere that I can see.

root@chefserver-001:~# find /var/log -name “chef
/var/log/chef
root@chefserver-001:~# ls -l /var/log/chef
total 4
-rw-r–r-- 1 root root 972 Jan 15 17:19 client-initial.log

That client-initial.log file is unrelated.

So, it’s not starting, reporting it’s status when not started, or even
creating any log files that I can see. This is Ubuntu 14.04 with OS updates
as of a few days ago. Very current, clean install.

Douglas.

On Thu, Jan 15, 2015 at 10:28 AM, Steven Danna steve@chef.io wrote:

Hi Douglas,

The yajl warnings are a known issue
(https://github.com/opscode/chef-server/issues/53). However, I don’t
think they should be preventing your Chef server from working.
chef-server-ctl status should output the warning followed by the
status of each service. Is it doing that? If so, which services are
down? It is likely that your server is not starting for a reason
unrelated to these warnings.

Sincerely,

Steven

On Thu, Jan 15, 2015 at 5:50 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

I just downloaded chef-server-core_12.0.1-1_amd64.deb. I have Ubuntu
14.04
(with current updates), and that’s the download I got when I clicked
’Ubuntu
14.04’ on the chef web site.

When attempting to start chef-server…

root@chefserver-001:/etc/init.d# chef-server-ctl start
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

Apparently, it does not work. The server does not start. A status
returns
the same result.

What’s going on? Solution?

Doug


Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garstang@gmail.com
Cell: +1-805-340-5627


#6

Steven,

No, I was not running that command, most likely because there’s absolutely
no mention of it at https://downloads.chef.io/chef-server/ubuntu/#/.

I do remember doing that in the past though on previous installs. That’s
still required?

Douglas.

On Thu, Jan 15, 2015 at 10:49 AM, Steven Danna steve@chef.io wrote:

Hi Douglas,

Did you run chef-server-ctl reconfigure after the package installation?

Sincerely,

Steven

On Thu, Jan 15, 2015 at 6:42 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

Steven,

It’s not starting, or even reporting a status (ie not started).

root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# chef-server-ctl status
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
root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# ps -ef | grep chef
root 2173 2148 0 18:39 pts/2 00:00:00 grep --color=auto chef

Nothing is logged anywhere that I can see.

root@chefserver-001:~# find /var/log -name “chef
/var/log/chef
root@chefserver-001:~# ls -l /var/log/chef
total 4
-rw-r–r-- 1 root root 972 Jan 15 17:19 client-initial.log

That client-initial.log file is unrelated.

So, it’s not starting, reporting it’s status when not started, or even
creating any log files that I can see. This is Ubuntu 14.04 with OS
updates
as of a few days ago. Very current, clean install.

Douglas.

On Thu, Jan 15, 2015 at 10:28 AM, Steven Danna steve@chef.io wrote:

Hi Douglas,

The yajl warnings are a known issue
(https://github.com/opscode/chef-server/issues/53). However, I don’t
think they should be preventing your Chef server from working.
chef-server-ctl status should output the warning followed by the
status of each service. Is it doing that? If so, which services are
down? It is likely that your server is not starting for a reason
unrelated to these warnings.

Sincerely,

Steven

On Thu, Jan 15, 2015 at 5:50 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

I just downloaded chef-server-core_12.0.1-1_amd64.deb. I have Ubuntu
14.04
(with current updates), and that’s the download I got when I clicked
’Ubuntu
14.04’ on the chef web site.

When attempting to start chef-server…

root@chefserver-001:/etc/init.d# chef-server-ctl start
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

Apparently, it does not work. The server does not start. A status
returns
the same result.

What’s going on? Solution?

Doug


Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garstang@gmail.com
Cell: +1-805-340-5627


Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garstang@gmail.com
Cell: +1-805-340-5627


#7

Hi Douglas,

Yes, chef-server-ctl reconfigure is required when installing and
upgrading chef-server. You can find the full installation docs here:
https://docs.chef.io/server/install_server.html I’ll make sure that
page is linked to from the download page if it isn’t already.

Cheers,

Steven

On Thu, Jan 15, 2015 at 6:52 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

Steven,

No, I was not running that command, most likely because there’s absolutely
no mention of it at https://downloads.chef.io/chef-server/ubuntu/#/.

I do remember doing that in the past though on previous installs. That’s
still required?

Douglas.

On Thu, Jan 15, 2015 at 10:49 AM, Steven Danna steve@chef.io wrote:

Hi Douglas,

Did you run chef-server-ctl reconfigure after the package installation?

Sincerely,

Steven

On Thu, Jan 15, 2015 at 6:42 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

Steven,

It’s not starting, or even reporting a status (ie not started).

root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# chef-server-ctl status
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
root@chefserver-001:~# chef-server-ctl start
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
root@chefserver-001:~# ps -ef | grep chef
root 2173 2148 0 18:39 pts/2 00:00:00 grep --color=auto chef

Nothing is logged anywhere that I can see.

root@chefserver-001:~# find /var/log -name “chef
/var/log/chef
root@chefserver-001:~# ls -l /var/log/chef
total 4
-rw-r–r-- 1 root root 972 Jan 15 17:19 client-initial.log

That client-initial.log file is unrelated.

So, it’s not starting, reporting it’s status when not started, or even
creating any log files that I can see. This is Ubuntu 14.04 with OS
updates
as of a few days ago. Very current, clean install.

Douglas.

On Thu, Jan 15, 2015 at 10:28 AM, Steven Danna steve@chef.io wrote:

Hi Douglas,

The yajl warnings are a known issue
(https://github.com/opscode/chef-server/issues/53). However, I don’t
think they should be preventing your Chef server from working.
chef-server-ctl status should output the warning followed by the
status of each service. Is it doing that? If so, which services are
down? It is likely that your server is not starting for a reason
unrelated to these warnings.

Sincerely,

Steven

On Thu, Jan 15, 2015 at 5:50 PM, Douglas Garstang
doug.garstang@gmail.com wrote:

I just downloaded chef-server-core_12.0.1-1_amd64.deb. I have Ubuntu
14.04
(with current updates), and that’s the download I got when I clicked
’Ubuntu
14.04’ on the chef web site.

When attempting to start chef-server…

root@chefserver-001:/etc/init.d# chef-server-ctl start
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

Apparently, it does not work. The server does not start. A status
returns
the same result.

What’s going on? Solution?

Doug


Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garstang@gmail.com
Cell: +1-805-340-5627


Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garstang@gmail.com
Cell: +1-805-340-5627