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
You ran the 1.10.22 previously right? You have to set the head back to the point you upgraded to 1.10.22 and re-import the chain in between. We had a regression in 1.10.22 which will lose some data.
It seems that you have fixed the original panic in #25575, so I am going to close this.
You ran the 1.10.22 previously right?
No I am running on the dev branch, not the stable channel. tried debug.setHead serveral times, still got
ERROR[09-02|14:38:42.796] Failed to retrieve beacon bounds for bad block reporting err="beacon sync not yet started"
WARN [09-02|14:38:42.797] Synchronisation failed, dropping peer peer=d5c94cfcfe2358133274d9a3c6d9e4bc766f0c1355c05565185e89ecb1e7f6c2 err="retrieved hash chain is invalid: invalid merkle root (remote: 7cc7e88cb15e7431fd61cdc8742decc9d1909dde5ff7e3e50a96006e07e1b954 local: 9168df37cb64cde9b78d788b0aa3973f6330a42c0a962de64ec2d4f9a8968f43)"
WARN [09-02|14:38:42.797] Synchronisation failed, retrying err="peer is unknown or unhealthy"
INFO [09-02|14:40:14.216] New local node record seq=1,655,740,187,340 id=2210dd52ea14560d ip=123.122.163.59 udp=30303 tcp=30303
Geth
Version: 1.11.0-unstable
Git Commit: 511bf8f18801520bf4e0c7e4d098a17d0665bc89
Git Commit Date: 20220901
Architecture: amd64
Go Version: go1.19
Operating System: linux
GOPATH=
GOROOT=
System information
Geth
Version: 1.11.0-unstable
Git Commit: d10c280
Git Commit Date: 20220831
Architecture: amd64
Go Version: go1.19
Operating System: linux
Expected behaviour
should not panic
Actual behaviour
panics
Steps to reproduce the behaviour
geth --cache 8000 --http --http.api eth,net,engine,admin --authrpc.jwtsecret /tmp/jwts
prysm.sh beacon-chain --http-web3provider=http://localhost:8551 --mainnet --jwt-secret=/tmp/jwts
After this panic, restart the node can not sync any more due to
Backtrace
The text was updated successfully, but these errors were encountered: