Skip to main content

Troubleshooting

Node warning logs​

Node error logs​

error: "failed to insert new head to L2 execution engine: missing trie node"

Make sure that your RPC is pointing to an Sepolia archive node, and not a full node.

error: L1_BLOCK_ID

The block that you want to prove has already been verified, you can ignore this.

Fatal: Failed to register the Ethereum service: database contains incompatible genesis

Try to remove the node with docker compose down -v and then try again.

Block batch iterator callback error; error="failed to fetch L2 parent block: not found

You can ignore this error.

error parsing HTTP 403 response body: invalid character '<' looking for beginning of value

Your IP address is being geo-blocked due to sanctions lists. If you're affected, try changing hosting locations or utilize a VPN to change your IP address.

daemon docker is not running
Cannot connect to the Docker daemon

Need to start the Docker before running the commands.

Bind for 0.0.0.0:port failed: port already allocated

This error just means that the port taiko-node is trying to allocate is already being used by either some other node you're running or by a left-over container of taiko node if you did not close down the node correctly, you can try running docker compose down in the simple-taiko-node folder and start it again using docker compose up -d or edit the .env and replace the problematic port with a different one.

no configuration file provided: not found

You are in the wrong directory, cd simple-taiko-node and run the command again.

docker: 'compose' is not a docker command

You are missing the docker compose plugin Installation Guide

simple-taiko-node-taiko_client_prover_relayer-1 | /bin/sh: /script/start-prover-relayer.sh: not found

This issue occurs on windows because of the Control Characters in this case the Line Endings, a quick fix would be to delete the node folder, run this git config --global core.autocrlf false in the shell, then clone the repo again.

If you do not want to delete the node folder, please follow one of these steps below.

no contract code at given address

When running a L3 node, users may run into this issue if their underlying L2 is still syncing. Please wait until your L2 is fully synced before starting your L3 node.

docker compose down -v
cd scripts
dos2unix start-zkevm-chain-rpcd.sh
dos2unix start-prover-relayer.sh
cd ..
docker compose up