8000 HotColdDBError(UnsupportedSchemaVersion { target_version: SchemaVersion(18), current_version: SchemaVersion(17) }) · Issue #7556 · sigp/lighthouse · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

HotColdDBError(UnsupportedSchemaVersion { target_version: SchemaVersion(18), current_version: SchemaVersion(17) }) #7556

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.

Sign up for GitHub

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

Jump to bottom
Open
Piggy0v0 opened this issue Jun 4, 2025 · 15 comments
Open

HotColdDBError(UnsupportedSchemaVersion { target_version: SchemaVersion(18), current_version: SchemaVersion(17) }) #7556

Piggy0v0 opened this issue Jun 4, 2025 · 15 comments
Labels
question User question (not actionable)

Comments

@Piggy0v0
Copy link
Piggy0v0 commented Jun 4, 2025

lighthouse bn --network mainnet --execution-endpoint http://127.0.0.1:8551 --execution-jwt /secrets/jwt.hex --checkpoint-sync-url https://mainnet.checkpoint.sigp.io --disable-deposit-contract-sync --http
Jun 04 05:26:30.826 INFO Logging to file path: "/root/.lighthouse/mainnet/beacon/logs/beacon.log"
Jun 04 05:26:30.828 INFO Lighthouse started version: Lighthouse/v7.0.1-e42406d
Jun 04 05:26:30.829 INFO Configured for network name: mainnet
Jun 04 05:26:30.841 INFO Data directory initialised datadir: /root/.lighthouse/mainnet
Jun 04 05:26:30.851 INFO Deposit contract address: 0x00000000219ab540356cbb839cbe05303d7705fa, deploy_block: 11184524
Jun 04 05:26:30.945 INFO Blob DB initialized oldest_data_column_slot: None, oldest_blob_slot: Some(Slot(8626176)), path: "/root/.lighthouse/mainnet/beacon/blobs_db", service: freezer_db
Jun 04 05:26:30.947 CRIT Failed to start beacon node reason: Unable to open database: HotColdDBError(UnsupportedSchemaVersion { target_version: SchemaVersion(18), current_version: SchemaVersion(17) })
Jun 04 05:26:30.948 INFO Internal shutdown received reason: Failed to start beacon node
Jun 04 05:26:30.949 INFO Shutting down.. reason: Failure("Failed to start beacon node")
@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

I don't what can i do

@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

where is the db？ How can i update the db？

@michaelsproul
Copy link
Member

Delete your database (at /root/.lighthouse/mainnet/beacon) or add the flag --purge-db (or --purge-db-force)

@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

Jun 04 05:31:08.426 INFO Logging to file path: "/root/.lighthouse/mainnet/beacon/logs/beacon.log"
Jun 04 05:31:08.428 INFO Lighthouse started version: Lighthouse/v7.0.1-e42406d
Jun 04 05:31:08.430 INFO Configured for network name: mainnet
Jun 04 05:31:08.443 INFO You are about to delete the chain database. This is irreversable and you will need to resync the chain.
Jun 04 05:31:08.443 INFO Type 'confirm' to delete the database. Any other input will leave the database intact and Lighthouse will exit.

@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

is right？

@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

Jun 04 05:33:30.974 INFO Logging to file path: "/root/.lighthouse/mainnet/beacon/logs/beacon.log"
Jun 04 05:33:30.980 INFO Lighthouse started version: Lighthouse/v7.0.1-e42406d
Jun 04 05:33:30.983 INFO Configured for network name: mainnet
Jun 04 05:33:30.997 INFO Data directory initialised datadir: /root/.lighthouse/mainnet
Jun 04 05:33:31.005 INFO Deposit contract address: 0x00000000219ab540356cbb839cbe05303d7705fa, deploy_block: 11184524
Jun 04 05:33:31.114 INFO Blob DB initialized oldest_data_column_slot: None, oldest_blob_slot: Some(Slot(8626176)), path: "/root/.lighthouse/mainnet/beacon/blobs_db", service: freezer_db
Jun 04 05:33:36.963 INFO Starting checkpoint sync remote_url: https://mainnet.checkpoint.sigp.io/, service: beacon
this is right

@michaelsproul
Copy link
Member

Yep, that looks better.

You had a really old database which isn't supported by the current version of LH, so your node is now syncing from scratch using checkpoint sync.

@michaelsproul michaelsproul added the question User question (not actionable) label Jun 4, 2025
@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

how many data it will be download

@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

I'm afraid there's not enough disk space

@michaelsproul
Copy link
Member

A full Lighthouse database is around 200-300GB, and you also need an execution node database which is around 1-1.5TB depending on the client.

@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

Is there a way to not be completely synchronized?
like from block 123455 to the block 234567

@michaelsproul
Copy link
Member

@Piggy0v0 On the Lighthouse side, yes, you can sync from any checkpoint: https://lighthouse-book.sigmaprime.io/advanced_checkpoint_sync.html#manual-checkpoint-sync

I'm not sure about the EL. Most ELs sync by downloading the current state as a snapshot, so building an old snapshot of the state is probably a lot slower.

What are you trying to accomplish?

@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

@michaelsproul I just want to test the lighthouse and geth,Then check whether the obtained block data is complete.

@Piggy0v0
Copy link
Author
Piggy0v0 commented Jun 4, 2025

But the total amount of block data is too much

@chong-he
Copy link
Member
chong-he commented Jun 4, 2025

But the total amount of block data is too much

generally you will need ~6 months of data for the consensus layer (auto download once you checkpoint sync) and all blocks for the execution later. However now that some EL clients have started to implement pre-merge history state expiry, the usage has gone down quite a bit, see: https://ethdocker.com/Usage/ResourceUsage/

You can check for the EL client you want to use to see how to apply the state expiry to use less space

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question User question (not actionable)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@michaelsproul @chong-he @Piggy0v0
0