On Fri, Dec 11, 2009 at 6:35 PM, Will Sargent < "> > wrote:
> So I'm installing Chef for the first time on an EC2 instance using the quick
> start guide and I have hit a wall at the point where I have to add a node so
> that running "sudo chef-client" does not give me a "401" error.
>
> I have read through the managing nodes page but the documentation does notYou likely have a pending registration for this client, and it's
> give me enough information to set myself up -- I have tried adding a
> registration token, but specifying it in /etc/chef/server.rb does not seem
> to change anything, and neither does sudo chef-client -t 'token'
making it so that you can't use the validation token for it. If you
delete the registration, it should complete with the token.
> I cannot use a web browser on this instance (tried lynx, it doesn't seemWe've made this much better in the upcoming version of Chef, but for
> sufficient), so anything I do has to be doable through command line. Help?
now, you're only real interface is through the JSON file you can pass
on the command line.
You may also want to check out the version of Knife the 37 Signals folks set up:
http://gist.github.com/104080
In 0.8, you'll have a Knife that provides access to all the chef
server functionality from the CLI.
Archive powered by MHonArc 2.6.16.