Files
proxmox/reports/status/BLOCK_PRODUCTION_STATUS.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

2.7 KiB

Block Production Status

Date: 2026-01-04 23:30 PST
Status: ⚠️ Services Active - Block Production Status Being Verified


Current Status

Services

  • Validators (1000-1004): Services are active/activating after configuration fixes
  • Sentries (1500-1503): Services are active

Block Production History

Last Block Production: January 3, 2026 around 21:09-21:12 PST

  • Last produced block: #600,171
  • Blocks were being produced regularly before configuration changes

Recent Activity:

  • Services were restarted multiple times due to configuration errors
  • Configuration has been fixed and services are restarting
  • Nodes may need time to sync before resuming block production

Configuration Issues Fixed

  1. Removed invalid TOML options:

    • qbft-validator-migration-mode-enabled (not supported)
    • max-remote-initiated-connections (not supported)
    • rpc-http-host-allowlist (not supported)
  2. Removed incompatible option:

    • fast-sync-min-peers (cannot be used with FULL sync-mode)
  3. Services are now starting successfully


Next Steps

  1. Wait for Services to Fully Start: Services are currently starting up

    • Allow 2-5 minutes for full initialization
    • Nodes need to sync with the network
  2. Monitor Block Production: Check logs for "Produced" messages

    ./scripts/check-validator-sentry-logs.sh 50
    
  3. Check Sync Status: Verify nodes are synced

    ssh root@192.168.11.10 "pct exec 1000 -- journalctl -u besu-validator.service | grep -i sync"
    
  4. Verify Consensus: Ensure validators can reach consensus

    • All validators must be running and synced
    • Network connectivity between validators must be working

Expected Behavior

Once services are fully started and synced:

  • Blocks should be produced every ~2 seconds (QBFT consensus)
  • Each validator will produce blocks in rotation
  • Logs will show "Produced #XXXXX" messages

Monitoring Commands

# Check if blocks are being produced
ssh root@192.168.11.10 "pct exec 1000 -- journalctl -u besu-validator.service --since '5 minutes ago' | grep -i 'Produced'"

# Check service status
ssh root@192.168.11.10 "pct exec 1000 -- systemctl status besu-validator.service"

# Check current block via RPC (if RPC is enabled)
curl -X POST -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' http://192.168.11.100:8545

Note: Block production will resume once all validators are fully started and synced with the network. The recent configuration changes required service restarts, which temporarily paused block production.