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.

Peering with Parity - Auth msg too short: 0

See original GitHub issue

What is wrong?

I run a Parity node (Parity/v1.10.4-stable-39b9f1e-20180514/x86_64-linux-gnu/rustc1.25.0), I added Trinity to my static-nodes list to try and force my nodes to talk to each other. However, it doesn’t appear that they want to peer…

Trinity Logs:

   DEBUG  05-29 16:38:16      server  Receiving handshake from Address(192.168.15.32:udp:53630|tcp:53630)
   DEBUG  05-29 16:38:16      server  Failed to decrypt handshake: Auth msg too short: 0
   DEBUG  05-29 16:38:17      server  Receiving handshake from Address(192.168.15.32:udp:53718|tcp:53718)
   DEBUG  05-29 16:38:17      server  Failed to decrypt handshake: Auth msg too short: 0
   DEBUG  05-29 16:38:17      server  Receiving handshake from Address(192.168.15.32:udp:53866|tcp:53866)
   DEBUG  05-29 16:38:17      server  Failed to decrypt handshake: Auth msg too short: 0
   DEBUG  05-29 16:38:17      server  Receiving handshake from Address(192.168.15.32:udp:53934|tcp:53934)
   DEBUG  05-29 16:38:17         eth  Sending ETH/Status msg: {'protocol_version': 63, 'network_id': 1, 'td': 17179869184, 'best_hash': b'\xd4\xe5g@\xf8v\xae\xf8\xc0\x10\xb8j@\xd5\xf5gE\xa1\x18\xd0\x90j4\xe6\x9a\xec\x8c\r\xb1\xcb\x8f\xa3', 'genesis_hash': b'\xd4\xe5g@\xf8v\xae\xf8\xc0\x10\xb8j@\xd5\xf5gE\xa1\x18\xd0\x90j4\xe6\x9a\xec\x8c\r\xb1\xcb\x8f\xa3'}
   DEBUG  05-29 16:38:17      server  Could not complete handshake: ConnectionResetError(104, 'Connection reset by peer')
   DEBUG  05-29 16:38:18      server  Receiving handshake from Address(192.168.15.32:udp:54064|tcp:54064)
   DEBUG  05-29 16:38:18         eth  Sending ETH/Status msg: {'protocol_version': 63, 'network_id': 1, 'td': 17179869184, 'best_hash': b'\xd4\xe5g@\xf8v\xae\xf8\xc0\x10\xb8j@\xd5\xf5gE\xa1\x18\xd0\x90j4\xe6\x9a\xec\x8c\r\xb1\xcb\x8f\xa3', 'genesis_hash': b'\xd4\xe5g@\xf8v\xae\xf8\xc0\x10\xb8j@\xd5\xf5gE\xa1\x18\xd0\x90j4\xe6\x9a\xec\x8c\r\xb1\xcb\x8f\xa3'}
   DEBUG  05-29 16:38:18      server  Could not complete handshake: ConnectionResetError(104, 'Connection reset by peer')
   DEBUG  05-29 16:38:19      server  Receiving handshake from Address(192.168.15.32:udp:54152|tcp:54152)
   DEBUG  05-29 16:38:19         eth  Sending ETH/Status msg: {'protocol_version': 63, 'network_id': 1, 'td': 17179869184, 'best_hash': b'\xd4\xe5g@\xf8v\xae\xf8\xc0\x10\xb8j@\xd5\xf5gE\xa1\x18\xd0\x90j4\xe6\x9a\xec\x8c\r\xb1\xcb\x8f\xa3', 'genesis_hash': b'\xd4\xe5g@\xf8v\xae\xf8\xc0\x10\xb8j@\xd5\xf5gE\xa1\x18\xd0\x90j4\xe6\x9a\xec\x8c\r\xb1\xcb\x8f\xa3'}
   DEBUG  05-29 16:38:19      server  Could not complete handshake: ConnectionResetError(104, 'Connection reset by peer')
   DEBUG  05-29 16:38:20      server  Receiving handshake from Address(192.168.15.32:udp:54248|tcp:54248)
   DEBUG  05-29 16:38:20      server  Could not complete handshake: ConnectionResetError(104, 'Connection reset by peer')
   DEBUG  05-29 16:38:21      server  Receiving handshake from Address(192.168.15.32:udp:54326|tcp:54326)
   DEBUG  05-29 16:38:21      server  Could not complete handshake: ConnectionResetError(104, 'Connection reset by peer')
   DEBUG  05-29 16:38:21      server  Receiving handshake from Address(45.77.102.136:udp:50032|tcp:50032)
   DEBUG  05-29 16:38:21      server  Could not complete handshake: No matching capabilities between us ([('eth', 63)]) and <Node(0x1a7e@45.77.102.136)> ((('les', 1),)), disconnecting

How can it be fixed

No Idea

Issue Analytics

State:
Created 5 years ago
Comments:14 (9 by maintainers)

Top GitHub Comments

3reactions

pipermerriamcommented, May 30, 2018

@MysticRyuujin

That first one is your private key (sorry!!!). We had a bug that was dumping nodekeys into the terminal (and logging) output. You should be able to remove your nodekey file and trinity will generate a new one gracefully.

rm ~/.local/share/trinity/mainnet/nodekey`

1reaction

MysticRyuujincommented, May 30, 2018

Yeah, it looks like maybe my enode id changed from my first run and I didn’t catch it. I’m not able to start my node right now 😄 but I’ll re-open if it turns out it’s still an issue after. Sorry!