Files
proxmox/docs/archive/DEPLOYMENT_MONITORING.md

2.1 KiB

Deployment Monitoring Guide

Deployment Started: 2025-12-20 13:13:10
Status: Running in background

Monitor Deployment Progress

Check Current Status

ssh root@192.168.11.10
tail -f /tmp/deploy-full.log

Check Deployment Log File

# Latest log file
tail -f /opt/smom-dbis-138-proxmox/logs/deploy-validated-set-*.log | tail -100

Check Container Creation Progress

# See which containers are being created
pct list | grep -E "100[0-4]|150[0-3]|250[0-2]"

# Check specific container status
pct status 1000

Check Deployment Process

# Check if deployment script is still running
ps aux | grep deploy-validated-set

# Check container creation processes
ps aux | grep "pct create"

Expected Progress Indicators

Phase 1: Deploy Containers (30-45 min)

Look for:

  • Creating validator node: besu-validator-{N}
  • Container {VMID} created with DHCP configuration
  • Configuring static IP address
  • Installing Besu in container {VMID}

Phase 2: Copy Configuration (5-10 min)

Look for:

  • Copying Besu configuration files
  • genesis.json copied to all containers
  • Validator keys copied

Phase 3: Bootstrap Network (2-5 min)

Look for:

  • Bootstrapping network
  • Collecting Enodes from Validators
  • static-nodes.json generated

Phase 4: Validate Deployment (2-5 min)

Look for:

  • Running comprehensive deployment validation
  • Container status validation
  • Validation passed

Quick Status Check Commands

# One-liner status check
ssh root@192.168.11.10 "tail -20 /tmp/deploy-full.log 2>/dev/null && echo '' && echo 'Containers:' && pct list | grep -E '100[0-4]|150[0-3]|250[0-2]'"

Completion Indicators

Deployment is complete when you see:

  • ✅ Deployment completed successfully!
  • All containers listed: pct list | grep -E "100[0-4]|150[0-3]|250[0-2]"
  • Total duration reported
  • Next steps displayed

Troubleshooting

If deployment appears stuck:

  1. Check the log file for errors
  2. Verify container creation is progressing
  3. Check system resources (disk space, memory)
  4. Review error messages in the log