nxdomain (was Re: Error:not found)

[Dave Cottlehuber <dc...@jsonified.com>]

> Hi Dave,
>  
> Curl and Dig looked ok to me. Here are the results
> The curl Result is this
>  
> *
> Adding handle: conn: 0x7f93eb803000
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0x7f93eb803000) send_pipe: 1, recv_pipe: 0
> * About to connect() to proxy proxy-***** port **(#0)

Also I see your DNS issue is fixed or gone away, good.

> 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.

Next, the proxy of evil. using env vars is not sufficient for couchdb, please read

https://wiki.apache.org/couchdb/Replication#Replicating_through_a_proxy

and see if that helps. It’s not in the main documentation but I think it’s still
applicable. This should be suitable:

{
    "_id": "npm-skimdb",
    "target": “registry",
    "continuous": true,
    "owner": "admin",
    "roles": [
        "_admin"
    ],
    "source": "https://skimdb.npmjs.com/registry",
    "proxy": "http://proxy:12345"
}

I use the super http://httpie.org/ http tool:

http --json --pretty all --verbose --style fruity \
  post $COUCH/testy \
  _id=npm-skimdb \
  source=https://skimdb.npmjs.com/registry \
  target=registry \
  continuous:=true \
  owner=admin roles:='["_admin"]' \
  proxy="http://proxy:12345"

A+
Dave