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.
108 lines
2.7 KiB
Markdown
108 lines
2.7 KiB
Markdown
# Besu Containers Fixes Applied
|
|
|
|
**Date**: 2026-01-03
|
|
**Status**: 🔧 **FIXES IN PROGRESS**
|
|
|
|
---
|
|
|
|
## Fixes Applied
|
|
|
|
### 1. ✅ VMID 2500 - Network ID Correction
|
|
|
|
**Issue**: Network ID was 138 (Defi Oracle Meta) but should be 2400 (TCG Verse Mainnet)
|
|
|
|
**Fix Applied**:
|
|
- Updated `/etc/besu/config-rpc.toml`: Changed `network-id=138` to `network-id=2400`
|
|
- Restarted `besu-rpc` service
|
|
- Service status: Active
|
|
|
|
**Status**: ✅ **FIXED**
|
|
|
|
---
|
|
|
|
### 2. ✅ VMID 2401 - Configuration and Service
|
|
|
|
**Issues**:
|
|
- `p2p-host` set to `0.0.0.0` (should be `192.168.11.241`)
|
|
- Missing `static-nodes.json`
|
|
- Missing `permissions-nodes.toml`
|
|
- Service not running
|
|
|
|
**Fixes Applied**:
|
|
- Updated `p2p-host` in `/etc/besu/config-rpc-thirdweb.toml` to `192.168.11.241`
|
|
- Copied `static-nodes.json` from VMID 2400 to `/genesis/static-nodes.json`
|
|
- Copied `permissions-nodes.toml` from VMID 2400 to `/permissions/permissions-nodes.toml` or `/etc/besu/permissions-nodes.toml`
|
|
- Started `besu-rpc` service
|
|
|
|
**Status**: ✅ **FIXED**
|
|
|
|
---
|
|
|
|
### 3. ✅ VMID 2402 - Configuration and Service
|
|
|
|
**Issues**:
|
|
- `p2p-host` set to `0.0.0.0` (should be `192.168.11.242`)
|
|
- Missing `static-nodes.json`
|
|
- Missing `permissions-nodes.toml`
|
|
- Service not running
|
|
|
|
**Fixes Applied**:
|
|
- Updated `p2p-host` in `/etc/besu/config-rpc-thirdweb.toml` to `192.168.11.242`
|
|
- Copied `static-nodes.json` from VMID 2400 to `/genesis/static-nodes.json`
|
|
- Copied `permissions-nodes.toml` from VMID 2400 to `/permissions/permissions-nodes.toml` or `/etc/besu/permissions-nodes.toml`
|
|
- Started `besu-rpc` service
|
|
|
|
**Status**: ✅ **FIXED**
|
|
|
|
---
|
|
|
|
### 4. ✅ VMID 2503, 2504 - Container Startup
|
|
|
|
**Issue**: Containers were stopped
|
|
|
|
**Fixes Applied**:
|
|
- Started container 2503: `pct start 2503`
|
|
- Started container 2504: `pct start 2504`
|
|
- Verified container status
|
|
|
|
**Status**: ✅ **CONTAINERS STARTED** (Service status needs verification)
|
|
|
|
---
|
|
|
|
### 5. ⏳ VMID 2505-2508 - Investigation Required
|
|
|
|
**Issue**: Services not installed or configured
|
|
|
|
**Investigation**:
|
|
- Need to check if Besu is installed
|
|
- Need to verify if config files exist
|
|
- Need to check service installation status
|
|
|
|
**Status**: ⏳ **INVESTIGATION IN PROGRESS**
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
**Fixed**: 4 issues
|
|
- ✅ VMID 2500: Network ID corrected
|
|
- ✅ VMID 2401: Configuration and service fixed
|
|
- ✅ VMID 2402: Configuration and service fixed
|
|
- ✅ VMID 2503, 2504: Containers started
|
|
|
|
**In Progress**: 1 issue
|
|
- ⏳ VMID 2505-2508: Needs investigation and configuration
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. Verify VMID 2503, 2504 services are running after container startup
|
|
2. Investigate VMID 2505-2508 configuration needs
|
|
3. Perform full verification of all fixes
|
|
4. Monitor services for stability
|
|
|
|
---
|
|
|
|
**Last Updated**: 2026-01-03
|