Hi Jeff, I think I'll need a reproducible test case or a little more
information to help debug this. mochiweb_request:send exits on any
error returned by the underlying gen_tcp:send, and unfortunately it
doesn't bother to log the reason for the error. You might try adding
a debug statement to line 125 of mochiweb_request.erl to figure out
the reason why .52 failed to serve this document GET request.
When you say that "the process has died" on .194, you mean the
replication process, right? Surely that error didn't bring down the
entire database? Best,
Adam
On Jan 28, 2009, at 10:17 AM, Jeff Hinrichs - DM&T wrote:
replicating from 192.168.2.52 [0.9.0a738346-incubating] ->
192.168.2.194 [0.9.0a738497-incubating]
-192.168.2.52:-
Eshell V5.6.4 (abort with ^G)
1> init:script_id().
{"OTP APN 181 01","R12B"}
-192.168.2.194-
Eshell V5.6.3 (abort with ^G)
1> init:script_id().
{"OTP APN 181 01","R12B"}
replication initiated in futon on .194 pulling from .52
During the process, I see this in the log...
[Wed, 28 Jan 2009 14:29:47 GMT] [debug] [<0.62.0>] 'GET'
/invoices/INV00651983?
revs=true&attachments=true&latest=true&open_revs=["3597612357"]
{1,
1}
Headers: [{'Connection',"keep-alive"},{'Host',"192.168.2.52"},{"Te",
[]}]
[Wed, 28 Jan 2009 14:29:53 GMT] [error] [<0.62.0>] Uncaught error in
HTTP request: {exit,normal}
[Wed, 28 Jan 2009 14:29:53 GMT] [debug] [<0.62.0>] Stacktrace:
[{mochiweb_request,send,2},
{couch_httpd,send_chunk,2},
{couch_httpd_db,'-db_doc_req/3-fun-1-',4},
{lists,foldl,3},
{couch_httpd_db,db_doc_req,3},
{couch_httpd_db,do_db_req,2},
{couch_httpd,handle_request,3},
{mochiweb_http,headers,4}]
[Wed, 28 Jan 2009 14:29:53 GMT] [debug] [<0.62.0>] HTTPd 500 error
response:
{"error":"error","reason":"normal"}
Checking the status of couch on .194 at this point shows that the
process has died
repeated attempts fail, on different documents
regards,
Jeff
