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

[ERROR] Tutorials:Creating Your Own L2 Rollup Testnet issue #849 #1029

Open
AgiletechDev opened this issue Oct 26, 2024 · 0 comments
Open

Comments

@AgiletechDev
Copy link

Description:

When running op-geth, I encountered the following error:

geth/datadir/geth/chaindata/ancient/chain readonly=false
Fatal: Failed to register the Ethereum service: incompatible state scheme, stored: path, provided: hash
This error was resolved by performing the following steps:

Remove the existing datadir:
rm -rf datadir
Recreate the datadir:
mkdir datadir
Reinitialize with the following command:
build/bin/geth init --datadir=datadir --state.scheme=hash genesis.json
During the execution of the build/bin/geth init --datadir=datadir --state.scheme=hash genesis.json command, I encountered another error:

ERROR[08-23|17:11:15.047] Head block is not reachable
INFO [08-23|17:11:15.362] Persisted trie from memory database nodes=3137 size=453.32KiB time=17.070932ms gcnodes=0 gcsize=0.00B gctime=0s livenodes=0 livesize=0.00B
INFO [08-23|17:11:15.535] Successfully wrote genesis state database=chaindata hash=fb7ed5..9b1a0f
INFO [08-23|17:11:15.535] Defaulting to pebble as the backing database
INFO [08-23|17:11:15.535] Allocated cache and file handles database=/root/op-geth/datadir/geth/lightchaindata cache=16.00MiB handles=16
INFO [08-23|17:11:15.572] Opened ancient database database=/root/op-geth/datadir/geth/lightchaindata/ancient/chain readonly=false
INFO [08-23|17:11:15.572] State scheme set by user scheme=hash
INFO [08-23|17:11:15.572] Writing custom genesis block
ERROR[08-23|17:11:15.588] Head block is not reachable
I chose to ignore this error for now, as it didn’t seem to affect subsequent operations. However, I believe this issue should be investigated to determine its cause and to ensure that it does not lead to further problems down the line.

Steps to Reproduce:

Run op-geth with the specified configurations.
Execute the above steps to resolve the initial error.
Observe the output for the "Head block is not reachable" error during geth init.
Expected Behavior:

The geth init command should complete without any errors, ensuring that the system is correctly initialized.

Actual Behavior:

An error stating "Head block is not reachable" is thrown during the initialization process.

Environment:

op-geth version: commit 641e996a2dcf1f81bac9416cb6124f86a69f1de7
Operating System: ubuntu 22.04
Additional Context:

I suggest investigating the root cause of the "Head block is not reachable" error and determining whether it might affect future operations. After that, modify the geth init command of the document. And is not the first time that happen this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant