-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest snapshot doesn't work on 1.2.5 and 1.2.4 #372
Comments
Try remove --maxpeers. and add --log.dir.verbosity=dbug. |
@blxdyx Looks like debug logs didn't add new entries:
|
logs in /home/erigon/.local/share/erigon/logs? |
Yes |
Do you check the checksum? It should have dbug logs. |
Sorry, but I don't see checksum directory.
|
Tried to restore it on different node, have the same issue |
After unwind, same issue but for different block number:
|
Get the peer info |
Peer info:
|
Looks like it's start sync when I delete |
Why add this, we have hardcode in the binary. |
It was added long time ago, I didn't remember the reason. I think we can close the issue. Thx for your help @blxdyx. |
Looks like it's stop working again :( Any suggestion on this?
|
I try to unwind multiple blocks, but didn't help. I don't see Reject header issue, but initial issue still here
|
It should have error log before "rejected header" . |
Sorry, after I unwind it, I don't have this |
"dups=884860" means you received so much block, but are old blocks, means that you don't connect the good peers. |
I have big number in maxpeers(400). Now I see message the peer count is 100. But it doesn't fix the issue:
|
Have remove |
Yes, I've removed it. I have |
Try set |
|
Maybe need run a new node from the snapshots in a new dir. There are no useful debug logs. Actually i don't know the problem. |
Restored from older snapshot(0326) on different node, but have the same issue:
it's really strange cause this snapshot works for me before for different erigon deployment with the same configuration. Tried to enable debug logs |
Hi, did you solve this? |
No, didn't fix it yet. Waiting for new snapshots to try. |
@0xdefo Start syncing after I've executed the command:
|
Thanks, I will try |
System information
Tested on v1.2.5 and 1.2.4
OS & Version: Windows/Linux/OSX
k8s 1.27.2
Erigon Command (with flags/config):
Chain/Network:
bsc
Expected behaviour
Node sync after I restore from latest snapshot.
Actual behaviour
Node doesn't sync and does not show any errors:
Steps to reproduce the behaviour
Restore snapshot from this. Start node.
The text was updated successfully, but these errors were encountered: