Skip to content
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

changi node panicked at 'attempt to subtract with overflow' #2097

Closed
kuegi opened this issue Jun 20, 2023 · 3 comments
Closed

changi node panicked at 'attempt to subtract with overflow' #2097

kuegi opened this issue Jun 20, 2023 · 3 comments
Labels

Comments

@kuegi
Copy link
Contributor

kuegi commented Jun 20, 2023

Summary

  • node crashed during normal operation, after restart, it resynced a lot of blocks but didn't manage to catch up to tip again. (failure of sync likely is caused by all other nodes crashed too, I lost all connections)
  • see attached crash report: thread '<unnamed>' panicked at 'attempt to subtract with overflow', ain-evm/src/block.rs:89:38

crashreport_chain.txt

Environment

  • Node Version: 4.0.0 beta 2
  • Block height on bug if applicable: last block before crash: 1717493 , managed to sync only to 1717395 afterwards
  • OS with version: OSX
@kuegi kuegi added the bug label Jun 20, 2023
@kuegi kuegi changed the title crash leading to failure in sync node panicked at 'attempt to subtract with overflow' Jun 20, 2023
@kuegi kuegi changed the title node panicked at 'attempt to subtract with overflow' changi node panicked at 'attempt to subtract with overflow' Jun 20, 2023
@prasannavl
Copy link
Member

It does appear all the seed nodes for changi are down with the same log provided as above. We're starting to investigate.

@prasannavl
Copy link
Member

Leaving some notes for info:

  • beta1 will not sync freshly sync after 1712914. beta2 was to workaround those for now until the next beta was ready but has crashed the network
  • Both the changi seed nodes had been upgraded to beta2, which caused the whole network to crash.
  • Possible next steps:
    • We can just simply restart the seed nodes. However, we're investigating first to get to the bottom of the issue, before restarting, since it'll result in a chain from 1717493

@shohamc1
Copy link
Contributor

Fixed by #2098

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants