incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "[mRg]" <emar...@googlemail.com>
Subject Re: Crash errors throughout logs
Date Mon, 08 Feb 2010 17:12:21 GMT
Are these worth worrying about or can I happily ignore them ?

On 8 Feb 2010, at 14:05, Paul Davis <paul.joseph.davis@gmail.com> wrote:

> Those are probably just clients closing their socket before reading
> the entire response.
>
> On Mon, Feb 8, 2010 at 6:50 AM, [mRg] <emargee@googlemail.com> wrote:
>> Hi all,
>>
>> We are moving slowly towards making our site live and was checking  
>> the
>> couchdb logs, they have masses and masses of these entries in.  
>> Having not
>> seen many couchdb errors can anyone shed any light on what these  
>> mean / how
>> i can get more information about them ?
>>
>> Any help is appreciated :)
>>
>> System info : Couchdb 0.10.0 / Redhat Enterprise Linux 5 / 4GB  
>> RAM / x64
>>
>> [Mon, 08 Feb 2010 11:31:04 GMT] [error] [<0.549.0>]  
>> {error_report,<0.21.0>,
>>    {<0.549.0>,crash_report,
>>     [[{pid,<0.549.0>},
>>       {registered_name,[]},
>>       {error_info,
>>           {error,
>>               {case_clause,{error,enotconn}},
>>               [{mochiweb_request,get,2},
>>                {couch_httpd,handle_request,5},
>>                {mochiweb_http,headers,5},
>>                {proc_lib,init_p_do_apply,3}]}},
>>
>> {initial_call,{mochiweb_socket_server,acceptor_loop, 
>> ['Argument__1']}},
>>       {ancestors,
>>            
>> [couch_httpd,couch_secondary_services,couch_server_sup,<0.1.0>]},
>>       {messages,[]},
>>       {links,[<0.61.0>,#Port<0.1514>]},
>>       {dictionary,[{mochiweb_request_qs,[]},{jsonp,undefined}]},
>>       {trap_exit,false},
>>       {status,running},
>>       {heap_size,2584},
>>       {stack_size,23},
>>       {reductions,2302}],
>>      []]}}
>>
>> [Mon, 08 Feb 2010 11:31:04 GMT] [error] [<0.61.0>]  
>> {error_report,<0.21.0>,
>>    {<0.61.0>,std_error,
>>     {mochiweb_socket_server,235,
>>         {child_error,{case_clause,{error,enotconn}}}}}}
>>

Mime
View raw message