proxmox/docs/06-besu/BESU_NODES_TWEAKS_AND_FOLLOWUPS.md

Besu Nodes – Tweaks and Follow-ups

Last updated: 2026-02-13

VMIDs 2503, 2504, 2505 (HYBX RPC)

• Host: r630-01 (192.168.11.11). IPs: .246, .247, .248.
• Service: These containers use besu.service (not besu-rpc). The unit expects /opt/besu/bin/besu, which is not installed in these CTs, so the service was crash-looping.
• Tweak applied: besu.service was stopped and disabled on 2503, 2504, 2505 to stop the crash loop.
• To use as RPC later: Install Besu in each container (e.g. copy from 2101 or use the same install method as other RPC nodes), then enable and start besu.service.

VMIDs 2307, 2308 (Putu RPC)

• Host: ml110. IPs: .237, .238 (RPC); P2P advertised as .203, .204.
• Tweaks applied: Enodes added to config/besu-node-lists/static-nodes.json and permissions-nodes.toml; node lists deployed to all nodes; config fixed (permissions TOML path, etc.); Besu restarted.
• Follow-up: After restart, nodes may show "Compacting database" and RPC may not respond for several minutes. Once startup completes, they will sync from ~1.88M toward chain head. Recheck with scripts/review-sentry-and-rpc-nodes.sh or curl -s -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' http://192.168.11.237:8545.

Review script

• scripts/review-sentry-and-rpc-nodes.sh now treats 2503–2505 as besu.service and shows a clear message when that service is inactive (e.g. "HYBX: Besu not installed or disabled").
• scripts/besu/restart-besu-reload-node-lists.sh includes 2307 and 2308 in the VMID list so they are restarted when node lists are reloaded.

Fix-all script

• scripts/besu/fix-all-besu-nodes.sh deploys canonical node lists, normalizes config (permissions TOML path, remove tx-pool-min-score, genesis), and restarts Besu on all nodes. Run: bash scripts/besu/fix-all-besu-nodes.sh. Use --no-restart to skip restarts.