cb47cce074
- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
99 lines
2.6 KiB
Markdown
99 lines
2.6 KiB
Markdown
# Besu Containers Fixes - Progress Report
|
|
|
|
**Date**: 2026-01-03
|
|
**Status**: 🔧 **FIXES IN PROGRESS**
|
|
|
|
---
|
|
|
|
## Fixes Applied
|
|
|
|
### 1. ✅ VMID 2500 - Network ID Correction
|
|
|
|
**Issue**: Network ID was 138 but should be 2400 for TCG Verse Mainnet
|
|
|
|
**Fix**:
|
|
- Updated `/etc/besu/config-rpc.toml`: `network-id=138` → `network-id=2400`
|
|
- Restarted service
|
|
- Status: ✅ **ACTIVE**
|
|
|
|
**Note**: Service restarted successfully but shows "Unable to find sync target" - may need to connect to peers on network 2400.
|
|
|
|
---
|
|
|
|
### 2. ✅ VMID 2401 - Configuration and Service
|
|
|
|
**Issues Fixed**:
|
|
- ✅ `p2p-host` updated: `0.0.0.0` → `192.168.11.241`
|
|
- ✅ Removed unsupported config options: `rpc-ws-origins`, `rpc-http-host-allowlist`, `rpc-http-timeout`
|
|
- ✅ Copied `static-nodes.json` from VMID 2400
|
|
- ✅ Copied `permissions-nodes.toml` from VMID 2400
|
|
- ✅ Service restarted
|
|
|
|
**Status**: ✅ **ACTIVE** (after config fix)
|
|
|
|
---
|
|
|
|
### 3. ✅ VMID 2402 - Configuration and Service
|
|
|
|
**Issues Fixed**:
|
|
- ✅ `p2p-host` updated: `0.0.0.0` → `192.168.11.242`
|
|
- ✅ Removed unsupported config options: `rpc-ws-origins`, `rpc-http-host-allowlist`, `rpc-http-timeout`
|
|
- ✅ Created `/genesis` and `/permissions` directories
|
|
- ✅ Copied `static-nodes.json` from VMID 2400
|
|
- ✅ Copied `permissions-nodes.toml` from VMID 2400
|
|
- ✅ Service restarted
|
|
|
|
**Status**: ✅ **ACTIVE** (after config fix)
|
|
|
|
---
|
|
|
|
### 4. ⚠️ VMID 2503, 2504 - Containers Started
|
|
|
|
**Status**:
|
|
- ✅ Containers started successfully
|
|
- ❌ Besu service not installed/configured
|
|
- ❌ No configuration files found
|
|
|
|
**Action Required**: These containers need Besu installation and configuration.
|
|
|
|
---
|
|
|
|
### 5. ❌ VMID 2505-2508 - Not Configured
|
|
|
|
**Status**:
|
|
- ❌ Besu not installed
|
|
- ❌ No configuration files
|
|
- ❌ No services configured
|
|
|
|
**Action Required**: These containers need full Besu installation and configuration.
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
**Fixed and Operational**: 4 nodes
|
|
- ✅ VMID 2500: Network ID corrected, service active
|
|
- ✅ VMID 2401: Config fixed, service active
|
|
- ✅ VMID 2402: Config fixed, service active
|
|
- ✅ VMID 2400: Already operational
|
|
|
|
**Containers Started but Not Configured**: 2 nodes
|
|
- ⚠️ VMID 2503, 2504: Running but need Besu setup
|
|
|
|
**Not Configured**: 4 nodes
|
|
- ❌ VMID 2505-2508: Need full installation
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. ✅ **COMPLETE**: Fixed VMID 2401, 2402 configuration issues
|
|
2. ⏳ **PENDING**: Install and configure Besu on VMID 2503, 2504
|
|
3. ⏳ **PENDING**: Install and configure Besu on VMID 2505-2508
|
|
4. ⏳ **VERIFY**: Check peer connectivity for all nodes
|
|
5. ⏳ **MONITOR**: Verify VMID 2500 connects to correct network (2400)
|
|
|
|
---
|
|
|
|
**Last Updated**: 2026-01-03
|