Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D69019F25 for ; Thu, 27 Oct 2011 19:38:40 +0000 (UTC) Received: (qmail 31735 invoked by uid 500); 27 Oct 2011 19:38:39 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 31694 invoked by uid 500); 27 Oct 2011 19:38:39 -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 31685 invoked by uid 99); 27 Oct 2011 19:38:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Oct 2011 19:38:39 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ziggythehamster@gmail.com designates 209.85.161.52 as permitted sender) Received: from [209.85.161.52] (HELO mail-fx0-f52.google.com) (209.85.161.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Oct 2011 19:38:32 +0000 Received: by faan26 with SMTP id n26so4459625faa.11 for ; Thu, 27 Oct 2011 12:38:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=FbePMcYPvTkuAEqGBfezFCHRlwxbaqAjBV38nWMRbP4=; b=sdSNAcYp1NPBH3c094KZhAdDVDyPbtMeHDqYQ9FZ/dcRqxAuHLdeWDdDuRq9h3e5bi j+wTuTWQrAPFmhiGhmZxN9pLIDlyyFPn7eLUWC5S0tB0SSvJE/wx6TWbfPagjRiYpMmc NXHjpF1RMt2/8qrI8aAuw/mN1aGxIWpcubGbk= MIME-Version: 1.0 Received: by 10.223.30.149 with SMTP id u21mr288712fac.18.1319744291891; Thu, 27 Oct 2011 12:38:11 -0700 (PDT) Sender: ziggythehamster@gmail.com Received: by 10.223.98.134 with HTTP; Thu, 27 Oct 2011 12:38:11 -0700 (PDT) Received: by 10.223.98.134 with HTTP; Thu, 27 Oct 2011 12:38:11 -0700 (PDT) In-Reply-To: <4EA9B22F.6030809@gmail.com> References: <4EA98D8E.8040302@gmail.com> <4EA9B22F.6030809@gmail.com> Date: Thu, 27 Oct 2011 14:38:11 -0500 X-Google-Sender-Auth: ykrnrfuImda_glheJ3NxnsRc-hU Message-ID: Subject: Re: Binary logs? From: Keith Gable To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=000e0ce00828b66bf704b04ce914 X-Virus-Checked: Checked by ClamAV on apache.org --000e0ce00828b66bf704b04ce914 Content-Type: text/plain; charset=ISO-8859-1 Honestly, I'd rm the log and go on my way. Am I horrible? On Oct 27, 2011 2:34 PM, "CGS" wrote: > I don't know. It may be a core dump from Erlang or other things which went > wrong when you started CouchDB for the first time. It is hard to say if the > problem cannot be reproduced. > > > > On 10/27/2011 07:04 PM, Travis Paul wrote: > >> Yeah vim shows a screen full of ^@^@^@^@ characters too, deleting them >> lets >> me view it as a test file again, but I wonder how it they got there? >> My other couch logs have those characters as well (i.e couch.log.1) >> >> On Thu, Oct 27, 2011 at 12:57 PM, CGS wrote: >> >> Try to open your file with vim and delete manually those chars at the top >>> of your file (somehow you accumulated garbage at the top of your file). >>> Save >>> it with another name if you want to keep the original (if you want next >>> time >>> not to repeat the operation, save it over the old file) and try grep >>> again. >>> >>> >>> >>> >>> On 10/27/2011 06:51 PM, Travis Paul wrote: >>> >>> It is likely an error in my code somewhere, I'm not too concerned about >>>> those errors as that app is nothing serious and needs to be taken down >>>> anyways. >>>> >>>> As for opening with less I see a bunch of "^@^@^@^@" characters filling >>>> the >>>> screen (maybe this means something in less?) and if I scroll down I can >>>> see >>>> normal log messages. >>>> >>>> I opened the file with hexedit and to be honest, had no idea what I was >>>> looking for... >>>> >>>> Using *strings* or *grep -a* works for me so, I supposed it's not a >>>> major >>>> >>>> issue, I can share the log file if you are interested. >>>> >>>> Thanks for your help >>>> >>>> >>>> On Thu, Oct 27, 2011 at 12:33 PM, Robert Newson >>>> wrote: >>>> >>>> Those are all normal ASCII values, though. You might need to open the >>>> >>>>> file in a hex editor to examine it safely. Grep is likely scanning for >>>>> bytes over 127 at the beginning of the file. >>>>> >>>>> As for the error, it looks like couchjs is crashing in your list >>>>> function, so perhaps you have a syntax error in your code? >>>>> >>>>> B. >>>>> >>>>> On 27 October 2011 17:30, Travis Paul wrote: >>>>> >>>>> I do see some errors that are probably making grep think the file is >>>>>> >>>>>> binary >>>>> >>>>> and I pasted them here http://pastebin.com/rA9kHSNF if they are at >>>>>> all >>>>>> >>>>>> of >>>>> >>>>> interest. I am unsure of their meaning. >>>>>> >>>>>> I encountered a 'bizarre' error that I want to catch, which occurred >>>>>> when >>>>>> >>>>>> I >>>>> >>>>> accessed the _rewrite url to a view and Couch returned a lot of plain >>>>>> >>>>>> text >>>>> >>>>> that looked like a stack trace, which a page refresh corrected and I >>>>>> have >>>>>> not been able to recreate. I don't recall the date when I encountered >>>>>> >>>>>> that >>>>> >>>>> error or what the error message looked like, so I'm not sure what to >>>>>> look >>>>>> for in old logs, but I never want a user to see it so I'm trying to >>>>>> catch >>>>>> >>>>>> it >>>>> >>>>> to see if it was something that I did or possibly a bug. >>>>>> >>>>>> >>>>>> On Thu, Oct 27, 2011 at 12:06 PM, Robert Newson >>>>>> >>>>>> wrote: >>>>> >>>>> Grep has a heuristic to detect text vs. binary by examining the first >>>>>> >>>>>>> part of the file. I'm curious to know what you have in, say, the >>>>>>> first >>>>>>> 100 bytes. >>>>>>> >>>>>>> couch.log is a text file, my guess is you have some strange >>>>>>> characters >>>>>>> in your log that is fooling grep. >>>>>>> >>>>>>> B. >>>>>>> >>>>>>> On 27 October 2011 16:59, Travis Paul wrote: >>>>>>> >>>>>>> If I try grep without the -a flag such as: *grep "Thu, 27 Oct 2011" >>>>>>>> couch.log* >>>>>>>> I get: *Binary file couch.log matches* >>>>>>>> >>>>>>>> tail, and head commands work as usual, but if I want to open the >>>>>>>> file >>>>>>>> >>>>>>>> in >>>>>>> >>>>>> gedit I have to do something like: *strings couch.log> >>>>>> >>>>>>> couch.log.text* >>>>>>> >>>>>> less command complains as well: *"couch.log" may be a binary file. >>>>>> >>>>>>> See >>>>>>> >>>>>> it >>>>>> >>>>>>> anyway?* >>>>>>>> >>>>>>>> On Thu, Oct 27, 2011 at 11:51 AM, Robert Newson >>>>>>>> >>>>>>>> wrote: >>>>>>> >>>>>>> couch.log is a text file with lines like; >>>>>>>> >>>>>>>>> [Thu, 27 Oct 2011 10:30:57 GMT] [info] [<0.15397.1>] 127.0.0.1 - - >>>>>>>>> >>>>>>>>> GET >>>>>>>> >>>>>>> /db1/doc1 200 >>>>>> >>>>>>> What are you seeing in there? >>>>>>>>> >>>>>>>>> B. >>>>>>>>> >>>>>>>>> On 27 October 2011 16:36, Travis Paul wrote: >>>>>>>>> >>>>>>>>> Any idea why the couchdb logs in /var/log/couchdb are binary >>>>>>>>>> files? >>>>>>>>>> >>>>>>>>>> I >>>>>>>>> >>>>>>>> have >>>>>> >>>>>>> to use *strings* or *grep -a* to do anything with them... just >>>>>>>>>> >>>>>>>>>> seemed >>>>>>>>> >>>>>>>> unusual. >>>>>> >>>>>>> Also, does anyone have a custom logwatch service for couchdb they >>>>>>>>>> >>>>>>>>>> would >>>>>>>>> >>>>>>>> like >>>>>>>> >>>>>>>>> to share? I'm going to be making one tomorrow if I can't find an >>>>>>>>>> >>>>>>>>>> existing >>>>>>>>> >>>>>>>> service. >>>>>>>> >>>>>>>>> Thanks! >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> > --000e0ce00828b66bf704b04ce914--