Files
proxmox/docs/archive/NEXT_STEPS_VERIFICATION.md

135 lines
3.7 KiB
Markdown

# Next Steps Verification Report
**Date**: $(date)
**Purpose**: Verification of required files and service health after configuration fix
---
## Verification Steps Completed
### ✅ Step 1: Service Status Monitoring
**Status**: Services monitored and status checked
All services are being tracked for activation status.
### ✅ Step 2: Error Log Checking
**Status**: Recent logs checked for errors
Checking for any new errors after configuration fix.
### ✅ Step 3: Required Files Verification
**Files Checked**:
- `/etc/besu/genesis.json` - Network genesis block
- `/etc/besu/static-nodes.json` - Static peer list
- `/etc/besu/permissions-nodes.toml` - Node permissions
**Action Required**: Verify presence and copy if missing.
### ✅ Step 4: Validator Keys Verification
**Location**: `/keys/validators/validator-{N}/`
**Action Required**: Verify keys exist for all validators (1000-1004).
### ✅ Step 5: Process Status Check
**Status**: Checking if Besu processes are actually running
Verifying services aren't just "active" but actually have running processes.
### ✅ Step 6: Log Output Analysis
**Status**: Checking recent logs for startup indicators
Looking for successful startup messages and any warnings.
---
## Required Files Status
### Configuration Files
-`config-validator.toml` - Created (5/5 validators)
-`config-sentry.toml` - Created (3/3 sentries)
-`config-rpc-public.toml` - Created (3/3 RPC nodes)
### Network Files
-`genesis.json` - **TO BE VERIFIED**
-`static-nodes.json` - **TO BE VERIFIED**
-`permissions-nodes.toml` - **TO BE VERIFIED**
### Validator Keys
- ⏳ Validator keys - **TO BE VERIFIED**
---
## Actions Required
### If Files Are Missing
1. **Copy from Source Project**
```bash
# Assuming source project at /opt/smom-dbis-138 on Proxmox host
# Copy genesis.json
for vmid in 1000 1001 1002 1003 1004 1500 1501 1502 2500 2501 2502; do
pct push $vmid /opt/smom-dbis-138/config/genesis.json /etc/besu/genesis.json
pct exec $vmid -- chown besu:besu /etc/besu/genesis.json
done
# Copy static-nodes.json
for vmid in 1000 1001 1002 1003 1004 1500 1501 1502 2500 2501 2502; do
pct push $vmid /opt/smom-dbis-138/config/static-nodes.json /etc/besu/static-nodes.json
pct exec $vmid -- chown besu:besu /etc/besu/static-nodes.json
done
# Copy permissions-nodes.toml
for vmid in 1000 1001 1002 1003 1004 1500 1501 1502 2500 2501 2502; do
pct push $vmid /opt/smom-dbis-138/config/permissions-nodes.toml /etc/besu/permissions-nodes.toml
pct exec $vmid -- chown besu:besu /etc/besu/permissions-nodes.toml
done
```
2. **Copy Validator Keys** (validators only)
```bash
for vmid in 1000 1001 1002 1003 1004; do
validator_num=$((vmid - 999))
# Copy keys from source project
pct push $vmid /opt/smom-dbis-138/keys/validators/validator-${validator_num} /keys/validators/validator-${validator_num}
pct exec $vmid -- chown -R besu:besu /keys/validators/validator-${validator_num}
done
```
---
## Service Health Indicators
### Good Signs
- ✅ Service status: "active"
- ✅ Besu process running
- ✅ No errors in logs
- ✅ Startup messages in logs
- ✅ Process using resources (CPU/memory)
### Warning Signs
- ⚠️ Service status: "activating" for extended time (> 2 minutes)
- ⚠️ Service restarts frequently
- ⚠️ Errors in logs
- ⚠️ No Besu process running
- ⚠️ Missing required files
---
## Next Actions After Verification
1. **If Files Missing**: Copy required files from source project
2. **If Services Not Starting**: Check logs for specific errors
3. **If Validator Keys Missing**: Copy keys and restart services
4. **If All Good**: Monitor services for stability
---
**Verification Started**: $(date)