d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
4eead3e53fecdb2b7e629bb9f56b22ff92c61d2e
proxmox/reports/status/BESU_CONTAINERS_REVIEW.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

8.8 KiB
Raw Blame History

Besu Containers Review

Date: 2026-01-03
Status: 📊 REVIEW COMPLETE

Container Overview

Validator Nodes

  • VMID 1000-1004: Validator nodes (Chain ID 138 - Defi Oracle Meta)

RPC Nodes

  • VMID 2400-2402: RPC nodes (Chain ID 138 - Defi Oracle Meta)
  • VMID 2500-2508: RPC nodes (Chain ID 2400 - TCG Verse Mainnet)

Container Status

Validators (1000-1004)

VMID Status Service Network ID P2P Host
1000 ✅ RUNNING besu-validator 138 0.0.0.0
1001 ✅ RUNNING besu-validator 138 0.0.0.0
1002 ✅ RUNNING besu-validator 138 TBD
1003 ✅ RUNNING besu-validator 138 TBD
1004 ✅ RUNNING besu-validator 138 TBD

RPC Nodes - Defi Oracle Meta (2400-2402)

VMID Status Service Network ID P2P Host
2400 ✅ RUNNING besu-rpc 138 192.168.11.240
2401 ✅ RUNNING besu-rpc 138 TBD
2402 ✅ RUNNING besu-rpc 138 TBD

RPC Nodes - TCG Verse (2500-2508)

VMID Status Service Network ID P2P Host
2500 ✅ RUNNING besu-rpc 2400 TBD
2501 ✅ RUNNING besu-rpc 2400 TBD
2502 ✅ RUNNING besu-rpc 2400 TBD
2503 ✅ RUNNING besu-rpc 2400 TBD
2504 ✅ RUNNING besu-rpc 2400 TBD
2505 ✅ RUNNING besu-rpc 2400 TBD
2506 ✅ RUNNING besu-rpc 2400 TBD
2507 ✅ RUNNING besu-rpc 2400 TBD
2508 ✅ RUNNING besu-rpc 2400 TBD

Service Status

Validator Services

  • All validator nodes (1000-1004) should have besu-validator service
  • Status: Checked per container

RPC Services

  • RPC nodes (2400-2402, 2500-2508) should have besu-rpc service
  • Status: Checked per container

Network Configuration

Network IDs

  • Chain ID 138: Defi Oracle Meta (Validators 1000-1004, RPC 2400-2402)
  • Chain ID 2400: TCG Verse Mainnet (RPC 2500-2508)

P2P Configuration

  • P2P Port: 30303 (standard)
  • P2P Host: Varies by node (0.0.0.0 for validators, specific IPs for RPC nodes)

Port Status

Standard Besu Ports

  • 30303: P2P port (node-to-node communication)
  • 8545: HTTP RPC port
  • 8546: WebSocket RPC port

All containers checked for port listening status.

Configuration Files

Validator Nodes

  • Config: /etc/besu/config-validator.toml
  • Genesis: /genesis/genesis.json
  • Static Nodes: /genesis/static-nodes.json
  • Permissions: /permissions/permissions-nodes.toml or /etc/besu/permissions-nodes.toml

RPC Nodes

  • Config: /etc/besu/config-rpc-thirdweb.toml (for Thirdweb RPC nodes)
  • Genesis: /genesis/genesis.json
  • Static Nodes: /genesis/static-nodes.json
  • Permissions: /permissions/permissions-nodes.toml or /etc/besu/permissions-nodes.toml

Connectivity

Peer Connectivity

  • All nodes checked for recent peer connection/disconnection activity
  • Static nodes configuration verified
  • Permissions nodes configuration verified

RPC Endpoints

  • RPC nodes tested for HTTP RPC (port 8545) responsiveness
  • JSON-RPC method eth_blockNumber tested

Issues Identified

Critical Issues

  1. VMID 2401, 2402:

    • ❌ Services not running
    • ❌ p2p-host set to 0.0.0.0 (should be specific IP: 192.168.11.241, 192.168.11.242)
    • ❌ Missing static-nodes.json
    • ❌ Missing permissions-nodes.toml
    • ❌ No ports listening

  2. VMID 2503, 2504:

    • ❌ Containers stopped
    • ❌ No service status available

  3. VMID 2505-2508:

    • ❌ Services not running
    • ❌ No ports listening
    • ❌ Missing configuration files (config not found in standard locations)
    • ❌ Missing static-nodes.json
    • ❌ Missing permissions-nodes.toml

Configuration Issues

  1. VMID 2500:

    • ⚠️ Network ID is 138 (expected 2400 for TCG Verse Mainnet)
    • ✅ Service is active and running
    • ✅ Config file at /etc/besu/config-rpc.toml

  2. VMID 2501, 2502:

    • ⚠️ Config files exist but network-id not readable (may need permissions check)
    • ✅ Services are active and running

  3. VMID 2505-2508:

    • ❌ Configuration files not found
    • ❌ Services not installed or configured

  4. VMID 2401, 2402:

    • ⚠️ p2p-host incorrectly set to 0.0.0.0 instead of specific IP addresses

  5. Static Nodes:

    • ⚠️ Most RPC nodes missing static-nodes.json (only 2400 and 2500 have it)

  6. Permissions:

    • ⚠️ Several RPC nodes (2401, 2402, 2503-2508) missing permissions-nodes.toml

