> On 29 Dec 2014, at 21:04 , Stephan Wissel <[email protected]> wrote: > > Hi there, > > I have a timeout problem with my replications. My replication request > roughly looks like: > (I started with https, but now test with http first, step by step) > > { > "target": "wisselblog", > "source": { > "url": "http://someserver.com/couch/wisselblog", > "auth": { > "oauth": { > "consumer_secret": somesecret", > "consumer_key": "somekey", > "token_secret": "tokensecret", > "token": "sometoken" > } > } > }, > "connection_timeout": 60000, > "user_ctx": { > "name": "stw", > "roles": ["_admin"] > } > } > > CouchDB sits behind a nginx HTTP server. When I access the database via > browser everything works nicely. > However I get timeouts and no replication when I try to replicate. > > The Error in the log looks like this: > > [Mon, 29 Dec 2014 19:38:49 GMT] [info] [<0.16786.0>] Retrying *HEAD* > request tohttp://someserver.com/couch/wisselblog in 0.25 seconds due to > error {conn_failed,{error,nxdomain}} > > I poked around with CURL and found a strange behavior of nginx: > > when executing curl -X HEAD the connection won't close (times out), only > with curl --head it works as expected.
Just for the record, curl -X HEAD is not valid curl, you mean curl -I (capital i). Best Jan -- > > I suspect (?) CouchDB does something similar as CURL? > Is there a way to fix that. Server Couch is 1.6x client 1.7 > > > Create a nice day! > Stephan H. Wissel > > Phone: +65 96673269 > Blog <http://www.wissel.net/blog> Twitter <http://twitter.com/notessensei> > Google+ <https://plus.google.com/114116118906495091782/about> Facebook > <http://www.facebook.com/stephan.wissel> LinkedIn > <http://sg.linkedin.com/in/notessensei> Xing > <https://www.xing.com/profile/StephanH_Wissel> Sametime > <http://www.wissel.net/blog/d6plinks/SHWL-84KE8U> *Skype*
signature.asc
Description: Message signed with OpenPGP using GPGMail
