Can't get the p2pool node running.
Latest repo cloned
https://github.com/nzsquirrell/p2pool-nzsunitus.conf:
rpcuser=unitusrpc
rpcpassword=x
server=1
listen=1
logtimestamps=1
gen=0
daemon=1
bind=10.0.4.2
rpcallowip=10.0.4.1
rpcallowip=127.0.0.1
rpcport=50604
maxconnections=20
~/unitus_pool$ python run_p2pool.py --net unitus_bla
2015-01-06 21:00:04.270700 p2pool (version 13.3-379-g4c2764f)
2015-01-06 21:00:04.270907
2015-01-06 21:00:04.271104 Testing bitcoind RPC connection to '
http://127.0.0.1:50604/' with username 'unitusrpc'...
2015-01-06 21:00:04.301014 ...success!
2015-01-06 21:00:04.301278 Current block hash: bee05d475225005e2802200539e39f5bc031d286ef0667dc83ebf4c38690fc93
2015-01-06 21:00:04.301424 Current block height: 11999
2015-01-06 21:00:04.301512
2015-01-06 21:00:04.301628 Testing bitcoind P2P connection to '127.0.0.1:50603'...
2015-01-06 21:00:09.302095 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used...
It gets stuck @ p2p connection every time. I tried starting p2pool right after unitusd to make sure there are available slots, nothing changes.
Any ideas? Thanks
That is forcing unitusd to listen only on 10.0.4.2 for Peer-2-Peer traffic, but then p2pool is trying to connect via 127.0.0.1.
Solutions: Either remove the bind=10.0.4.2 from your unitus.conf file, or append '--bitcoind-address 10.0.4.2' to your command to start p2pool - this would force p2pool to connect to that interface in place of the loopback interface.
Let me know if you are going to make this node public and i'll add a link to it on the existing nodes. PM me your geographical location.
Thanks.