I followed (https://ethereum.stackexchange.com/a/13035/4575) to connect to my private network using Parity
. Same configuration works on the different node.
Parity
halts on connection. It won't give any output or log for me to track what went wrong. What should I do to prevent this problem?
parity --chain parity.json --network-id 23422 --reserved-peers myPrivateNetwork.txt -ludp=debug,tcp=debug,sync=debug --jsonrpc-port 8546
2017-05-19 12:40:55 main INFO parity::run Starting Parity/v1.7.0-unstable-7707f75-20170327/x86_64-linux-gnu/rustc1.16.0
2017-05-19 12:40:55 main INFO parity::run State DB configuration: fast
2017-05-19 12:40:55 main INFO parity::run Operating mode: active
2017-05-19 12:40:55 main INFO ethcore::service Configured for Ebloc using Ethash engine
2017-05-19 12:40:55 hyper-client INFO miner Updated conversion rate to Ξ1 = US$110.54 (1076964100 wei/gas)
...//HALTS do not do anything.
It exits with following error message: RPC io error: Address already in use (os error 98)
. But I have doubled check that the port 8546
is empty. netstat -antu | grep "8546"
returns empty. When I try with --jsonrpc-port 8547
or different empty port number, it gives the same error message.
version Parity/v1.7.0-unstable-7707f75-20170327/x86_64-linux-gnu/rustc1.16.0
and same issue occured when I try with:--jsonrpc-port 53216
@5chdn – alper May 19 '17 at 11:39Parity
from source with:cargo build --release
@5chdn – alper May 19 '17 at 11:42nightly release
? Actually no specific reason. It was the only installation guide I was able to find. Do you suggest any other release I could try? @5chdn – alper May 19 '17 at 11:53