-
Notifications
You must be signed in to change notification settings - Fork 298
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
Startup error: No enum constant tech.pegasys.teku.storage.server.StateStorageMode #8357
Comments
... 14 more |
teku-24.3.1 oracle-java-20 Ubuntu 22.04.4 LTS Configuration | Network: mainnet, Storage Mode: MINIMAL |
Description
From Discord:
This isn't the first time I have seen this issue happening. For some reason, the file
<data_folder>/beacon/data-storage-mode.txt
gets corrupted or something and causes this issue.Need to investigate under what circumstances this happens and how we can better handle it.
[Detailed description of the problem and the impact it has]
Steps to Reproduce (Bug)
Modify an existing
data-storage-mode.txt
file in the beacon data directory with an invalid value, or empty. Then start teku.Expected behavior:
Service should be able to start with no issues. Or should warn the user when something is wrong (and how to fix it).
data-storage-mode.txt
. We also log a message to let the user know.data-storage-mode.txt
file, we use the value on the file to configure the database;data-storage-mode.txt
file, we should warn the user and halt execution. In this case, we don't have a reliable way of deciding what mode makes sense. So we are going to stop and print an error message letting the user know that something is wrong, and that they should restart the node using the option--data-storage-mode
to override the existing cached config. In the end,data-storage-mode.txt
will be updated with the mode selected by the user using the option--data-storage-mode
.Actual behavior:
Node does not start and gives the error:
main | FATAL | BeaconNodeCommand | No enum constant tech.pegasys.teku.storage.server.StateStorageMode.
Frequency:
Once the conditions to trigger this problem appear, they happen consistently, until some manual intervention happens (e.g. deleting the
data-storage-mode.txt
file so it gets recreated.Versions (Add all that apply)
TODO
teku --version
or look for log lines starting withTeku version:
]java -version
]cat /etc/*release
]docker version
]The text was updated successfully, but these errors were encountered: