incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Logsdon <>
Subject HTTP Error 303 causes erlang stack trace
Date Mon, 11 Oct 2010 16:47:09 GMT

I kicked off a replication to from my local couchdb by pushing from the local

It was for a 2M doc database and all was going well up until 678K entries but then I had a
connection issue and well it's all gone horribly wrong.

Anyway basically the replication has gone from "Replicator" and I cant restart it. The erlang
stack trace in couchdb.log looks like this:

** Reason for termination == 
** {http_request_failed,<<"unhandled response code 303">>}

[Sun, 10 Oct 2010 17:29:52 GMT] [error] [<0.17737.2>] {error_report,<0.30.0>,
               {http_request_failed,<<"unhandled response code 303">>},
                {{http_request_failed,<<"unhandled response code 303">>},

Have I bumped into a bug here or....????



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message