You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Syncing should happen without errors. Issue without action from my part 24 hours ago. Restarted eth and lighthouse beacon and validator without success.
Restarting geth makes it look for peers again, but I cannot see from the logs that it ever starts syncing. I have 41 (tried 43) peers currently - shouldn't it start syncing with that many?
Your consensus client is pushing an invalid payload to you. Maybe it's some issues in consensus layer client. Can you share a bit more logs from Geth side?
System information
Geth
Version: 1.10.26-stable
Git Commit: e5eb32a
Architecture: amd64
Go Version: go1.18.5
Operating System: linux
GOPATH=
GOROOT=go
Linux 5.4.0-100-generic #113-Ubuntu SMP Thu Feb 3 18:43:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Lighthouse v3.2.1-6d5a2b5
BLS library: blst-modern
SHA256 hardware acceleration: false
Specs: mainnet (true), minimal (false), gnosis (true)
Expected behaviour
Syncing should happen without errors. Issue without action from my part 24 hours ago. Restarted eth and lighthouse beacon and validator without success.
Restarting geth makes it look for peers again, but I cannot see from the logs that it ever starts syncing. I have 41 (tried 43) peers currently - shouldn't it start syncing with that many?
eth.syncing
returnsfalse
.Actual behaviour
Unable to sync.
Steps to reproduce the behaviour
Start Geth.
out.log
The text was updated successfully, but these errors were encountered: