You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by "[mRg]" <em...@googlemail.com> on 2010/02/08 12:50:42 UTC
Crash errors throughout logs
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}}}}}}
Re: Crash errors throughout logs
Posted by Metin Akat <ak...@gmail.com>.
Yeah, I'm using c-l. So I have nothing to worry about then :)
On Mon, Feb 8, 2010 at 3:59 PM, [mRg] <em...@googlemail.com> wrote:
> Metin: Are you using couch-lucene ? I am and have just disabled it and have
> seen no more errors so far.
>
> On 8 February 2010 13:13, Metin Akat <ak...@gmail.com> wrote:
>
>> Yeah, same here. Gentoo, CouchDB 10.1
>>
>>
>> On Mon, Feb 8, 2010 at 1:50 PM, [mRg] <em...@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}}}}}}
>> >
>>
>
Re: Crash errors throughout logs
Posted by "[mRg]" <em...@googlemail.com>.
Metin: Are you using couch-lucene ? I am and have just disabled it and have
seen no more errors so far.
On 8 February 2010 13:13, Metin Akat <ak...@gmail.com> wrote:
> Yeah, same here. Gentoo, CouchDB 10.1
>
>
> On Mon, Feb 8, 2010 at 1:50 PM, [mRg] <em...@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}}}}}}
> >
>
Re: Crash errors throughout logs
Posted by Metin Akat <ak...@gmail.com>.
Yeah, same here. Gentoo, CouchDB 10.1
On Mon, Feb 8, 2010 at 1:50 PM, [mRg] <em...@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}}}}}}
>
Re: Crash errors throughout logs
Posted by Paul Davis <pa...@gmail.com>.
On Mon, Feb 8, 2010 at 12:12 PM, [mRg] <em...@googlemail.com> wrote:
> Are these worth worrying about or can I happily ignore them ?
>
You should be able to ignore those quite happily. Maybe we should
special case them with the other errors that we catch.
> On 8 Feb 2010, at 14:05, Paul Davis <pa...@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] <em...@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}}}}}}
>>>
>
Re: Crash errors throughout logs
Posted by "[mRg]" <em...@googlemail.com>.
Are these worth worrying about or can I happily ignore them ?
On 8 Feb 2010, at 14:05, Paul Davis <pa...@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] <em...@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}}}}}}
>>
Re: Crash errors throughout logs
Posted by Paul Davis <pa...@gmail.com>.
Those are probably just clients closing their socket before reading
the entire response.
On Mon, Feb 8, 2010 at 6:50 AM, [mRg] <em...@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}}}}}}
>