[chef] Re: chef-client errors connecting to server for the first time

[Mike < >]

Did this client (or a client with the same name) exist prior to this
client registering?

If you ever did a `knife node delete` this doesn't clear the client
entry - you may have to clear the client via `knife client delete`.

Is the bootstrap placing the client's generated pem file in the
location that client.rb is looking for it?

Can you provide the output of the chef-client run in debug mode?
`chef-client -ldebug`

On Wed, Aug 8, 2012 at 2:11 PM, Kwasi Gyasi - Agyei
<
 >
 wrote:
> Entire error located here: http://pastebin.com/BEgNh2mm
>
> I'm getting these errors [http://pastebin.com/BEgNh2mm][chef-client/server
> errors] after successfully bootstrapping a node with chef.
>
> The initial error which occurs is as follows
>
> (snippet from sever logs):
>
> merb : chef-server (api) : worker (port 4000) ~ Started request handling:
> Wed Aug 08 19:04:32 +0200 2012
> merb : chef-server (api) :worker (port 4000) ~ Params: {"name"=>"devhouse",
> "controller"=>"clients", "action"=>"create", "admin"=>false}
> merb : chef-server (api) : worker (port 4000) ~ `Connection reset by peer -
> (Errno::ECONNRESET)`
>
> (snippet from client STDOUT)
>
> [2012-08-08T19:47:57+02:00] INFO: *** Chef 10.12.0 ***
> [2012-08-08T19:47:57+02:00] INFO: Client key /etc/chef/client.pem is not
> present - registering
> [2012-08-08T19:47:58+02:00] INFO: HTTP Request Returned 409 Conflict: Client
> already exists
> [2012-08-08T19:47:58+02:00] INFO: HTTP Request Returned 403 Forbidden: You
> are not allowed to take this action.
> [2012-08-08T19:47:58+02:00] FATAL: Stacktrace dumped to
> /var/chef/cache/chef-stacktrace.out
> [2012-08-08T19:47:58+02:00] FATAL: Net::HTTPServerException: 403 "Forbidden"
>
> From the above the error the only thing I can deduce is that the client
> failed to communicate with the server, but, the mind boggling thing is that,
> somehow the client was able to register with the server cause executing
> `knife client list` shows client which field in the list however updated
> attempt by client fails with `403 "Forbidden"`
>
> Chef common errors does not seem to have any records of such behavior.