Chef-solo error

Chef Infra (archive)
1

I try to install chef server having these configs :

Version is 10.12.0
CentOS 6.2 64 bits

When ran this command got the error below:

chef-solo -c /etc/chef/solo.rb -j ~/chef.json -r

https://s3.amazonaws.com/chef-solo/bootstrap-latest.tar.gz

/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/chef-solo:25
/usr/bin/chef-solo:19:in `load’
/usr/bin/chef-solo:19
[2012-07-29T14:29:25+03:00] ERROR: Running exception handlers
[2012-07-29T14:29:25+03:00] ERROR: Exception handlers complete
[2012-07-29T14:29:25+03:00] FATAL: Stacktrace dumped to
/tmp/chef-solo/chef-stacktrace.out
[2012-07-29T14:29:25+03:00] FATAL: Mixlib::ShellOut::ShellCommandFailed:
service[rabbitmq-server] (chef-server::rabbitmq line 46) had an error:
Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but
received ‘1’

dump has this content :

cat /tmp/chef-solo/chef-stacktrace.out

Generated at Sun Jul 29 14:29:25 +0300 2012
Mixlib::ShellOut::ShellCommandFailed: service[rabbitmq-server]
(chef-server::rabbitmq line 46) had an error:
Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but
received ‘1’
---- Begin output of /sbin/service rabbitmq-server start &> /dev/null ----
STDOUT:
STDERR:
---- End output of /sbin/service rabbitmq-server start &> /dev/null ----
Ran /sbin/service rabbitmq-server start &> /dev/null returned 1
/usr/lib64/ruby/gems/1.8/gems/mixlib-shellout-1.0.0/lib/mixlib/shellout.rb:242:in
invalid!' /usr/lib64/ruby/gems/1.8/gems/mixlib-shellout-1.0.0/lib/mixlib/shellout.rb:228:inerror!’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/mixin/shell_out.rb:36:in
shell_out!' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/provider/service/simple.rb:41:instart_service’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/provider/service/init.rb:38:in
start_service' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/provider/service.rb:57:inaction_start’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/resource.rb:454:in
send' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/resource.rb:454:inrun_action’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/runner.rb:49:in
run_action' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/runner.rb:85:inconverge’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/runner.rb:85:in
each' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/runner.rb:85:inconverge’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/resource_collection.rb:94:in
execute_each_resource' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/resource_collection/stepable_iterator.rb:116:incall’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/resource_collection/stepable_iterator.rb:116:in
call_iterator_block' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/resource_collection/stepable_iterator.rb:85:instep’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/resource_collection/stepable_iterator.rb:104:in
iterate' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/resource_collection/stepable_iterator.rb:55:ineach_with_index’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/resource_collection.rb:92:in
execute_each_resource' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/runner.rb:80:inconverge’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/client.rb:330:in
converge' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/client.rb:163:inrun’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/application/solo.rb:207:in
run_application' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/application/solo.rb:195:inloop’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/…/lib/chef/application/solo.rb:195:in
run_application' /usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/../lib/chef/application.rb:70:inrun’
/usr/lib64/ruby/gems/1.8/gems/chef-10.12.0/bin/chef-solo:25
/usr/bin/chef-solo:19:in `load’

Also , two questions :

in /etc/chef/solo.rb the cookbook_path “/tmp/chef-solo/cookbooks” . Is the
/tmp correct place to save a cookbooks there ?

If I install/configure chef server this def “server_url”:
“http://localhost:4000”, will start the service on port 4000 on local
inteface only , right ? Should it be changed to real hostname of the server
.Otherwise service will listen on 127.0.0.1 only and client won’t access the
server .Please clarify .

Thanks ,

/Vlad .

2

On 2012-07-29 04:23:50, vlad.berezovski@gmail.com wrote:

Mixlib::ShellOut::ShellCommandFailed: service[rabbitmq-server]
(chef-server::rabbitmq line 46) had an error:
Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but
received '1'

It means your rabbitmq-server script failed with error code 1
instead of the expected 0. You need to figure out why that is,
possible fix the script etc.

in /etc/chef/solo.rb the cookbook_path "/tmp/chef-solo/cookbooks" . Is the
/tmp correct place to save a cookbooks there ?

Not sure there is a "right" place. We deploy chef to /opt/chef
with capistrano so our cookbook_path ends up being
/opt/chef/current/cookbooks.

If I install/configure chef server this def "server_url":
"http://localhost:4000", will start the service on port 4000 on local
inteface only , right ? Should it be changed to real hostname of the server
.Otherwise service will listen on 127.0.0.1 only and client won't access the
server .Please clarify .

If you use chef solo why are looking at this? localhost should
bind to server's private interface, and yes, you may want to use
another interface either public or private for intra host access.
What actually happens is easy to verify with netstat -4l if on
Linux.

/Allan

Allan Wind
Life Integrity, LLC
http://lifeintegrity.com

3

What may be wrong with rabbitmq-server if I just followed wiki's guide ?
Anyway , will try to reinstall the package .

I use solo as part of the server installation . that's why I assume that
server;s url should point to its hostname and not localhost .

/Vlad
On Sun, Jul 29, 2012 at 5:03 PM, Allan Wind allan_wind@lifeintegrity.comwrote:

On 2012-07-29 04:23:50, vlad.berezovski@gmail.com wrote:

Mixlib::ShellOut::ShellCommandFailed: service[rabbitmq-server]
(chef-server::rabbitmq line 46) had an error:
Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0],
but
received '1'

It means your rabbitmq-server script failed with error code 1
instead of the expected 0. You need to figure out why that is,
possible fix the script etc.

in /etc/chef/solo.rb the cookbook_path "/tmp/chef-solo/cookbooks" . Is
the
/tmp correct place to save a cookbooks there ?

Not sure there is a "right" place. We deploy chef to /opt/chef
with capistrano so our cookbook_path ends up being
/opt/chef/current/cookbooks.

If I install/configure chef server this def "server_url":
"http://localhost:4000", will start the service on port 4000 on local
inteface only , right ? Should it be changed to real hostname of the
server
.Otherwise service will listen on 127.0.0.1 only and client won't
access the
server .Please clarify .

If you use chef solo why are looking at this? localhost should
bind to server's private interface, and yes, you may want to use
another interface either public or private for intra host access.
What actually happens is easy to verify with netstat -4l if on
Linux.

/Allan

Allan Wind
Life Integrity, LLC
http://lifeintegrity.com