[chef] Re: Bad Request "corruption"

[Seth Falcon < >]

Hi Landon,

A couple of ideas below...

On Tue, Aug 17, 2010 at 9:31 AM, Landon 
<
 >
 wrote:
> The stack trace on the client side looks like:
> [Tue, 17 Aug 2010 09:07:20 -0700] WARN: HTTP Request Returned 500
> Internal Server Error: 400 "Bad Request"
> C:/Ruby187/lib/ruby/1.8/net/http.rb:2101:in `error!': 500 "Internal Server 
> Error
> " (Net::HTTPFatalError)
>        from 
> C:/Ruby187/lib/ruby/gems/1.8/gems/chef-0.9.8/bin/../lib/chef/rest.r
> b:229:in `api_request'
> .....

Once this starts happening, does it continue to occur for subsequent
chef-client runs?

> On the server with debug enabled, I see:
> [Tue, 17 Aug 2010 16:14:29 +0000] DEBUG: Signatures match? : 'true'
> [Tue, 17 Aug 2010 16:14:29 +0000] DEBUG: Request time difference:
> 1.149902, within 900 seconds? : true
> [Tue, 17 Aug 2010 16:14:29 +0000] DEBUG: Expected content hash is:
> '8C9sV3ubH2xoJ1cEq6/xwnPrL5o='
> [Tue, 17 Aug 2010 16:14:29 +0000] DEBUG:  Request Content Hash is:
> '8C9sV3ubH2xoJ1cEq6/xwnPrL5o='
> [Tue, 17 Aug 2010 16:14:29 +0000] DEBUG:            Hashes match?: true
> [Tue, 17 Aug 2010 16:14:29 +0000] DEBUG: Sending HTTP Request via GET
> to localhost:5984/chef/_design/id_map/_view/name_to_id
> [Tue, 17 Aug 2010 16:14:29 +0000] DEBUG: Sending HTTP Request via GET
> to localhost:5984/chef/_design/id_map/_view/name_to_id
> [Tue, 17 Aug 2010 16:14:29 +0000] DEBUG: Sending HTTP Request via PUT
> to localhost:5984/chef/a1773816-65ab-4026-a342-112ef9438106
> [Tue, 17 Aug 2010 16:14:30 +0000] WARN: HTTP Request Returned 400 Bad
> Request: bad_request
>
> I can't come up with a set of reproducible steps.  It just seems to
> "happen" suddenly. That document_id corresponds to the Node obviously,
> but I am not sure how to get more information from Couch?
>
> I would appreciate thoughts on how I can debug this further and try to
> figure out what's going on.  This is a total show stopper for me since
> I can't figure out how to prevent or fix short of deleting the node
> and readding it.

Is there anything of interest in the couchdb log file?  One thing you
could try to get more info from couchdb is to turn on debug logging
(http://localhost:5984/_utils/config.html look for the log section).

+ seth

-- 
Seth Falcon | @sfalcon | http://userprimary.net/