coKauf

coKauf

Member Since 3 years ago

Experience Points
0
follower
Lessons Completed
0
follow
Best Reply Awards
2
repos

1 contributions in the last year

Pinned
⚡ test repository
Activity
Jan
15
4 days ago
Activity icon
issue

coKauf issue comment ethereum/go-ethereum

coKauf
coKauf

Error "peer connected on snap without compatible eth support" with a private network

System information

Geth
Version: 1.10.13-stable
Git Commit: 7a0c19f813e285516f4b525305fd73b625d2dec8
Architecture: amd64
Go Version: go1.17.2
Operating System: linux
GOPATH=
GOROOT=go

Expected behaviour

I have created a private network, with a genesis file created by puppeth and using a chainId that is not already in use. I expect the peers to be able to connect to each other.

Actual behaviour

Peers fail to connect withSnapshot extension registration failed peer=af5dfeb7 err="peer connected on snap without compatible eth support"

Steps to reproduce the behaviour

  1. Take the attached genesis file and move it to a new directory
  2. Run geth init --datadir "peer1" genesis.json and geth init --datadir "peer2" genesis.json to initiate the peer
  3. In console 1 run geth --datadir "peer1" --networkid 1111 --port 30401 console 2>peer1.log
  4. In console 2 run geth --datadir "peer2" --networkid 1111 --port 30402 console 2>peer2.log
  5. In console 3 run tail -f peer1.log to see the error message

My attempted fixes

  • Setting --snapshot=false produces the same error
  • Changing the --syncmode to full, fast or light made no difference
  • Adding the peers manually with admin.addPeer(${peer1.admin.nodeInfo.enode}) returns true, however net.peerCount and admin.peers.length return 0
  • Changing the chainId did not produce any different results
  • Waiting did not help

Files

coKauf
coKauf

I have the same snapshot error even when replacing the IP address in 'peer1.admin.nodeInfo.enode' with local host.