Service Issues

  1. VMID 2400:

    • ⚠️ Systemd service shows "inactive" but Besu process is running
    • ✅ Ports are listening and nodes are syncing
    • Action: Verify systemd service name or check if started manually

  2. VMID 2500-2502:

    • ✅ Services are active and running correctly
    • ✅ Ports are listening and nodes are syncing

  3. VMID 2401, 2402, 2505-2508:

    • ❌ Services not running
    • ❌ No Besu processes active

Connectivity Issues

  1. VMID 2500:

    • ⚠️ Error in logs: ArrayIndexOutOfBoundsException for eth_feeHistory method
    • ✅ Still syncing and has 5 peers

  2. VMID 2400:

    • ⚠️ Only 2 peers (validators have 11-12 peers)
    • ✅ Still syncing blocks

RPC Endpoint Issues

  1. VMID 2400, 2500-2502:
    • ⚠️ RPC endpoints returning HTML instead of JSON (may be behind reverse proxy)
    • ✅ Ports 8545 are listening

Recommendations

Immediate Actions Required

  1. Fix VMID 2401, 2402:

    • Update p2p-host in config to specific IPs (192.168.11.241, 192.168.11.242)
    • Copy static-nodes.json from VMID 2400
    • Copy permissions-nodes.toml from VMID 2400
    • Start besu-rpc service

  2. Start VMID 2503, 2504:

    • Start containers: pct start 2503 and pct start 2504
    • Verify service status after startup

  3. Fix VMID 2500:

    • ⚠️ CRITICAL: Network ID is 138 but should be 2400 for TCG Verse
    • Update network-id in /etc/besu/config-rpc.toml to 2400
    • Restart service after change

  4. Fix VMID 2501, 2502:

    • Verify network ID in config files
    • Check file permissions if network-id not readable
    • Ensure network ID is 2400 for TCG Verse

  5. Fix VMID 2505-2508:

    • Install Besu if not installed
    • Create configuration files
    • Verify network ID is 2400
    • Copy static-nodes.json and permissions-nodes.toml
    • Create and start besu-rpc services

Configuration Improvements

  1. Standardize Configuration:

    • Ensure all RPC nodes have config files in /etc/besu/
    • Verify all nodes have correct p2p-host (specific IP, not 0.0.0.0)
    • Ensure all nodes have static-nodes.json and permissions-nodes.toml

  2. Service Management:

    • Verify systemd service names for VMID 2400, 2500-2502
    • Ensure all services are enabled: systemctl enable besu-rpc
    • Standardize service startup across all nodes

  3. Network Configuration:

    • Verify all nodes have correct network IDs (138 for Defi Oracle, 2400 for TCG Verse)
    • Ensure P2P hosts match container IP addresses

Monitoring

  1. Peer Connectivity:

    • Monitor peer counts (validators have 11-12, RPC nodes should have similar)
    • VMID 2400 has only 2 peers - investigate connectivity

  2. Block Sync:

    • All active nodes appear to be syncing (block heights consistent)
    • Monitor sync status regularly

  3. RPC Endpoints:

    • Verify RPC endpoints return JSON (not HTML)
    • Test all RPC methods for functionality

Maintenance

  1. Regular Checks:

    • Weekly service status review
    • Monthly configuration audit
    • Quarterly peer connectivity analysis

  2. Documentation:

    • Document configuration file locations for VMID 2500-2508
    • Document any non-standard service names
    • Maintain inventory of static nodes and permissions

Summary

Total Containers Reviewed: 18

  • Validators: 5 (1000-1004) - ✅ ALL OPERATIONAL
  • RPC Nodes: 13 (2400-2402, 2500-2508)

Operational Status

✅ Fully Operational: 8 nodes

  • Validators: 5 (1000-1004)
  • RPC Nodes: 3 (2400, 2500-2502)

⚠️ Configuration Issues: 1 node

  • VMID 2500: Network ID is 138 (expected 2400 for TCG Verse chain)

❌ Not Operational: 8 nodes

  • VMID 2401, 2402: Services not running, configuration issues
  • VMID 2503, 2504: Containers stopped
  • VMID 2505-2508: Services not running, missing configuration

Key Findings

  1. Validators: All 5 validators are healthy with 11-12 peers each
  2. Chain 138 RPC: Only 1 of 3 nodes operational (2400)
  3. Chain 2400 RPC: Only 3 of 9 nodes operational (2500-2502)
  4. Configuration: Many RPC nodes missing standard config files
  5. Services: Several nodes running but systemd services show inactive

Status: 📊 REVIEW COMPLETE - ACTION REQUIRED

Last Updated: 2026-01-03

Reference in New Issue View Git Blame Copy Permalink