Python Socket exception when using cbdocloader

Hey There,
i am trying to use the cbdocloader tool to create some seed data on a remote couchbase server. Unfortunately, there seems to be some problems to establish the connection at some python code:

root@5b3bf3ddba49:/# cbdocloader -u Administrator -p SECURE -b dev -n OUR.SERVER.COM /seedData/910d771c-b685-4004-92e4-bde7aa5ec3de.json
bucket creation is successful
Exception in thread s0:
Traceback (most recent call last):
  File "/usr/lib/python2.7/", line 810, in __bootstrap_inner
  File "/usr/lib/python2.7/", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/opt/couchbase/lib/python/", line 91, in run
    rv, batch, need_backoff = self.scatter_gather(mconns, batch)
  File "/opt/couchbase/lib/python/", line 72, in scatter_gather
    rv, conn = self.find_conn(mconns, vbucket_id, msgs)
  File "/opt/couchbase/lib/python/", line 325, in find_conn
    rv, conn = CBSink.connect_mc(host, port, user, pswd)
  File "/opt/couchbase/lib/python/", line 329, in connect_mc
    mc = cb_bin_client.MemcachedClient(host, int(port))
  File "/opt/couchbase/lib/python/", line 46, in __init__
    self.s.connect_ex((host, port))
  File "/usr/lib/python2.7/", line 224, in meth
    return getattr(self._sock,name)(*args)
gaierror: [Errno -2] Name or service not known

We have not idea what is the probleme here, we already checket that all Ports are available the the couchbase server and it is also possible to connect to the Ports 8091, 11210 and 11211. The cbdocloader is installed inside of a docker container, running Ubuntu 14.04 and using python 2.7.6. Any clues and further ideas for research are welcome.

Thanks in advance and best regards,

Our SDK team has a tool, which not only checks the ports, but also does addition diagnostics of the cluster configuration and connections from the clients. Could you try to run it and post results back here? It has static binaries built for most popular platforms, but you can also build it from source using go compiler:

Thank you for the prompt reply!
We used the sdk-doctor to check our environment and already found some wrong configuration parts, we fixed this by using a correct hostname as the node name and now we do not get the python stacktrace anymore.

Unfortunately, we are still not able to really create the seedData at the remote couchbase but instead receive a SASL error for every document we try to import:

2017-05-04 11:38:48,989: s0 error: CBSink.connect() for send: error: SASL auth exception:, user: test
2017-05-04 11:38:48,989: s0 error: async operation: error: SASL auth exception:, user: test on sink: http://OUR.HOST.COM(9201faee-4b96-46db-81f1-7121110f7fb7.json@N/A)

It is a little confusing to see the output user: test because test is only the bucket name.
The cbdocloader command we are using is

cbdocloader -u Administrator -p SECURE -b dev -n OUR.SERVER.COM /seedData/company/9201faee-4b96-46db-81f1-7121110f7fb7.json

I would not expect the authentication errors because the bucket was completly new created with the same parameters before.