Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to connect to namecoind #2

Closed
ulrichard opened this issue Jan 24, 2015 · 2 comments
Closed

Failed to connect to namecoind #2

ulrichard opened this issue Jan 24, 2015 · 2 comments

Comments

@ulrichard
Copy link

I always get "Failed to connect to namecoind" from running DyName.py
The same configuration works for p2pool, and I checked it a couple of times.

If I try it in the interactive console, I get this:

namecoind_session = AuthServiceProxy('http://ulrichard:[email protected]:
7333')
blockheight = namecoind_session.getblockcount()
Traceback (most recent call last):
File "", line 1, in
File "/home/ulrichard/sourcecode/DyName/jsonrpc/authproxy.py", line 98, in call
'Content-type' : 'application/json' })
File "/usr/lib/python3.4/http/client.py", line 1090, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python3.4/http/client.py", line 1128, in _send_request
self.endheaders(body)
File "/usr/lib/python3.4/http/client.py", line 1086, in endheaders
self._send_output(message_body)
File "/usr/lib/python3.4/http/client.py", line 924, in _send_output
self.send(msg)
File "/usr/lib/python3.4/http/client.py", line 859, in send
self.connect()
File "/usr/lib/python3.4/http/client.py", line 836, in connect
self.timeout, self.source_address)
File "/usr/lib/python3.4/socket.py", line 499, in create_connection
sock.bind(source_address)
TypeError: getsockaddrarg: AF_INET address must be tuple, not int

Here is the content of ~/.namecoin/bitcoin.conf :
server=1
daemon=1
rpcpassword=passwd
rpcport=7333
rpcuser=ulrichard
rpcallowip=192.168.2.*

@ulrichard
Copy link
Author

I played with it for a while.
With python2 it works.
With python3 I couldn't get it to run.
So I just use it with python2 for now.

@JeremyRand
Copy link
Owner

Hmm, that's interesting. I'll see if I can test sometime soon and see why Py3 would fail on this. Thanks for the report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants