Closed Johnaverse closed 10 months ago
Same here using the same version.
It seems this has been fixed on the latest commit on that branch. Just not sure if it's safe to use
Yes, this issue is fixed in release/txtracing/1.1.2-rc.6, please use this updated branch and is safe to use. Node should recover itself.
FYI, we're still running smoothly on v1.1.2-rc.5
after we missed the upgrade to rc.6
.
The latest hotfixes are now available in the following branches:
For version 1.1.2, refer to the branch release/txtracing/1.1.2-rc.6.1
.
For version 1.1.3, check out release/txtracing/1.1.3-rc.3.1
.
If you previously used the release/txtracing/1.1.2-rc.5
branch, we recommend upgrading directly to release/txtracing/1.1.2-rc.6.1
.
While the earlier hotfix addressed this specific crash, there remained potential for other related crashes. These have now been addressed in the recent update.
If you experienced this crash, It's likely that your node DB is in now a dirty state and won't restart. You can execute the command opera --datadir /path/to/datadir db heal --experimental
for recovery. When you restart your node, it will start the EVM snapshot reconstruction. This recovery process may be time-consuming, with the duration primarily influenced by your disk speed.
Duplication of #505
version: go-opera/v1.1.2-txtracing-rc.6-f8983789-1691829635
The ftm height is 67571797 and the opera crashed with following error
My parms: