Troubleshooting Guide
This guide helps you diagnose and resolve common issues with ChainLaunch Pro.
Common Issues
Node Won't Start
Symptoms:
- Node status remains "Stopped" after clicking start
- Error message in logs
Diagnosis:
-
Check node logs: Go to the nodes list, and enter the node that is failing. Then at the bottom check the logs.
-
Check system resources:
- Verify CPU and memory available
- Check disk space:
df -h
-
Check port availability:
# Linux/macOS
lsof -i :30303 # P2P port
lsof -i :8545 # JSON-RPC port
Solutions:
| Error Message | Solution |
|---|---|
Port already in use | Change node port in configuration or kill process using port |
Insufficient disk space | Free up disk space or mount larger volume |
Permission denied | Check file permissions on node data directory |
Connection refused | Check firewall rules and network connectivity |
Out of memory | Increase memory allocation or reduce node count |
Nodes Not Discovering Each Other
Symptoms:
- Block height not increasing
- Peer count = 0
- Consensus not starting (Fabric/Besu)
Diagnosis:
-
Check peer count:
# For Besu via RPC
curl -X POST http://localhost:8545 \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "net_peerCount",
"params": [],
"id": 1
}' -
Check network connectivity between nodes:
# Test if node A can reach node B
ping node-b-ip
telnet node-b-ip 30303 -
Check enode URLs (Besu):
# Get node's enode
curl -X POST http://localhost:8545 \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "admin_nodeInfo",
"params": [],
"id": 1
}'
Solutions:
| Issue | Solution |
|---|---|
| Firewall blocking ports | Open P2P port (30303) and RPC port (8545) in firewall |
| Nodes on different networks | Verify genesis block hash matches across nodes |
| Bootnode not running | Start bootnode and configure its address in other nodes |
| DNS not resolving | Use IP addresses instead of hostnames |
| Network policy restricting traffic | Review Kubernetes network policies or security groups |