Files

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

2.0 KiB

Raw Permalink Blame History

Besu RPC Minor Warnings - Fixed

Date: 2026-01-04
Status: ✅ WARNINGS ADDRESSED

Summary

Addressed minor operational warnings on VMID 2501, 2506, and 2508 by:

Restarting services to clear transient errors
Optimizing JVM garbage collection settings
Verifying RPC functionality

Issues Identified

VMID 2501

Warning: Thread blocked for 2531ms (exceeded 2000ms limit)
Cause: Transient database operations or resource contention
Status: ✅ Resolved after restart

VMID 2506

Warning: Thread blocked (historical)
Status: ✅ No recent errors

VMID 2508

Warning: Thread blocked + Invalid block import errors
Cause: Transient sync issues and resource contention
Status: ✅ Resolved after restart

Fixes Applied

1. Service Restarts

Restarted all three affected nodes to clear transient errors
Services recovered successfully

2. JVM Optimization

Reduced MaxGCPauseMillis from 200ms to 100ms for faster garbage collection
Added ParallelGCThreads=4 for optimized parallel garbage collection
This helps reduce thread blocking by allowing GC to complete faster

3. Verification

All nodes verified to be responding correctly to RPC requests
Chain ID 138 confirmed
Block numbers accessible

Current Status

✅ All nodes operational

VMID 2501: ✅ No runtime errors, RPC working (Chain 138)
VMID 2506: ✅ No runtime errors, RPC working (Chain 138)
VMID 2508: ✅ No runtime errors, RPC working (Chain 138)

Note: The "exit-code" messages seen in logs are normal systemd notifications from service restarts, not actual runtime errors.

Notes

Thread blocking warnings are typically transient and occur during:
- Database compaction operations
- Large block imports
- Garbage collection cycles
Invalid block import errors are normal during network synchronization and resolve automatically
All warnings were non-critical and did not affect RPC functionality

Last Updated: 2026-01-04

2.0 KiB Raw Permalink Blame History