-
Notifications
You must be signed in to change notification settings - Fork 475
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
pruning: head doesn't match snapshot #2441
Comments
I hava a same qusetion |
same issue here. |
This may be related to a previous stop. When I stopped the node via |
As noted above, this is most likely due to a corrupted database caused by an ungraceful shutdown. |
@joshuacolvin0 you mentioned that it's important to do graceful shutdown ( see also #2421 ) can you elaborate on how to do this? it's nice that you focus on docker, but we "native folks" are somewhat overlooked ( see my other issues ) is this okay, or is there a better way?
|
I also encountered a similar problem. At first I thought it was a problem with the snapshot file, but later I found that I just needed to remove the --init.prune="full" parameter. |
Hi. I dont't understand how pruning works. When i start with
--init.prune full
i see the following
what can i do?
Bonus question: my second node, a full archival node is 30 TB big. Other operators say that would be too much. what is correct?
The text was updated successfully, but these errors were encountered: