Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CABvT1DFq-fizJtqWj0ExtZJxgSV1xb=6ivvM-pVv1Mwb3Rgp4A@mail.gmail.com>
References: 
 <CAGjF4oyS2Vwyi8_H53zhixkFSj88ETYBi=+qifU8P0MJqwC2rg@mail.gmail.com>
	<CAHZBNKbKUMeaWu8Zk0879EFJHeVD4B+Z54Gof2tymiPs48wv7w@mail.gmail.com>
	<CABvT1DFq-fizJtqWj0ExtZJxgSV1xb=6ivvM-pVv1Mwb3Rgp4A@mail.gmail.com>
Date: Mon, 19 Mar 2012 10:54:07 +0000
Message-ID: 
 <CABvT1DE9viuGrq3umZ5L0vOdF8vZsVST8tG5xg-Y5CC2fVmHDg@mail.gmail.com>
Subject: Re: Weird error
From: Robert Newson <rnewson@apache.org>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hm, looks like it wasn't me that committed the fix, but everything still st=
ands.

On 19 March 2012 10:52, Robert Newson <rnewson@apache.org> wrote:
> The genuine error aside, the io_lib part of that is because we don't
> capture the stacktrace correctly when we log. I fixed this over on
> cloudant a while back;
>
> Couchdb does this;
>
> =A0 =A0 =A0 =A0Tag:Error ->
> =A0 =A0 =A0 =A0 =A0 =A0?LOG_ERROR("Uncaught error in HTTP request: ~p",[{=
Tag, Error}]),
> =A0 =A0 =A0 =A0 =A0 =A0?LOG_INFO("Stacktrace: ~p",[erlang:get_stacktrace(=
)]),
> =A0 =A0 =A0 =A0 =A0 =A0send_error(HttpReq, Error)
>
> The improvement is this;
>
> =A0 =A0 =A0 =A0Tag:Error ->
> =A0 =A0 =A0 =A0 =A0 =A0Stack =3D erlang:get_stacktrace(),
> =A0 =A0 =A0 =A0 =A0 =A0twig:log(error, "req_err ~p:~p ~p", [Tag, Error,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0json_stack({Error, nil, Stack})]),
> =A0 =A0 =A0 =A0 =A0 =A0send_error(HttpReq, {Error, nil, Stack})
>
> This is fixed on master but not 1.1.x or 1.2.x. Worth a backport imo
> if it's not too late for 1.2.0.
>
> B.
>
>
>
> On 19 March 2012 09:21, Dave Cottlehuber <dave@muse.net.nz> wrote:
>> On 19 March 2012 09:08, Karoly Szanto <szanto.karoly@gmail.com> wrote:
>>> Hi,
>>> In the couchDB server log file I get the following weird error that I c=
an't
>>> understand
>>>
>>> [Thu, 08 Mar 2012 02:07:29 GMT] [error] [<0.1783.0>] Uncaught error in =
HTTP
>>> request: {error,
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0{case_clause,
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {error,enotsock}}}
>>> [Thu, 08 Mar 2012 02:07:29 GMT] [info] [<0.1783.0>] Stacktrace:
>>> [{io_lib_pretty,cind_tag_tuple,7},
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {io_lib=
_pretty,while_fail,3},
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {io_lib=
_pretty,print,6},
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {io_lib=
_format,build,3},
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {io_lib=
_format,build,3},
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {io_lib=
_format,build,3},
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {io_lib=
_format,build,3},
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {io_lib=
_format,build,3}]
>>>
>>> Any hints?
>>>
>>> Thank you,
>>> Karoly
>>
>> Hi Karoly
>>
>> enotsock I think is complaining you passed a file not a socket.
>> Nothing comes to mind immediately,
>> but I'd be interested to know -
>>
>> what erlang version, OS are you running?
>> do you have multiple network interfaces, and what is your bind_address
>> set to for couchdb?
>> any relevant couch activity prior to this issue? maybe some more log
>> info would help.
>> is this repeatable, and has couch been running correctly prior?
>>
>> Some reading -
>> http://erlang.2086793.n4.nabble.com/enotsock-again-td2088701.html
>> http://erlang.2086793.n4.nabble.com/erlang-questions-Unable-to-start-eja=
bberd-or-use-TCP-IP-communication-in-erlang-interpreter-td2093426.html
>> http://comments.gmane.org/gmane.comp.lang.erlang.general/8410%3Cbr
>>
>> A+
>> Dave