Anyone Have Chef Server 12 RC 4 Working on Centos 7


#1

Hello all,

I was wondering if anyone has had any luck getting Chef Server 12 working on Centos 7?

I was able to install the the server core and chef-manage (I had to use the RPM for that one) but when I run chef-server-ctl reconfigure I get the following failure:

- configure service runit_service[rabbitmq]

Recipe: private-chef::rabbitmq

  • execute[/opt/opscode/bin/private-chef-ctl start rabbitmq] action run
    ================================================================================
    Error executing action run on resource ‘execute[/opt/opscode/bin/private-chef-ctl start rabbitmq]’
    ================================================================================

Mixlib::ShellOut::ShellCommandFailed

Expected process to exit with [0], but received ‘1’
---- Begin output of /opt/opscode/bin/private-chef-ctl start rabbitmq ----
STDOUT: warning: rabbitmq: unable to open supervise/ok: file does not exist
STDERR:
---- End output of /opt/opscode/bin/private-chef-ctl start rabbitmq ----
Ran /opt/opscode/bin/private-chef-ctl start rabbitmq returned 1

Resource Declaration:

In /opt/opscode/embedded/cookbooks/private-chef/recipes/rabbitmq.rb

79: execute “#{opc_ctl} start rabbitmq” do
80: retries 20
81: end
82:

Compiled Resource:

Declared in /opt/opscode/embedded/cookbooks/private-chef/recipes/rabbitmq.rb:79:in `from_file’

execute("/opt/opscode/bin/private-chef-ctl start rabbitmq") do
action "run"
retries 0
retry_delay 2
guard_interpreter :default
command "/opt/opscode/bin/private-chef-ctl start rabbitmq"
backup 5
returns 0
cookbook_name :"private-chef"
recipe_name "rabbitmq"
end

Running handlers:
[2014-10-17T09:03:24-04:00] ERROR: Running exception handlers
Running handlers complete

[2014-10-17T09:03:24-04:00] ERROR: Exception handlers complete
[2014-10-17T09:03:24-04:00] FATAL: Stacktrace dumped to /opt/opscode/embedded/cookbooks/cache/chef-stacktrace.out
Chef Client failed. 2 resources updated in 83.438880821 seconds
[2014-10-17T09:03:24-04:00] ERROR: execute[/opt/opscode/bin/private-chef-ctl start rabbitmq] (private-chef::rabbitmq line 79) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received ‘1’
---- Begin output of /opt/opscode/bin/private-chef-ctl start rabbitmq ----
STDOUT: warning: rabbitmq: unable to open supervise/ok: file does not exist
STDERR:
---- End output of /opt/opscode/bin/private-chef-ctl start rabbitmq ----
Ran /opt/opscode/bin/private-chef-ctl start rabbitmq returned 1
[2014-10-17T09:03:24-04:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
[root@localhost ~]# pri
printafm printenv printf private-chef-ctl
[root@localhost ~]# pri
printafm printenv printf private-chef-ctl
[root@localhost ~]# private-chef-ctl start rabbitmq
warning: rabbitmq: unable to open supervise/ok: file does not exist
[root@localhost ~]# private-chef-ctl start rabbitmq-server
[root@localhost ~]#

Thanks,
Austin


#2

Hey Austin,

Chef hasn’t added official support for Centos 7 yet. We’re working on
shipping Chef Server12 and once that is done we’ll begin the process of
verifying and ensuring the server works and is officially supported on
Centos 7 and Ubuntu 14.04.

However, emails like this are fantastic! I encourage you to open an
issue about this on either the opscode-omnibus[1] or chef-server repo[2]
(either works, we setup the chef-server repo so everyone would have an
easy name to remember and we’ll switch to fully recommending that one in
the future). This will give us a place to track any work you’ve done and
to interact with you a way that is also easy for others to contribute.
Then once we do roll onto supporting Centos 7 the work goes faster,
because of all the knowledge you’ve provided.

For this specific issue, I’ll state the obvious and it seems something
has moved out from under rabbitmq that it expects. I believe to even
have gotten to this point you’ve already made other changes to the setup
of the server. If you open that issue and can provide all the steps
you’ve done up to this point, that will give me more information to be
able to help you figure this out. Either something you already modified
moved something rabbit expected, or the version of rabbit that ships
with the Chef Server 12 doesn’t work on Centos 7.

Thanks,

Mark Mzyk
Chef Engineer

[1] https://github.com/opscode/opscode-omnibus
[2] https://github.com/opscode/chef-server

Johnson, Austin mailto:Austin.Johnson@Kronos.com
October 17, 2014 at 9:45 AM
Hello all,

I was wondering if anyone has had any luck getting Chef Server 12
working on Centos 7?

I was able to install the the server core and chef-manage (I had to
use the RPM for that one) but when I run chef-server-ctl reconfigureI
get the following failure:

- configure service runit_service[rabbitmq]

Recipe: private-chef::rabbitmq

  • execute[/opt/opscode/bin/private-chef-ctl start rabbitmq] action run
    ================================================================================
    Error executing action run on resource
    ’execute[/opt/opscode/bin/private-chef-ctl start rabbitmq]’
    ================================================================================

Mixlib::ShellOut::ShellCommandFailed

Expected process to exit with [0], but received ‘1’
---- Begin output of /opt/opscode/bin/private-chef-ctl start rabbitmq ----
STDOUT: warning: rabbitmq: unable to open supervise/ok: file does not
exist
STDERR:
---- End output of /opt/opscode/bin/private-chef-ctl start rabbitmq ----
Ran /opt/opscode/bin/private-chef-ctl start rabbitmq returned 1

Resource Declaration:

In /opt/opscode/embedded/cookbooks/private-chef/recipes/rabbitmq.rb

79: execute “#{opc_ctl} start rabbitmq” do
80: retries 20
81: end
82:

Compiled Resource:

Declared in

/opt/opscode/embedded/cookbooks/private-chef/recipes/rabbitmq.rb:79:in
`from_file’

