PyEthApp can't get min_peers=5 possibly because one single peer keeps timing out

My PyEthAp 1.0.3 client, running in Docker, can't get to the minimum number of peers (5). One IP number in particular is repeated over and over again. I have put "xx" in the number to protect someone's privacy. But my question is, how can I get the client to stop asking that one node to connect.

hello client_version=pyethapp/v0.9.19/linux2/py2.7.9 version=4 capabilities=[['eth', 60], ['p2p', 4]]
INFO:p2p.peermgr connecting random node=
INFO:p2p.peermgr connection timeout timeout=2.0 address=('x.x.xx.xxx', 30303)
INFO:p2p.peermgr missing peers known=4 num_peers=0 min_peers=5

Comments

  • JohnPelhamBlackJohnPelhamBlack Posts: 3Member
    edited October 2015
    ok, privacy is not a consideration, the node I get stuck on is 5.1.83.226, which apparently at one time was one of the bootstrap_nodes.

    Also, I have upgraded to version 1.0.7. I'm running the dockerfile, which I built last night.

    It did seem to work better at first, it ran all night long and got to block 346969 and stopped.
    INFO:eth.chainservice added txs=8 gas_used=168000 block=<Block(#346969 f051ebb2)>

    I stopped the docker container and started it back up but now it is stuck trying to get to 5 peers, failing repeatedly on 5.1.83.226.

    INFO:p2p.peer received hello client_version=Geth/v1.2.2-465e810c/linux/go1.5.1 version=4 capabilities=(('eth', 62), ('eth', 61))
    INFO:p2p.peermgr connecting random node=
    INFO:p2p.peermgr missing peers known=4 num_peers=1 min_peers=5
    INFO:p2p.peermgr connecting random node=
    INFO:p2p.peermgr connection timeout timeout=2.0 address=('5.1.83.226', 30303)
    INFO:p2p.peermgr missing peers known=4 num_peers=1 min_peers=5
    INFO:p2p.peermgr connecting random node=
    INFO:p2p.peermgr connection timeout timeout=2.0 address=('5.1.83.226', 30303)
Sign In or Register to comment.