Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Trinity stalls during sync

See original GitHub issue

What is wrong?

From timestamp INFO 06-06 23:06:38 till INFO 06-07 00:42:38 my trinity node synced no headers despite being connected to 10 peers (9 inbound, 1 outbound)

DEBUG LOG: https://gist.github.com/pipermerriam/f33802d8d8890af3c6c7a128e2745e75/raw/8326dec145f393626b0e402cdac77b482230518f/trinity-stalled-sync.log

How can it be fixed

Haven’t actually dug into the logs yet to see why.

Issue Analytics

State:
Created 5 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

3reactions

gsalgadocommented, Jun 7, 2018

Some interesting things to notice:

DEBUG 06-06 23:05:55 peer Already connected to 11 peers: [<Node(0x6e5c@72.36.89.13)>, <Node(0x18de@72.36.89.13)>, <Node(0x3cde@72.36.89.13)>, <Node(0x51da@72.36.89.13)>, <Node(0x3167@72.36.89.13)>, <Node(0xc342@72.36.89.13)>, <Node(0x7053@72.36.89.13)>, <Node(0xa845@72.36.89.13)>, <Node(0x45cc@72.36.89.13)>, <Node(0x3b65@178.69.199.63)>, <Node(0x42b3@210.186.135.215)>]; sleeping

Out of the 11 peers above, 9 are the same IP address, but different node IDs

INFO  06-06 23:06:02       chain  Head TD (17179869184) announced by ETHPeer <Node(0x3cde@72.36.89.13)> not higher than ours (130894749091490763), not syncing

And they seem to be behind us, so we won’t try to sync from them

DEBUG 06-06 23:52:52 peer Already connected to 10 peers: [<Node(0x6e5c@72.36.89.13)>, <Node(0x18de@72.36.89.13)>, <Node(0x3cde@72.36.89.13)>, <Node(0x51da@72.36.89.13)>, <Node(0x3167@72.36.89.13)>, <Node(0xc342@72.36.89.13)>, <Node(0x7053@72.36.89.13)>, <Node(0xa845@72.36.89.13)>, <Node(0x45cc@72.36.89.13)>, <Node(0xe6e0@72.36.89.13)>]; sleeping

Now all your peers are the same node?

DEBUG 06-07 00:43:07 server Receiving handshake from Address(72.36.89.13:udp:53558|tcp:53558)

And we keep receiving incoming handshakes from that IP

I was initially tempted to think there could be a bug in PeerPool causing us to keep peers in PeerPool._connected_nodes even after they’ve disconnected, but the fact that each of those peers have a different node ID but the same IP address suggests something malicious is going on

1reaction

carvercommented, Jun 7, 2018

Sounds similar to the eclipse attack. One of the mitigations they suggested was limiting the number of peers with the same address, IIRC, so 👍 to:

If we refused to pair with multiple peers using the same IP address it should be very unlikely for us to end up in a situation like this, where none of our connected peers have a higher TD than ourselves

Top Results From Across the Web

Syncing stalls and does not resume even after restart · Issue #74 ...

My node synced fine up to block 6678121 but doesn't seem to go beyond that (even after restarting trinity). Also the log is...

"Paul E. McKenney": Re: spinlock lockup, rcu stalls etc. - LKML

[28932.599607] BUG: spinlock lockup suspected on CPU#0, trinity-child2/6990 ... execution would serve any number of sync() requests, as long as each > ...

email 2.3.4 pop email sync stops | XDA Forums

I have had this problem in cm7 all nightly builds up to #55 and just stayed with rc1. After 8 plus hours the...

But why the 42 why not in sync : r/pokemongo - Reddit

Here are a few things to keep in mind: Rule 3 - No Cheating, suggesting cheating, naming cheating tools and more. Please take...

NVIDIA/Troubleshooting - ArchWiki

If vsync is enabled by the driver it will sync to only one of these ... If, while using the legacy NVIDIA drivers,...