execute("/opt/opscode/bin/private-chef-ctl start rabbitmq") do
action "run"
retries 0
retry_delay 2
guard_interpreter :default
command "/opt/opscode/bin/private-chef-ctl start rabbitmq"
backup 5
returns 0
cookbook_name :"private-chef"
recipe_name "rabbitmq"
end

Running handlers:
[2014-10-17T09:03:24-04:00] ERROR: Running exception handlers
Running handlers complete

[2014-10-17T09:03:24-04:00] ERROR: Exception handlers complete
[2014-10-17T09:03:24-04:00] FATAL: Stacktrace dumped to
/opt/opscode/embedded/cookbooks/cache/chef-stacktrace.out
Chef Client failed. 2 resources updated in 83.438880821 seconds
[2014-10-17T09:03:24-04:00] ERROR:
execute[/opt/opscode/bin/private-chef-ctl start rabbitmq]
(private-chef::rabbitmq line 79) had an error:
Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with
[0], but received ‘1’
---- Begin output of /opt/opscode/bin/private-chef-ctl start rabbitmq ----
STDOUT: warning: rabbitmq: unable to open supervise/ok: file does not
exist
STDERR:
---- End output of /opt/opscode/bin/private-chef-ctl start rabbitmq ----
Ran /opt/opscode/bin/private-chef-ctl start rabbitmq returned 1
[2014-10-17T09:03:24-04:00] FATAL:
Chef::Exceptions::ChildConvergeError: Chef run process exited
unsuccessfully (exit code 1)
[root@localhost ~]# pri
printafm printenv printf private-chef-ctl
[root@localhost ~]# pri
printafm printenv printf private-chef-ctl
[root@localhost ~]# private-chef-ctl start rabbitmq
warning: rabbitmq: unable to open supervise/ok: file does not exist
[root@localhost ~]# private-chef-ctl start rabbitmq-server
[root@localhost ~]#

Thanks,
Austin


#3

This is probably an issue with the underlying runit cookbook, which is
actually pulled from the community for EC11/Server12 (but not
open-source 11). Github sources are here:

I see there’s no CentOS 7 in the kitchen configs on that cookbook.
Opening an issue there is probably going to be the fastest way towards
fixing it.