Skip to main content

Troubleshooting

This guide provides solutions to common issues when running RibbleChain nodes, sequencers, or staking setups.

Node Issues​

Node Not Syncing​

  • Symptoms: ribblechain-cli node sync shows no progress.
  • Solution:
    • Check internet connectivity and peer count: ribblechain-cli node peers.
    • Increase max peers: ribblechain-cli node config --max-peers 50.
    • Restart node: docker restart ribblechain-node.

High CPU/Memory Usage​

  • Symptoms: Node consumes excessive resources.
  • Solution:

Sequencer Issues​

Sequencer Not Processing Batches​

  • Symptoms: ribblechain-cli sequencer status shows no activity.
  • Solution:
    • Check logs: docker logs ribblechain-sequencer.
    • Verify configuration: cat ~/.ribblechain/sequencer.config.json.
    • Restart sequencer: docker restart ribblechain-sequencer.

High Batch Latency​

  • Symptoms: Batches take too long to process.
  • Solution:
    • Reduce batch size: ribblechain-cli sequencer config --max-batch-size 500.
    • Optimize network bandwidth.
    • Check Sequencer Monitoring.

Staking Issues​

Rewards Not Received​

  • Symptoms: ribblechain-cli stake rewards shows zero rewards.
  • Solution:
    • Verify validator uptime: ribblechain-cli stake performance.
    • Ensure minimum stake (32,000 $XRB for validators).
    • Wait for the next epoch (e.g., daily).

Slashing Events​

  • Symptoms: Staked amount decreases unexpectedly.
  • Solution:
    • Check logs for downtime or malicious behavior.
    • Improve node uptime with Node Security.
    • Contact Support for disputes.

General Tips​

  • Logs: Always check logs for detailed error messages.
  • CLI: Use --verbose for more output: ribblechain-cli --verbose node status.
  • Community: Ask for help on Community Channels.
  • Updates: Ensure the latest CLI and node versions: npm update -g ribblechain-cli.

Next Steps​