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

About poa Private chain v1.10 #30883

Closed
ljb943 opened this issue Dec 9, 2024 · 4 comments
Closed

About poa Private chain v1.10 #30883

ljb943 opened this issue Dec 9, 2024 · 4 comments
Labels

Comments

@ljb943
Copy link

ljb943 commented Dec 9, 2024

Help My private chain stop and start again as shown below

INFO [12-09|22:21:43.725] Initialising Ethereum protocol network=1 dbversion=8
INFO [12-09|22:21:43.725] Loaded most recent local header number=1,840,288 hash=0004e5..f39c9d td=3,682,353 age=10h29m58s
INFO [12-09|22:21:43.725] Loaded most recent local full block number=1,840,288 hash=0004e5..f39c9d td=3,682,353 age=10h29m58s
INFO [12-09|22:21:43.725] Loaded most recent local fast block number=1,840,288 hash=0004e5..f39c9d td=3,682,353 age=10h29m58s
INFO [12-09|22:21:43.726] Loaded last fast-sync pivot marker number=1,236,268
WARN [12-09|22:21:43.726] Head state missing, repairing number=1,840,288 hash=0004e5..f39c9d snaproot=d8bbfd..0d1ac4

@ljb943 ljb943 added the type:bug label Dec 9, 2024
@ljb943
Copy link
Author

ljb943 commented Dec 9, 2024

I don't know why he wants to roll back to 1236268, which will cause me to lose a lot of data

@rjl493456442
Copy link
Member

Do you have any unclean shutdown? Geth will lose the in-memory states if unclean shutdown occurs, an additional state recovery procedure will be scheduled if so in the next startup.

@ljb943
Copy link
Author

ljb943 commented Dec 10, 2024

Do you have any unclean shutdown? Geth will lose the in-memory states if unclean shutdown occurs, an additional state recovery procedure will be scheduled if so in the next startup.

Yes, my server suddenly stopped, and when I found it and started up again, the above problem occurred. Is there any way to solve it?

@MariusVanDerWijden
Copy link
Member

Not really, it rolls back the chain and goes from there. If there is another node in the network, it will sync back up again.
Not much we can do about it, sorry!

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