Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 82194 invoked from network); 19 Aug 2010 23:40:16 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Aug 2010 23:40:16 -0000 Received: (qmail 91015 invoked by uid 500); 19 Aug 2010 23:40:15 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 90960 invoked by uid 500); 19 Aug 2010 23:40:14 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 90952 invoked by uid 99); 19 Aug 2010 23:40:14 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Aug 2010 23:40:14 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.214.180] (HELO mail-iw0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Aug 2010 23:39:48 +0000 Received: by iwn6 with SMTP id 6so2986797iwn.11 for ; Thu, 19 Aug 2010 16:39:26 -0700 (PDT) Received: by 10.231.85.206 with SMTP id p14mr633871ibl.89.1282261165924; Thu, 19 Aug 2010 16:39:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.199.143 with HTTP; Thu, 19 Aug 2010 16:39:05 -0700 (PDT) From: Landon Clark Date: Thu, 19 Aug 2010 16:39:05 -0700 Message-ID: Subject: invalid UTF-8 JSON To: user@couchdb.apache.org Content-Type: multipart/mixed; boundary=001485e8cefc4de343048e35b13e X-Virus-Checked: Checked by ClamAV on apache.org --001485e8cefc4de343048e35b13e Content-Type: text/plain; charset=ISO-8859-1 I am using a tool called Chef to manage our servers. Chef uses CouchDB as a backend storage engine. Chef captures about 200KB of data about the configuration of each server. Occasionally, CouchDB returns an error (using both 1.0.1 on OSX 10.6 and .10.0 on Ubuntu 10.4): {"error":"bad_request","reason":"invalid UTF-8 JSON"} As far as I can tell, the JSON is valid. I have loaded it using the Ruby JSON parser and a JSONlint validator. Can someone give me a hint about how I should go about debugging this? I tried enabling debugging in CouchDB but that did not give me any more information that I can decipher. Attached in the JSON and I am trying to load it using this command: curl -X PUT -H "content-type: application/json" http://127.0.0.1:5984/test/doc -d @error.log Any help would be much appreciated. Thanks, Landon --001485e8cefc4de343048e35b13e--