d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
cb47cce074da46f3ce5910b752d435c4a3ee87d0
proxmox/reports/status/BESU_FIXES_COMPLETE.md
defiQUG cb47cce074 Complete markdown files cleanup and organization 
- 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.
2026-01-06 01:46:25 -08:00

4.0 KiB
Raw Blame History

Besu Containers Fixes - Complete

Date: 2026-01-03
Status: ✅ FIXES COMPLETE (Critical Issues Resolved)

Fixes Applied and Completed

1. ✅ VMID 2500 - Network ID Correction

Issue: Network ID was 138 (Defi Oracle Meta) but should be 2400 (TCG Verse Mainnet)

Fixes Applied:

  • Updated /etc/besu/config-rpc.toml: Changed network-id=138 to network-id=2400
  • Restarted besu-rpc service
  • Service restarted successfully

Status: ✅ FIXED - Service ACTIVE

2. ✅ VMID 2401 - Configuration and Service Fix

Issues Found:

  • p2p-host set to 0.0.0.0 (should be 192.168.11.241)
  • Unsupported config options causing service failures
  • Missing configuration files

Fixes Applied:

  1. Updated p2p-host in /etc/besu/config-rpc-thirdweb.toml to 192.168.11.241
  2. Removed unsupported options:
    • rpc-ws-origins
    • rpc-http-host-allowlist
    • rpc-http-timeout
    • rpc-tx-feecap
  3. Copied static-nodes.json from VMID 2400 to /genesis/static-nodes.json
  4. Copied permissions-nodes.toml from VMID 2400
  5. Restarted service

Status: ✅ FIXED - Service ACTIVE

3. ✅ VMID 2402 - Configuration and Service Fix

Issues Found:

  • p2p-host set to 0.0.0.0 (should be 192.168.11.242)
  • Unsupported config options causing service failures
  • Missing configuration files

Fixes Applied:

  1. Updated p2p-host in /etc/besu/config-rpc-thirdweb.toml to 192.168.11.242
  2. Removed unsupported options:
    • rpc-ws-origins
    • rpc-http-host-allowlist
    • rpc-http-timeout
    • rpc-tx-feecap
  3. Created /genesis and /permissions directories
  4. Copied static-nodes.json from VMID 2400 to /genesis/static-nodes.json
  5. Copied permissions-nodes.toml from VMID 2400
  6. Restarted service

Status: ✅ FIXED - Service ACTIVE

4. ✅ VMID 2503, 2504 - Containers Started

Issue: Containers were stopped

Fixes Applied:

  • Started container 2503: pct start 2503
  • Started container 2504: pct start 2504

Status: ✅ CONTAINERS RUNNING

Note: These containers need Besu installation and configuration (not part of critical fixes).

Summary

Critical Issues Fixed: 3/3 ✅

  1. ✅ VMID 2500: Network ID corrected (138 → 2400)
  2. ✅ VMID 2401: Configuration fixed, service operational
  3. ✅ VMID 2402: Configuration fixed, service operational

Containers Started: 2/2 ✅

  1. ✅ VMID 2503: Container running
  2. ✅ VMID 2504: Container running

Operational Status

Fully Operational: 6 nodes

  • ✅ VMID 1000-1004: Validators (5 nodes) - All operational
  • ✅ VMID 2400: RPC Node (Chain 138) - Operational
  • ✅ VMID 2401: RPC Node (Chain 138) - NOW OPERATIONAL
  • ✅ VMID 2402: RPC Node (Chain 138) - NOW OPERATIONAL
  • ✅ VMID 2500-2502: RPC Nodes (Chain 2400) - Operational (3 nodes)

Needs Setup (Not Critical): 6 nodes

  • ⏳ VMID 2503, 2504: Containers running, need Besu installation
  • ⏳ VMID 2505-2508: Need full Besu installation and configuration

Configuration Changes Applied

Unsupported Options Removed

  • rpc-ws-origins (not supported in Besu 23.10.0)
  • rpc-http-host-allowlist (not supported in Besu 23.10.0)
  • rpc-http-timeout (not supported in Besu 23.10.0)
  • rpc-tx-feecap (removed in Besu 23.10.0)

Network Configuration

  • VMID 2500: Network ID corrected from 138 to 2400
  • VMID 2401: P2P host corrected to 192.168.11.241
  • VMID 2402: P2P host corrected to 192.168.11.242

Next Steps (Optional)

  1. VMID 2503, 2504: Install and configure Besu
  2. VMID 2505-2508: Full Besu installation and configuration
  3. Monitor: Verify peer connectivity for all nodes
  4. Verify: Check VMID 2500 connects to correct network (2400)

Notes

  • All critical configuration issues have been resolved
  • All services are now operational or starting
  • VMID 2503-2508 setup can be done separately as they are not critical for current operations

Last Updated: 2026-01-03
Status: ✅ ALL CRITICAL FIXES COMPLETE

Reference in New Issue View Git Blame Copy Permalink