[chef] Re: Re: Re: Re: Bad Request "corruption"

[Landon < >]

A couple of more points:

My version of CouchDB is 0.10.0, the default in Ubuntu 10.4 it
appears.  Is anyone else having issues with this version of CouchDB?

The JSON that I posted, though large, does appear to be valid
according to JSON lint...

Again, appreciate all thoughts.

Landon

On Tue, Aug 17, 2010 at 3:31 PM, Landon 
<
 >
 wrote:
> Hi Seth,
> First of all, thanks for helping with this.  There seems to be a
> couple of things going on:
> I find the error message in the couch log.  The start looks like this:
> [Tue, 17 Aug 2010 16:14:30 GMT] [error] [<0.24065.13>] attempted
> upload of invalid JSON
>
> The invalid JSON is 200KB large!!  Is this normal?  It appears that
> OHAI on windows is posting LARGE amounts of data.  I have attached the
> whole error line here but it seems like there is something broken if
> OHAI is posting this much data, right?
>
> The other strange thing is a few hours later the server started
> rejecting the Client key so I had to delete.  now the Client Node
> connects fine, but this is a ticking time bomb I feel.
>
> Please tell me I am not crazy??
>
> Thanks,
> Landon
>
> On Tue, Aug 17, 2010 at 2:40 PM, Seth Falcon 
> <
 >
>  wrote:
>> On Tue, Aug 17, 2010 at 12:17 PM, Landon 
>> <
 >
>>  wrote:
>>> Yes, it happens during every run.  I will have to check the log.  I
>>> will turn on teh debug logging and send what I see.
>>
>> Another thing you could explore is capturing the HTTP request that is
>> erroring out using ngrep (or other packet sniffer tool).  If we could
>> see what is getting sent, we might be able to determine where things
>> are going astray.  If you pursue this route, you could capture the
>> communication between chef-server and couchdb as well as between the
>> client and chef-server.
>>
>> + seth
>>
>