[chef] Re: Re: EC2 AMI with chef-server installed


Chronological Thread 
  • From: Ringo De Smet < >
  • To:
  • Subject: [chef] Re: Re: EC2 AMI with chef-server installed
  • Date: Tue, 13 Apr 2010 16:00:26 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=bp5c+5Fj/pG37x8bo4if7K8Yt6bCiuXZaZdeX+odslYBdKKLG+4xrrTvujBkHCtVIe VDGPomJIQn4RtbGxCfTVEEKosBgR8D5nPmNfunPg8w8bVIrUs/Cl+PyCODRzFqVcUCrB h9ZIoDZwOliQN2iVnsi41qHn3sJzNIJwmjf4w=

John,

Thank you for posting your script. This saved me considerable time.

However, I do want to post the issues I still encountered:

1) when running chef-solo, I got this error:

[Tue, 13 Apr 2010 15:00:27 +0200] INFO:
template[/etc/sv/chef-solr/run] sending restart action to
service[chef-solr] (delayed)
[Tue, 13 Apr 2010 15:00:27 +0200] INFO:
template[/etc/sv/chef-solr/log/run] sending restart action to
service[chef-solr] (delayed)
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/mixin/command.rb:179:in
`handle_command_failures': /etc/init.d/chef-solr restart returned 1,
expected 0 (Chef::Exceptions::Exec)
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/mixin/command.rb:122:in
`run_command'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/provider/service/init.rb:53:in
`restart_service'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/provider/service.rb:87:in
`action_restart'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/runner.rb:60:in
`send'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/runner.rb:60:in
`run_action'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/runner.rb:126:in
`converge'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/runner.rb:123:in
`each'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/runner.rb:123:in
`converge'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/client.rb:319:in
`converge'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/client.rb:110:in
`run_solo'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/application/solo.rb:198:in
`run_application'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/application/solo.rb:190:in
`loop'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/application/solo.rb:190:in
`run_application'
        from 
/usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/application.rb:57:in
`run'
        from /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/chef-solo:26
        from /usr/bin/chef-solo:19:in `load'
        from /usr/bin/chef-solo:19

Running "/etc/init.d/chef-solr restart" manually did work, so I
restarted the chef-solo process. It now ended with success.

2) After that, I did a restart of 2 chef processes to workaround the
initial login problem:

/etc/init.d/chef-server restart
/etc/init.d/chef-server-webui restart

Login is now possible with the admin password listed in /etc/chef/server.rb.

That was it for me.

Ringo



Archive powered by MHonArc 2.6.16.

§