Skip to main content
Version: Testnet

Full node

Node Not Synced​

  • Error Displayed:
    The height displayed using rollappd q block | jq .block.header.height does not match the sequencer and is not increasing.

  • Solution:
    Check P2P connectivity by following the guide here.

Not Connected to DA Light Client​

  • Error Displayed:

    time="Sep 19 08:45:15.953" level=error msg="Failed to sync Celestia DA[attempt 1 error RPC client error: sendRequest failed: Post \"http://localhost:26658\": dial tcp 127.0.0.1:26658: connect: connection refused]" module=celestia

  • Solution:
    The DA light client is unavailable at the specified URL http://localhost:26658. Ensure the Celestia light client is up and running. If it isn’t, start it with the following command:

    roller da-light-client start

DA Unauthorized​

  • Error Displayed:

    level=error msg="Failed to sync Celestia DA[attempt 2 error RPC client error: sendRequest failed: request failed, http status 401 Unauthorized]" module=celestia

  • Solution:
    The RollApp configuration requires an authorization token from the DA light client. If changes are made, update the auth_token in the da_config section of the dymint.toml configuration file. You can obtain the authorization token with this command:

    celestia light auth admin --node.store <da-light-client-store-path> --gateway --p2p.network <celestia-network>

Blob Not Found in DA​

  • Error Displayed:

    time="Sep 19 10:43:22.823" level=error msg="RetrieveBatches process failed.[error All attempts fail:\n#1: retrieval failed\n#2: retrieval failed\n#3: retrieval failed\n#4: retrieval failed]" module=celestia

  • Solution:
    Failure to retrieve blobs from DA is often due to network issues in Celestia. First, try restarting the Celestia light client. If the issue persists, it may be related to the performance of the Celestia full-node connected to the light client. If using a public node, consider switching to a different one. A list of public nodes is available in the Celestia documentation.

Transactions Rejected​

  • Error Displayed:

     time="2024-11-06T16:18:47Z" level=info msg="rejected bad transaction[priority 0 tx 11227670C6989F29427C0F472DD1BEA01B1D6DC7CD819A039444FEAF0E720D9D peer_id map[1:true] code 32 post_check_err <nil>]"

  • Solution:
    If transactions are rejected without a clear reason, it may be because the node is not synced, causing incoming transactions to be seen as invalid. Check P2P connectivity to ensure full nodes are synced with the sequencer, as explained here.

Mempool is Full​

  • Error Displayed:
    TBC

  • Solution:
    If nodes are not connected to P2P and are not receiving blocks produced by the sequencer, transactions accepted and included in blocks may not be cleared from the mempool, causing it to fill up. Check P2P connectivity to ensure full nodes are synced with the sequencer, as explained here, which will allow the mempool to clear accepted transactions.