General discussion about Chef

[chef] chef-client "Bad Request"


Chronological Thread 
  • From: John Timms <john@gnoso.com>
  • To: chef@lists.opscode.com
  • Subject: [chef] chef-client "Bad Request"
  • Date: Wed, 8 Jul 2009 14:35:44 -0400
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=ALC78Qpb5dPCLsh47+Hdt+aqqHdVyfvYLO+JGVDqKPWpJhz7yoQQceU6j8tFuYMi6p KybFpC/p3mKh+SZP5hjblR7WqTlnl1lg09YeySKZ5nflS426Mwzlyidf+cFP65ftf9DN MRdvxGEN/YZCSk1nOKPZ0op7xBBXsbWpF+qmk=
When running chef-client, I am getting a 400 "Bad Request" error, instead of the 401 error that I should be getting. the server thereafter shows up in the chef-server admin interface for registrations, but even after validation, the server does not show up in the list of nodes and running chef-client again produces the same error. I'm not really sure what to do here, though I've done a good bit of searching through the documentation. Looking through the logs on the chef-server, I noticed that there was the following warning:
 
"WARNING: making https request to https://10.4.4.37/openid/server/node/juliet without verifying server certificate; no CA path was specified."
 
and on the next line:
 
"Discovery failed for https://10.4.4.37/openid/server/node/juliet: Failed to fetch identity URL https://10.4.4.37/openid/server/node/juliet : Error connecting to SSL URL https://10.4.4.37/openid/server/node/juliet: hostname does not match - (Merb::ControllerExceptions::BadRequest)"
 
What is the cause of this problem and how can I resolve it? Happy to provide more information if needed.
 
John Timms

 

Archive powered by MHonArc 2.6.16.

§