- 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.
1.5 KiB
1.5 KiB
Next Steps Completion — RPC Stability Hardening
Date: 2026-01-05
What we found
1) Storage node restriction mismatch (startup blocker)
- VMIDs 2400–2402 and 2500–2508 (RPC nodes) use
local-lvm:*asrootfs. - The Proxmox node
ml110is hosting these VMIDs, butlocal-lvmin/etc/pve/storage.cfgwas restricted tor630-01only. - Result: containers could fail to start on
ml110with:storage 'local-lvm' is not available on node 'ml110'
2) Besu heap oversizing (runtime instability)
- VMIDs 2506–2508 had 4GB memory but
BESU_OPTS=-Xmx8g -Xms8g→ high risk of swap/IO thrash. - VMID 2505 had the same symptom earlier and already caused a failure.
Actions taken
Storage fix (cluster config)
- Updated
/etc/pve/storage.cfgonml110to allowlocal-lvmonml110. pvesm statusnow showslocal-lvmactive onml110.
RPC stability fix (node configs)
- VMID 2505:
- Container resources: memory 6144MB, swap 1024MB
- Besu heap:
BESU_OPTS=-Xms2g -Xmx4g
- VMIDs 2506–2508:
- Besu heap right-sized to:
BESU_OPTS=-Xms1g -Xmx2g - Restarted
besu-rpcand confirmed listeners:8545/:8546/:9545
- Besu heap right-sized to:
Verification
- Full RPC fleet retest: 12/12 reachable + authorized, block spread Δ0
- Report:
reports/rpc_nodes_test_20260105_064904.md
- Report:
New reusable scripts added
scripts/audit-proxmox-rpc-storage.shscripts/audit-proxmox-rpc-besu-heap.sh