-
Notifications
You must be signed in to change notification settings - Fork 492
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
Synchronisation failed #1430
Comments
We will need more info to debug this issue. Can you enable debug logs and attach them here? Moreover, can you share your bor config being used to start? Thanks! |
@manav2401 - From beginning onwards we haven't changed the settings, using the same Logs /lib/systemd/system/bor.service `[Unit] [Service] [Install] |
After updating the latest bor version for amoy sentry my syncing is not happening, it's stuck on particular block number for more than 2 days.
We used this command to update the version
curl -L https://raw.githubusercontent.com/maticnetwork/install/main/bor.sh | bash -s -- v1.5.5 amoy sentry
Synchronisation failed, dropping peer peer=bc18345a4b2d1b37bae59e4981aac923094fadf0fe6553416965d763a801186a err="retrieved hash chain is invalid: mismatch error"
Whitelisting milestone deferred err="chain out of sync"
The text was updated successfully, but these errors were encountered: