Logging & Troubleshooting

Monitoring logs and diagnosing issues is essential to ensure that a Celestium node operates smoothly. Logs provide valuable insight into block synchronization, consensus processes, transaction execution, and potential errors.

---

Accessing Node Logs

When running a Celestium node, logs are printed to the console by default. You can also redirect logs to a file for easier review:

./celestium-node --rpc http://rpc-private-testnet.celestium.network --chain-id 252525 > node.log 2>&1 &

• Real-time log view:

  tail -f node.log

• View last 100 lines:

  btail -n 100 node.log

• Search for errors in logs:

  grep "ERROR" node.log

---

Common Log Messages

Log Level	Description
INFO	Standard operational messages, including block finalization.
WARN	Non-critical issues, such as slow sync or network latency.
ERROR	Critical errors that could affect node functionality.
DEBUG	Detailed information (useful for development and debugging).

---

Common Node Issues and Solutions

Issue	Cause	Solution
Node is not syncing	Network issues or wrong RPC URL	Verify network connectivity and RPC URL configuration.
High CPU or Memory Usage	Block processing or large transaction load	Ensure system meets hardware requirements; monitor with metrics.
Failed transaction execution	Gas limit too low, or contract error	Check transaction gas limit and contract logic.
Peer connection issues	Network configuration or firewall	Ensure ports are open and node can reach peers.
Storage read/write errors	Disk performance issues	Ensure NVMe SSD is functioning properly and has sufficient space.

---

Increasing Log Verbosity

For more detailed logs, use the --log-level flag:

./celestium-node --rpc http://rpc-private-testnet.celestium.network --chain-id 252525 --log-level debug

Available levels:

• error

• warn

• info (default)

• debug

---

Resetting Node Data

If the node experiences persistent issues, resetting the local blockchain data can resolve corruption or sync failures:

rm -rf celestium-data/
./celestium-node --rpc http://rpc-private-testnet.celestium.network --chain-id 252525 --data-dir celestium-data

---

Reporting Issues

If problems persist, consider:

• Collecting relevant logs (node.log).

• Noting system details (CPU, RAM, Disk usage).

• Gathering block height and chain ID.

Submit issues to the official Celestium support channels or community forums.

---

Effective logging and troubleshooting ensure your node remains healthy, minimizing downtime and enhancing network participation.