Title: Multiple *coin p2pools, same error -- Twisted ? Post by: airborne305 on May 04, 2013, 07:38:25 PM ***note: i am pretty new to the Linux world. Following different tutorials for the different *coins, i ended up with stuff under the USERNAME and under ROOT. so i relocated, CHMOD'ed a few things and CHOWN'ed things to fall under USERNAME. When running any of the *coind's, they all seem to download the blocks and create the file structure in the appropriate place; under /home/USERNAME/.*coin/***
I setup a multi-p2pool in Debian. while all the *coind's (bitcoin, feathercoin, litecoin, namecoin, and terracoin) run fine and download the blocks and all of that, when i run ~/p2pool/run_p2pool.py i get the below error in a constant rotation on all of the different coin pools. i previously had a bitcoin p2pool running just fine. when i started adding the other *coin pools and trying to organize the files/folders/permissions, i feel i may have messed something up. Code: 2013-05-04 12:19:18.052282 > Error while checking Bitcoin connection: in the *coin.conf files, they are all fairly cookie cutter configs. one thing i am not sure about is, assigning unique RPC ports and ports. since the RPC port is local, i imagine i could make it whatever i want as long as the python launch has that same port specified. now the "port=" im not sure about. is "port=" just my outbound connection port? or is this something specific? please advise heres an example of a *.coin.conf file. Code: server=1 .bitcoin/bitcoin.conf Code: rpcport=3332 .litecoin/litecoin.conf Code: rpcport=3333 .namecoin/namecoin.conf Code: rpcport=3334 .feathercoin/feathercoin.conf Code: rpcport=3335 and so on. |