fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
5.1 KiB
5.1 KiB
Troubleshooting Quick Reference
Last Updated: 2025-01-20
Document Version: 1.0
Status: Active Documentation
Quick Reference: Common Issues and Solutions
Container Issues
| Issue | Quick Check | Quick Fix |
|---|---|---|
| Container won't start | pct status <vmid> |
pct start <vmid> |
| Container out of disk | pct exec <vmid> df -h |
pct set <vmid> -rootfs <size> |
| Container out of memory | pct list --full |
pct set <vmid> -memory <mb> |
| Container network issue | pct exec <vmid> ping 8.8.8.8 |
Check network config |
| Container service down | pct exec <vmid> systemctl status <service> |
pct exec <vmid> systemctl restart <service> |
Network Issues
| Issue | Quick Check | Quick Fix |
|---|---|---|
| Can't reach container | ping <container-ip> |
Check firewall rules |
| DNS not working | pct exec <vmid> nslookup google.com |
Check DNS config |
| Port not accessible | nc -zv <ip> <port> |
Check port forwarding |
| VLAN not working | ip addr show |
Check VLAN config |
| Cloudflare tunnel down | pct status 102 |
Restart cloudflared container |
Service Issues
| Issue | Quick Check | Quick Fix |
|---|---|---|
| Besu node not syncing | pct exec <vmid> curl http://localhost:8545 |
Check logs, restart |
| RPC endpoint down | curl https://rpc-http-pub.d-bis.org |
Check Nginx, restart RPC |
| Blockscout not loading | curl http://192.168.11.140:80 |
Check Blockscout status |
| Cloudflare tunnel error | pct logs 102 |
Check tunnel config |
Performance Issues
| Issue | Quick Check | Quick Fix |
|---|---|---|
| High CPU usage | pct list --full |
Check processes, limit CPU |
| High memory usage | pct list --full |
Increase memory or optimize |
| Disk I/O high | iostat -x 1 |
Check disk usage, optimize |
| Network latency | ping <target> |
Check network, optimize routing |
Quick Diagnostic Commands
Container Health Check
# Check container status
pct status <vmid>
# Check container resources
pct list --full | grep <vmid>
# Check container logs
pct logs <vmid> --tail 50
# Check container network
pct exec <vmid> ip addr show
Network Health Check
# Test connectivity
ping -c 4 192.168.11.1
# Check DNS
nslookup google.com
# Check routes
ip route show
# Test port
nc -zv <ip> <port>
Service Health Check
# Check Besu RPC
curl -X POST http://localhost:8545 -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
# Check Blockscout
curl http://192.168.11.140:80
# Check Cloudflare tunnel
pct status 102
Common Error Messages
| Error Message | Likely Cause | Solution |
|---|---|---|
| "No space left on device" | Disk full | Free up space or expand disk |
| "Connection refused" | Service not running | Start service or check firewall |
| "Network unreachable" | Network config issue | Check network configuration |
| "Permission denied" | Permission issue | Check file permissions |
| "Container not found" | Wrong VMID | Verify VMID with pct list |
Emergency Procedures
Container Won't Start
- Check status:
pct status <vmid> - Check logs:
pct logs <vmid> - Check config:
pct config <vmid> - Try manual start:
pct start <vmid> - If still failing, check resources:
pct list --full
Network Completely Down
- Check router:
ping 192.168.11.1 - Check switch: Physical connection
- Check Proxmox network:
ip addr show - Check firewall:
iptables -L - Restart network:
systemctl restart networking
Service Critical Failure
- Check service status:
systemctl status <service> - Check logs:
journalctl -u <service> -n 50 - Restart service:
systemctl restart <service> - If persistent, check configuration
- Escalate to detailed troubleshooting guide
Quick Fixes by Service
Besu Node
# Restart Besu container
pct restart <vmid>
# Check Besu logs
pct logs <vmid> | grep -i error
# Check Besu RPC
curl -X POST http://localhost:8545 -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
RPC Endpoint
# Check RPC container
pct status 2500
# Check Nginx
pct exec 105 nginx -t
# Restart Nginx
pct exec 105 systemctl restart nginx
# Test RPC endpoint
curl https://rpc-http-pub.d-bis.org
Cloudflare Tunnel
# Check tunnel status
pct status 102
# Check tunnel logs
pct logs 102 | tail -50
# Restart tunnel
pct restart 102
# Verify tunnel health
# Check Cloudflare dashboard
Related Documentation
- ../09-troubleshooting/TROUBLESHOOTING_FAQ.md ⭐⭐⭐ - Complete troubleshooting FAQ
- ../09-troubleshooting/TROUBLESHOOTING_FAQ.md ⭐⭐ - Troubleshooting FAQ and flow
- ../03-deployment/OPERATIONAL_RUNBOOKS.md ⭐⭐ - Operational runbooks
Last Updated: 2025-01-20
Review Cycle: Quarterly