Is there a public EC2 AMI with chef-server installed? This would give people
a working server in under 5 minutes that they can play with.
I spent over an hour tonight and am going to bed without it working yet. A
lot of people would give up at this point if they were just checking out a
bit of software.
It took me a few hours to get my first chef server up and running.
(I found the wiki to be quite confusing. Fewer links and a diagram would have helped.)
This is what I did for ubuntu 9.10. Even then I had to contend with the ‘lost admin password’ a couple of times.
I’m in a pretty happy place now, with server, client and knife working… trying to get to grips with the cookbooks now… apache2 openid doesn’t seem to work for me.
Thanks for the script. It's nice to have an automated (and human readable)
script to install chef.
My initial password is still not working for the webui so I'm stuck. I've
changed it in /etc/chef/server.rb and restarted the webui to no avail.
How did you fix the 'lost admin password' problem?
thanks,
Mike
On Sat, Apr 3, 2010 at 4:32 AM, John Merrells john@merrells.com wrote:
It took me a few hours to get my first chef server up and running.
(I found the wiki to be quite confusing. Fewer links and a diagram would
have helped.)
This is what I did for ubuntu 9.10. Even then I had to contend with the
'lost admin password' a couple of times.
I'm in a pretty happy place now, with server, client and knife working....
trying to get to grips with the cookbooks now... apache2 openid doesn't seem
to work for me.
My initial password is still not working for the webui so I'm stuck. I've changed it in /etc/chef/server.rb and restarted the webui to no avail.
I tried that too...
How did you fix the 'lost admin password' problem?
I did 'gem uninstall chef;gem install chef' a couple of times... then i was very careful when changing the admin password... and the first thing i did was create some extra admin users just to be on the safe side
I still don't know why this happens.
Now that I'm up and running I'm not actually using the webui very much. The command line utility 'knife' is really good.
I tried this script on my local machine at home (Ubuntu 9.10) but it seems
to fail because Ohai sets 'null' for a domain. I'm trying this on my home
computer, which i'd like to access from a dyndns.org address. Anyone have a
workaround?
Thanks for the script. It's nice to have an automated (and human readable)
script to install chef.
My initial password is still not working for the webui so I'm stuck. I've
changed it in /etc/chef/server.rb and restarted the webui to no avail.
How did you fix the 'lost admin password' problem?
thanks,
Mike
On Sat, Apr 3, 2010 at 4:32 AM, John Merrells john@merrells.com wrote:
It took me a few hours to get my first chef server up and running.
(I found the wiki to be quite confusing. Fewer links and a diagram would
have helped.)
This is what I did for ubuntu 9.10. Even then I had to contend with the
'lost admin password' a couple of times.
I'm in a pretty happy place now, with server, client and knife working....
trying to get to grips with the cookbooks now... apache2 openid doesn't seem
to work for me.
On Sat, Apr 3, 2010 at 10:31 AM, Sidney Burks sid137@gmail.com wrote:
I tried this script on my local machine at home (Ubuntu 9.10) but it seems
to fail because Ohai sets 'null' for a domain. I'm trying this on my home
computer, which i'd like to access from a dyndns.org address. Anyone have a
workaround?
Thanks for the script. It's nice to have an automated (and human readable)
script to install chef.
My initial password is still not working for the webui so I'm stuck. I've
changed it in /etc/chef/server.rb and restarted the webui to no avail.
How did you fix the 'lost admin password' problem?
thanks,
Mike
On Sat, Apr 3, 2010 at 4:32 AM, John Merrells john@merrells.com wrote:
It took me a few hours to get my first chef server up and running.
(I found the wiki to be quite confusing. Fewer links and a diagram would
have helped.)
This is what I did for ubuntu 9.10. Even then I had to contend with the
'lost admin password' a couple of times.
I'm in a pretty happy place now, with server, client and knife
working.... trying to get to grips with the cookbooks now... apache2 openid
doesn't seem to work for me.
Chef Infra (archive) client directories
mkdir /etc/chef
chown root:root /etc/chef
chmod 755 /etc/chef
#install the validation key so that the chef-client can register with the chef-server
cat > /etc/chef/validation.pem <<EOF
-----BEGIN RSA PRIVATE KEY-----
XXXXXX # EDIT ME
-----END RSA PRIVATE KEY-----
EOF
On Sat, Apr 3, 2010 at 10:31 AM, Sidney Burks sid137@gmail.com wrote:
I tried this script on my local machine at home (Ubuntu 9.10) but it seems
to fail because Ohai sets 'null' for a domain. I'm trying this on my home
computer, which i'd like to access from a dyndns.org address. Anyone have a
workaround?
Thanks for the script. It's nice to have an automated (and human readable)
script to install chef.
My initial password is still not working for the webui so I'm stuck. I've
changed it in /etc/chef/server.rb and restarted the webui to no avail.
How did you fix the 'lost admin password' problem?
thanks,
Mike
On Sat, Apr 3, 2010 at 4:32 AM, John Merrells john@merrells.com wrote:
It took me a few hours to get my first chef server up and running.
(I found the wiki to be quite confusing. Fewer links and a diagram would
have helped.)
This is what I did for ubuntu 9.10. Even then I had to contend with the
'lost admin password' a couple of times.
I'm in a pretty happy place now, with server, client and knife
working.... trying to get to grips with the cookbooks now... apache2 openid
doesn't seem to work for me.
How did you fix the 'lost admin password' problem?
I did 'gem uninstall chef;gem install chef' a couple of times... then i was
very careful when changing the admin password... and the first thing i did
was create some extra admin users just to be on the safe side
Did you login using the password in /etc/chef/server.rb?
I still don't know why this happens.
I just ran your install script (from previous email) on a fresh EC2 instance
(ubuntu 9.10 i386 ami-fd5100b8) and then ran:
gem uninstall chef;gem install chef
a couple of times.
I still get 'Could not complete logging in.'
I'm trying to use chef-0.8.10. Should I try an older release?
Mike
Now that I'm up and running I'm not actually using the webui very much. The
How did you fix the 'lost admin password' problem?
I did 'gem uninstall chef;gem install chef' a couple of times... then i
was very careful when changing the admin password... and the first thing i
did was create some extra admin users just to be on the safe side
Did you login using the password in /etc/chef/server.rb?
I still don't know why this happens.
I just ran your install script (from previous email) on a fresh EC2
instance (ubuntu 9.10 i386 ami-fd5100b8) and then ran:
gem uninstall chef;gem install chef
a couple of times.
I still get 'Could not complete logging in.'
I'm trying to use chef-0.8.10. Should I try an older release?
Mike
Now that I'm up and running I'm not actually using the webui very much. The
Thank you for posting your script. This saved me considerable time.
However, I do want to post the issues I still encountered:
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:inrun_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:inaction_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:inrun_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:ineach’
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:inconverge’
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:inrun_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:inrun_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:inload’
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.
After that, I did a restart of 2 chef processes to workaround the
initial login problem:
/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.
After that, I did a restart of 2 chef processes to workaround the
initial login problem: