Barrett Davis
Member
We've been trying to write our dApp ontop of Dash, but testnet keeps giving us a head ache! Dashd keeps dying on our containers because of a "bad peer"?
2018-04-08 18:01:17 ERROR: detected bad peer for initial headers sync, disconnecting 5478
Every time we detect a bad peer, we infinite loop into a disaster.
Part of the log:
018-04-08 18:01:16 ThreadSocketHandler -- removing node: peer=5477 addr=116.62.210.72:19999 nRefCount=1 fNetworkNode=1 fInbound=0 fMasternode=0
2018-04-08 18:01:16 ProcessMessages: advertising address 52.91.249.51:19999
2018-04-08 18:01:16 receive version message: /Dash Core:0.12.2.3/: version 70208, blocks=100127, us=52.91.249.51:35156, peer=5487
2018-04-08 18:01:16 AdvertiseLocal: advertising address 52.91.249.51:19999
2018-04-08 18:01:17 ERROR: detected bad peer for initial headers sync, disconnecting 5478
2018-04-08 18:01:17 ProcessMessages(headers, 81570 bytes) FAILED peer=5478
2018-04-08 18:01:17 ERROR: detected bad peer for initial headers sync, disconnecting 5478
Every time we detect a bad peer, we infinite loop into a disaster.
Part of the log:
018-04-08 18:01:16 ThreadSocketHandler -- removing node: peer=5477 addr=116.62.210.72:19999 nRefCount=1 fNetworkNode=1 fInbound=0 fMasternode=0
2018-04-08 18:01:16 ProcessMessages: advertising address 52.91.249.51:19999
2018-04-08 18:01:16 receive version message: /Dash Core:0.12.2.3/: version 70208, blocks=100127, us=52.91.249.51:35156, peer=5487
2018-04-08 18:01:16 AdvertiseLocal: advertising address 52.91.249.51:19999
2018-04-08 18:01:17 ERROR: detected bad peer for initial headers sync, disconnecting 5478
2018-04-08 18:01:17 ProcessMessages(headers, 81570 bytes) FAILED peer=5478