170 lines
4.1 KiB
Markdown
170 lines
4.1 KiB
Markdown
# VMID 1503 Review
|
|
|
|
**Date**: $(date)
|
|
**Container**: besu-sentry-4
|
|
**VMID**: 1503
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
VMID 1503 is a sentry container that appears to have been deployed but is missing the Besu service file, causing it to be inactive while other sentries are running.
|
|
|
|
---
|
|
|
|
## Container Status
|
|
|
|
### Basic Information
|
|
|
|
- **VMID**: 1503
|
|
- **Hostname**: besu-sentry-4
|
|
- **IP Address**: (to be verified)
|
|
- **Status**: Running (container is up)
|
|
- **Type**: Sentry node
|
|
|
|
### Container Configuration
|
|
|
|
- **Memory**: 4GB (4096 MB)
|
|
- **CPU Cores**: 2
|
|
- **Disk**: 100GB
|
|
- **Network**: Bridge vmbr0
|
|
|
|
---
|
|
|
|
## Issues Identified
|
|
|
|
### 🔴 Critical Issue: Missing Service File
|
|
|
|
**Problem**: `besu-sentry.service` file is missing from `/etc/systemd/system/`
|
|
|
|
**Impact**:
|
|
- Service cannot be started
|
|
- Container is running but Besu is not
|
|
- Node is not participating in the network
|
|
|
|
**Comparison**:
|
|
- ✅ Other sentries (1500, 1501, 1502): Have service files
|
|
- ❌ VMID 1503: Missing service file
|
|
|
|
---
|
|
|
|
## Files Status
|
|
|
|
### Configuration Files
|
|
|
|
| File | Status | Notes |
|
|
|------|--------|-------|
|
|
| `config-sentry.toml` | ❌ Missing | Should exist |
|
|
| `config-sentry.toml.template` | ⏳ To be checked | May or may not exist |
|
|
| `genesis.json` | ✅ Copied | Should be present after file copy |
|
|
| `static-nodes.json` | ✅ Copied | Should be present after file copy |
|
|
| `permissions-nodes.toml` | ✅ Copied | Should be present after file copy |
|
|
|
|
### Installation Files
|
|
|
|
| Component | Status | Notes |
|
|
|-----------|--------|-------|
|
|
| Besu binary | ⏳ To be checked | Should be at `/opt/besu/bin/besu` |
|
|
| Besu installation | ⏳ To be checked | Should be at `/opt/besu/` |
|
|
| Service file | ❌ Missing | `/etc/systemd/system/besu-sentry.service` |
|
|
|
|
---
|
|
|
|
## Recommended Actions
|
|
|
|
### Option 1: Create Service File (Quick Fix)
|
|
|
|
If Besu is installed, create the service file based on other sentries:
|
|
|
|
```bash
|
|
# Copy service file from working sentry (1500)
|
|
pct exec 1500 -- cat /etc/systemd/system/besu-sentry.service > /tmp/besu-sentry.service
|
|
pct push 1503 /tmp/besu-sentry.service /etc/systemd/system/besu-sentry.service
|
|
pct exec 1503 -- systemctl daemon-reload
|
|
pct exec 1503 -- systemctl enable besu-sentry.service
|
|
pct exec 1503 -- systemctl start besu-sentry.service
|
|
```
|
|
|
|
### Option 2: Re-run Installation Script
|
|
|
|
If Besu is not properly installed, re-run the installation script:
|
|
|
|
```bash
|
|
# Find and run the sentry installation script
|
|
# From the deployment project
|
|
cd /opt/smom-dbis-138-proxmox
|
|
# Check for installation script
|
|
ls -la install/besu-sentry-install.sh
|
|
|
|
# Push and run installation script
|
|
pct push 1503 install/besu-sentry-install.sh /tmp/install.sh
|
|
pct exec 1503 -- bash /tmp/install.sh
|
|
```
|
|
|
|
### Option 3: Verify Deployment
|
|
|
|
Check if this container was intentionally excluded or if there was a deployment issue:
|
|
|
|
```bash
|
|
# Check deployment logs
|
|
# Review deployment script execution for VMID 1503
|
|
# Verify if this was a known exclusion
|
|
```
|
|
|
|
---
|
|
|
|
## Comparison with Other Sentries
|
|
|
|
### Working Sentries (1500, 1501, 1502)
|
|
|
|
- ✅ Service files exist
|
|
- ✅ Configuration files present
|
|
- ✅ Services can be started
|
|
- ✅ Besu processes running
|
|
|
|
### VMID 1503
|
|
|
|
- ❌ Service file missing
|
|
- ⏳ Configuration files status unclear
|
|
- ❌ Service cannot be started
|
|
- ❌ Besu not running
|
|
|
|
---
|
|
|
|
## Verification Steps
|
|
|
|
After applying fixes, verify:
|
|
|
|
```bash
|
|
# Check service file exists
|
|
pct exec 1503 -- ls -la /etc/systemd/system/besu-sentry.service
|
|
|
|
# Check configuration file exists
|
|
pct exec 1503 -- ls -la /etc/besu/config-sentry.toml
|
|
|
|
# Check service status
|
|
pct exec 1503 -- systemctl status besu-sentry.service
|
|
|
|
# Check if Besu process is running
|
|
pct exec 1503 -- ps aux | grep besu
|
|
|
|
# Check logs
|
|
pct exec 1503 -- journalctl -u besu-sentry.service --no-pager -n 20
|
|
```
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. ✅ **Review completed** - Issues identified
|
|
2. ⏳ **Investigate root cause** - Why service file is missing
|
|
3. ⏳ **Apply fix** - Create service file or re-run installation
|
|
4. ⏳ **Verify** - Ensure service starts and runs correctly
|
|
5. ⏳ **Monitor** - Watch for stability
|
|
|
|
---
|
|
|
|
**Review Completed**: $(date)
|
|
**Status**: ⚠️ **ISSUE IDENTIFIED - SERVICE FILE MISSING**
|
|
|