-
Notifications
You must be signed in to change notification settings - Fork 828
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
Fail starting after upgrade to 24.3.3 due to Invalid metadata file #7003
Comments
Hi @onemoz, On my side, when I downgrade from a higher version to a lower one, I have this first error message, which is expected Then I restart with
As explained in #6555, to downgrade, you need to execute this subcommand
This subcommand changes DATABASE_METADATA.json content from
to
If you changed it manually, it should work as well, but you need to restart besu. Are you sure you changed the one that is inside besu data folder directory (--data-path parameter value) ? |
Thank @ahamlat for your prompt answer!!
I never had an issue when downgrading from 24.3.3 to 24.3.1. I was running 24.3.1 without issue, I then used the docker image 24.3.3, this shows the error describe in the issue and then because it was failing I went back to use 24.3.1, and it keeps working. So 24.3.1 always worked in my case. Only 24.3.3 was failing. I could run the command to revert the database version from v2 to v1:
Which indeed changed the file to the expected value. Then upgraded to the 24.3.3 version, and that's working now!
Thanks a lot for helping me fixing this :) Is this expected the 24.3.3 doesn't support v2 of the metadata file? |
Thanks for the update @onemoz.
|
Ha yes, sorry I assumed wrongly the medatada format one v1 and v2, when both are v2. Thanks a lot for your help! |
I'm going to close this issue then and you can re-open if you notice any unexpected behaviour. |
FYI, our discord announcement last month should give some context about what happened here:
Unfortunately, some users updated to the bad 24.3.1 release, mostly via RocketPool. We had already deleted it from the github releases page before we realised this which might be adding to the confusion here. |
Thanks! This explains everything. My bad for not joining the besu discord and look for the information there (I find discord harder/messier to search into for this kind of problem compare to github issues or regular documentation). |
@onemoz It was definitely our bad for the release mishap! |
Description
After an update from 24.3.1 to 24.3.3, Besu fails to start with
Invalid metadata file /ethclient/besu/DATABASE_METADATA.json
:The content of the file is
Which seems related to #6555
This issue has been hitting couple of people (at least in the rocket pool community, 3 or 4 people had this issue).
Doing a resync did fix the issue in their case, and the content of their
DATABASE_METADATA.json
becameI tried to backup my old
DATABASE_METADATA.json
and copy this content inside and start with 24.3.3, but that didn't work, Besu still fails starting with the same error message.When I rollback to Besu 24.3.1 and the old metadata file, this keeps working.
Expected behavior: Keep working after the upgrade to 24.3.3
Actual behavior: Besu doesn't start anymore
**Expected from the Besu team:
Thank you in advance!
The text was updated successfully, but these errors were encountered: