Here is my hosts file
## # Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost fe80::1%lo0 localhost Is there anything specific you want me to check? <[email protected]> wrote: [info] [<0.804.0>] Retrying HEAD request to https://skimdb.npmjs.com/registry/express/ in 0.5 seconds due to error {conn_failed,{error,nxdomain}} nxdomain is about that the domain name does not exist or could be resolved. Does your DNS configured right? -- ,,,^..^,,, From: Sundar Sankarnarayanan <[email protected]<mailto:[email protected]>> Date: Friday, October 3, 2014 at 10:56 AM To: Sundar S <[email protected]<mailto:[email protected]>> Subject: FW: Error:not found From: Sundar Sankarnarayanan <[email protected]<mailto:[email protected]>> Date: Friday, October 3, 2014 at 10:40 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Error:not found Jeff, This is what I get when I remove “cancel:true: from the option. [info] [<0.804.0>] Retrying HEAD request to https://skimdb.npmjs.com/registry/express/ in 0.25 seconds due to error {conn_failed,{error,nxdomain}} [info] [<0.804.0>] Retrying HEAD request to https://skimdb.npmjs.com/registry/express/ in 0.5 seconds due to error {conn_failed,{error,nxdomain}} [info] [<0.804.0>] Retrying HEAD request to https://skimdb.npmjs.com/registry/express/ in 1.0 seconds due to error {conn_failed,{error,nxdomain}} [info] [<0.804.0>] Retrying HEAD request to https://skimdb.npmjs.com/registry/express/ in 2.0 seconds due to error {conn_failed,{error,nxdomain}} [info] [<0.804.0>] Retrying HEAD request to https://skimdb.npmjs.com/registry/express/ in 4.0 seconds due to error {conn_failed,{error,nxdomain}} [info] [<0.804.0>] Retrying HEAD request to https://skimdb.npmjs.com/registry/express/ in 8.0 seconds due to error {conn_failed,{error,nxdomain}} [info] [<0.804.0>] Retrying HEAD request to https://skimdb.npmjs.com/registry/express/ in 16.0 seconds due to error {conn_failed,{error,nxdomain}} [info] [<0.111.0>] 127.0.0.1 - - POST /_replicate 500 [error] [<0.805.0>] ** Generic server <0.805.0> terminating ** Last message in was {'EXIT',<0.804.0>,killed} ** When Server state == {state,"https://skimdb.npmjs.com/registry/express/";, 20,[],[], {[],[]}} ** Reason for termination == ** killed =ERROR REPORT==== 3-Oct-2014::10:07:25 === ** Generic server <0.805.0> terminating ** Last message in was {'EXIT',<0.804.0>,killed} ** When Server state == {state,"https://skimdb.npmjs.com/registry/express/";, 20,[],[], {[],[]}} ** Reason for termination == ** killed [error] [<0.805.0>] {error_report,<0.30.0>, {<0.805.0>,crash_report, [[{initial_call, {couch_replicator_httpc_pool,init,['Argument__1']}}, {pid,<0.805.0>}, {registered_name,[]}, {error_info, {exit,killed, [{gen_server,terminate,6, [{file,"gen_server.erl"},{line,746}]}, {proc_lib,init_p_do_apply,3, [{file,"proc_lib.erl"},{line,239}]}]}}, {ancestors, [<0.804.0>,couch_replicator_job_sup, couch_primary_services,couch_server_sup,<0.31.0>]}, {messages,[]}, {links,[]}, {dictionary,[]}, {trap_exit,true}, {status,running}, {heap_size,376}, {stack_size,27}, {reductions,494}], []]}} =CRASH REPORT==== 3-Oct-2014::10:07:25 === crasher: initial call: couch_replicator_httpc_pool:init/1 pid: <0.805.0> registered_name: [] exception exit: killed in function gen_server:terminate/6 (gen_server.erl, line 746) ancestors: [<0.804.0>,couch_replicator_job_sup,couch_primary_services, couch_server_sup,<0.31.0>] messages: [] links: [] dictionary: [] trap_exit: true status: running heap_size: 376 stack_size: 27 reductions: 494 neighbours: [error] [<0.111.0>] httpd 500 error response: {"error":"timeout"} > On Oct 3, 2014, at 9:41 AM, Sundar Sankarnarayanan > <[email protected]<mailto:[email protected]>> wrote: > > curl -X POST http://admin:[email protected]:5984/_replicate -d > '{"source":"https://skimdb.npmjs.com/registry";, "target":"http://admin:[email protected]:5984/registry";, "continuous":true, "create_target":true, "cancel":true}' -H "Content-Type: application/json" Why did you add "cancel":true? That's to cancel an existing replication. If there's no replication with those parameters already running, the 404 error is expected. Try taking out the cancel property. —Jens From: Sundar Sankarnarayanan <[email protected]<mailto:[email protected]>> Date: Friday, October 3, 2014 at 9:41 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Error:not found Hi, Am new to couchDB and am running into replication issues using couchDB. Environments tried this on an RHEL server and my Mac. On both environments, Am behind a proxy and have exported http_proxy and https_proxy. I also have exported no_proxy for localhost and 127.0.0.1. I do have admin account setup (Admin and admin123 password) for the local couchDB instance and my log levels are set to debug. All am trying to do is replicate from a remote ("https://skimdb.npmjs.com/registry” or http://isaacs.iriscouch.com/registry/“) to my local couch. I get a {error:not found”} and no reason is specified. The command I use is curl -X POST http://admin:[email protected]:5984/_replicate -d '{"source":"https://skimdb.npmjs.com/registry";, "target":"http://admin:[email protected]:5984/registry";, "continuous":true, "create_target":true, "cancel":true}' -H "Content-Type: application/json" I have tried with variations of this command, with admin username and password as part of the target, removing create_target, cancel and continuous, results seems to always be the same. I have a suspicion that it is because couch / Erlang behind the proxy that is not using the proxy configs, but am not able to confirm that as there is nothing more that is being logged. Could you point me in the right direction to help figure what is going on? Thanks Sundar S American Express made the following annotations ****************************************************************************** "This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you." American Express a ajouté le commentaire suivant le Ce courrier et toute pièce jointe qu'il contient sont réservés au seul destinataire indiqué et peuvent renfermer des renseignements confidentiels et privilégiés. Si vous n'êtes pas le destinataire prévu, toute divulgation, duplication, utilisation ou distribution du courrier ou de toute pièce jointe est interdite. Si vous avez reçu cette communication par erreur, veuillez nous en aviser par courrier et détruire immédiatement le courrier et les pièces jointes. Merci. ******************************************************************************
