fbda1b4beb
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>
3.5 KiB
3.5 KiB
RPC VMID Migration - Current Status
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Date: 2025-01-20
Status: 🔄 IN PROGRESS
Migration Progress
The migration script is currently running. Cloning containers can take 30-60 minutes per container depending on size and storage speed.
Current Status
Migration Started: 2025-01-20 08:00
Process: Running in background
Completed Migrations
- ⏳ 2504 → 2304 (besu-rpc-ali-0x1) - IN PROGRESS
- Status: Clone operation running
- New VMID 2304 exists but in "create" state
- Old VMID 2504 stopped for cloning
Pending Migrations
The following migrations are queued and will proceed after current clone completes:
- ⏳ 2500 → 2101 (besu-rpc-core-1)
- ⏳ 2501 → 2201 (besu-rpc-public-1)
- ⏳ 2502 → 2301 (besu-rpc-private-1)
- ⏳ 2400 → 2401 (besu-rpc-thirdweb-0x8a-1)
- ⏳ 2401 → 2402 (besu-rpc-thirdweb-0x8a-2)
- ⏳ 2402 → 2403 (besu-rpc-thirdweb-0x8a-3)
- ⏳ 2503 → 2303 (besu-rpc-ali-0x8a)
- ⏳ 2505 → 2305 (besu-rpc-luis-0x8a)
- ⏳ 2506 → 2306 (besu-rpc-luis-0x1)
- ⏳ 2507 → 2307 (besu-rpc-putu-0x8a)
- ⏳ 2508 → 2308 (besu-rpc-putu-0x1)
Monitoring Migration
Check Clone Progress
# Check if clone processes are running
ssh root@192.168.11.10 "ps aux | grep 'pct clone' | grep -v grep"
# Check status of new VMIDs
ssh root@192.168.11.10 "pct list | grep -E '^(2101|2201|2301|2303|2304|2305|2306|2307|2308|2401|2402|2403)'"
# Check status of old VMIDs
ssh root@192.168.11.10 "pct list | grep -E '^(2500|2501|2502|2503|2504|2505|2506|2507|2508|2400|2401|2402)'"
Check Migration Log
tail -f /tmp/rpc-migration.log
Expected Timeline
- Per Container Clone: 5-15 minutes (depending on size)
- Total Migration Time: 1-3 hours for all 12 containers
- Network Configuration: ~1 minute per container
- Total Estimated Time: 2-4 hours
What's Happening
- Clone Operation: Creating full copies of containers with new VMIDs
- Storage Allocation: Allocating disk space for new containers
- Network Configuration: Updating IP addresses after clone completes
- Hostname Update: Setting new hostnames
Important Notes
- ✅ Old containers remain intact (for safety)
- ✅ Old containers are stopped during cloning
- ✅ Migration can be safely interrupted (old containers preserved)
- ⚠️ Do not delete old containers until new ones are verified
- ⚠️ Migration script will skip already-cloned VMIDs if re-run
Next Steps After Migration Completes
- Verify all new VMIDs exist and are configured
- Start new containers
- Deploy Besu node files to new containers
- Restart Besu services
- Verify connectivity
- Update NPMplus proxy rules (if needed)
- Decommission old containers (after verification)
Troubleshooting
If Migration Appears Stuck
-
Check if clone process is actually running:
ssh root@192.168.11.10 "ps aux | grep 'pct clone'" -
Check storage space:
ssh root@192.168.11.10 "vgs && lvs" -
Check container status:
ssh root@192.168.11.10 "pct list | grep create"
If Migration Fails
- Check error logs
- Verify storage availability
- Check network connectivity
- Re-run migration script (it will skip completed migrations)
Last Updated: 2025-01-20 08:05
Next Check: Monitor clone progress