Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
212 lines
4.8 KiB
Markdown
212 lines
4.8 KiB
Markdown
# Besu Configuration Deployment - Complete
|
|
|
|
**Last Updated:** 2026-01-31
|
|
**Document Version:** 1.0
|
|
**Status:** Active Documentation
|
|
|
|
---
|
|
|
|
**Date**: 2026-01-17
|
|
**Status**: ✅ **DEPLOYMENT COMPLETE**
|
|
**Deployment Time**: 2026-01-17
|
|
|
|
---
|
|
|
|
## Deployment Summary
|
|
|
|
### Successfully Deployed Nodes
|
|
|
|
**Validators (5/5)** ✅:
|
|
- VMID 1000 - besu-validator-1
|
|
- VMID 1001 - besu-validator-2
|
|
- VMID 1002 - besu-validator-3
|
|
- VMID 1003 - besu-validator-4
|
|
- VMID 1004 - besu-validator-5
|
|
|
|
**Sentries (4/4)** ✅:
|
|
- VMID 1500 - besu-sentry-1
|
|
- VMID 1501 - besu-sentry-2
|
|
- VMID 1502 - besu-sentry-3
|
|
- VMID 1503 - besu-sentry-4
|
|
|
|
**RPC Nodes (1/1 running)** ✅:
|
|
- VMID 2101 - besu-rpc-core-1
|
|
|
|
**Total**: 10 nodes deployed
|
|
|
|
---
|
|
|
|
## Deployment Details
|
|
|
|
### Configuration Changes Deployed
|
|
|
|
For all nodes:
|
|
- ✅ Removed 11 deprecated options
|
|
- ✅ Logging optimized (WARN for validators/RPC, INFO for sentries)
|
|
- ✅ CORS hardened (specific origins for core RPC)
|
|
- ✅ Empty comments cleaned
|
|
- ✅ All configs validated before deployment
|
|
|
|
### Backup Status
|
|
|
|
All existing configurations were backed up with timestamps:
|
|
- Backup format: `/etc/besu/config-*.toml.backup.YYYYMMDD_HHMMSS`
|
|
- All backups created successfully before deployment
|
|
|
|
---
|
|
|
|
## Post-Deployment Verification
|
|
|
|
### Service Status
|
|
|
|
All services restarted successfully:
|
|
- ✅ All validator services: Active
|
|
- ✅ All sentry services: Active
|
|
- ✅ RPC service (2101): Active
|
|
|
|
### Configuration Verification
|
|
|
|
- ✅ All configs deployed and validated
|
|
- ✅ No deprecated options detected
|
|
- ✅ Logging levels correct:
|
|
- Validators: WARN
|
|
- Sentries: INFO
|
|
- RPC: WARN
|
|
|
|
### Error Checking
|
|
|
|
Run verification:
|
|
```bash
|
|
./scripts/verify-post-deployment.sh
|
|
```
|
|
|
|
---
|
|
|
|
## Monitoring Plan
|
|
|
|
### Immediate (0-1 hour)
|
|
|
|
- [ ] Verify all services are active
|
|
- [ ] Check for configuration errors in logs
|
|
- [ ] Verify logging levels are correct
|
|
- [ ] Test RPC endpoints (if applicable)
|
|
|
|
### Short-term (1-6 hours)
|
|
|
|
- [ ] Monitor service status
|
|
- [ ] Check for configuration-related errors
|
|
- [ ] Verify network connectivity
|
|
- [ ] Test consensus participation (validators)
|
|
- [ ] Test archive queries (sentries)
|
|
|
|
### Medium-term (6-48 hours)
|
|
|
|
- [ ] Monitor resource usage (memory, CPU, disk)
|
|
- [ ] Check peer connections
|
|
- [ ] Verify sync status
|
|
- [ ] Monitor for performance issues
|
|
|
|
---
|
|
|
|
## Verification Commands
|
|
|
|
### Check Service Status
|
|
|
|
```bash
|
|
# Validators
|
|
for vmid in 1000 1001 1002 1003 1004; do
|
|
pct exec $vmid -- systemctl status besu-validator.service
|
|
done
|
|
|
|
# Sentries
|
|
for vmid in 1500 1501 1502 1503; do
|
|
pct exec $vmid -- systemctl status besu-sentry.service
|
|
done
|
|
|
|
# RPC
|
|
pct exec 2101 -- systemctl status besu-rpc.service
|
|
```
|
|
|
|
### Check Logging Levels
|
|
|
|
```bash
|
|
# Validators (should be WARN)
|
|
pct exec 1000 -- grep "^logging" /etc/besu/config-validator.toml
|
|
|
|
# Sentries (should be INFO)
|
|
pct exec 1500 -- grep "^logging" /etc/besu/config-sentry.toml
|
|
|
|
# RPC (should be WARN)
|
|
pct exec 2101 -- grep "^logging" /etc/besu/config-rpc-core.toml
|
|
```
|
|
|
|
### Check for Errors
|
|
|
|
```bash
|
|
# Check recent logs for errors
|
|
pct exec 1000 -- journalctl -u besu-validator.service --since "1 hour ago" | grep -i "error\|unknown option"
|
|
|
|
pct exec 1500 -- journalctl -u besu-sentry.service --since "1 hour ago" | grep -i "error\|unknown option"
|
|
|
|
pct exec 2101 -- journalctl -u besu-rpc.service --since "1 hour ago" | grep -i "error\|unknown option"
|
|
```
|
|
|
|
---
|
|
|
|
## Skipped Nodes
|
|
|
|
The following RPC nodes were skipped (not running):
|
|
- VMID 2500-2508: Stopped containers (will deploy when started)
|
|
|
|
**Note**: These nodes will be deployed automatically when started and deployment script is run again.
|
|
|
|
---
|
|
|
|
## Rollback Procedure
|
|
|
|
If issues are detected, rollback using backups:
|
|
|
|
```bash
|
|
# For each node, restore from backup
|
|
# Example for validator 1000:
|
|
pct exec 1000 -- cp /etc/besu/config-validator.toml.backup.YYYYMMDD_HHMMSS /etc/besu/config-validator.toml
|
|
pct exec 1000 -- systemctl restart besu-validator.service
|
|
```
|
|
|
|
**Backup locations**: All backups are on each node at `/etc/besu/config-*.toml.backup.*`
|
|
|
|
---
|
|
|
|
## Deployment Logs
|
|
|
|
Deployment logs saved:
|
|
- Deployment log: `/tmp/besu-deployment.log`
|
|
- Verification log: `/tmp/post-deployment-verification.log`
|
|
|
|
---
|
|
|
|
## Related Documentation
|
|
|
|
- `DEPLOYMENT_CHECKLIST.md` - Pre-deployment checklist
|
|
- `BESU_DEPLOYMENT_MONITORING.md` - Post-deployment monitoring guide
|
|
- `BESU_IMPLEMENTATION_COMPLETE.md` - Implementation summary
|
|
- `CONFIG_CHANGELOG.md` - Configuration change history
|
|
|
|
---
|
|
|
|
## Deployment Sign-Off
|
|
|
|
**Deployment Status**: ✅ **COMPLETE**
|
|
|
|
**Deployed By**: Automated deployment script
|
|
**Deployment Date**: 2026-01-17
|
|
**Nodes Deployed**: 10 nodes (all running nodes)
|
|
**Configuration Version**: Cleaned and validated (v23.10.0+ compatible)
|
|
|
|
**Next Review**: Monitor for 24-48 hours, then review status
|
|
|
|
---
|
|
|
|
**Last Updated**: 2026-01-17
|
|
**Status**: Deployment Complete - Monitoring Active
|