94 lines
2.2 KiB
Markdown
94 lines
2.2 KiB
Markdown
|
# Enode Collection Status - VMIDs 2400, 2402, 2403
|
||
|
|
|
||
|
|
**Last Updated:** 2026-01-31
|
||
|
|
**Document Version:** 1.0
|
||
|
|
**Status:** Active Documentation
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
**Date**: 2025-01-18
|
||
|
|
**Status**: Partial success
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Collection Results
|
||
|
|
|
||
|
|
### ✅ VMID 2400 (192.168.11.240) - SUCCESS
|
||
|
|
|
||
|
|
**Enode Collected**:
|
||
|
|
```
|
||
|
|
enode://38e138ea5a4b0b244e4484b5c327631b5d3c849dcb188ff3d9ff0a8b6ad7edb738303a1a948888c269aa7555e5ff47d75b7b63dbd579d05580b5442b3fa0ebfc@192.168.11.240:30303
|
||
|
|
```
|
||
|
|
|
||
|
|
**Status**: ✅ **Added to allowlist**
|
||
|
|
|
||
|
|
**Method**: Admin RPC API via `pct exec` - successful
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### ⚠️ VMID 2402 (192.168.11.242) - PENDING
|
||
|
|
|
||
|
|
**Status**: Admin RPC API not accessible or disabled
|
||
|
|
|
||
|
|
**Possible Reasons**:
|
||
|
|
- Admin API not enabled in Besu config
|
||
|
|
- Besu service may not be fully started
|
||
|
|
- RPC port may not be accessible
|
||
|
|
|
||
|
|
**Action Required**:
|
||
|
|
1. Check if ADMIN is in `rpc-http-api` list in Besu config
|
||
|
|
2. Verify Besu service is running: `pct exec 2402 -- systemctl status besu`
|
||
|
|
3. Check if admin API is accessible: Try `admin_nodeInfo` RPC call
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### ⚠️ VMID 2403 (192.168.11.243) - PENDING
|
||
|
|
|
||
|
|
**Status**: Admin RPC API not accessible or disabled
|
||
|
|
|
||
|
|
**Possible Reasons**:
|
||
|
|
- Admin API not enabled in Besu config
|
||
|
|
- Besu service may not be fully started
|
||
|
|
- RPC port may not be accessible
|
||
|
|
|
||
|
|
**Action Required**:
|
||
|
|
1. Check if ADMIN is in `rpc-http-api` list in Besu config
|
||
|
|
2. Verify Besu service is running: `pct exec 2403 -- systemctl status besu`
|
||
|
|
3. Check if admin API is accessible: Try `admin_nodeInfo` RPC call
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Allowlist Update Status
|
||
|
|
|
||
|
|
**File Updated**: `smom-dbis-138/config/permissions-nodes.toml`
|
||
|
|
|
||
|
|
**Status**:
|
||
|
|
- ✅ 2400 added
|
||
|
|
- ⏸️ 2402 pending (enode needed)
|
||
|
|
- ⏸️ 2403 pending (enode needed)
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Next Steps
|
||
|
|
|
||
|
|
### To Complete Collection for 2402 and 2403:
|
||
|
|
|
||
|
|
**Option 1: Enable Admin API** (if disabled)
|
||
|
|
```toml
|
||
|
|
rpc-http-api=["ETH","NET","WEB3","TXPOOL","QBFT","ADMIN"]
|
||
|
|
```
|
||
|
|
|
||
|
|
**Option 2: Check Besu Logs for Enode**
|
||
|
|
```bash
|
||
|
|
ssh root@192.168.11.10 "pct exec 2402 -- journalctl -u besu -n 100 | grep -i enode"
|
||
|
|
ssh root@192.168.11.10 "pct exec 2403 -- journalctl -u besu -n 100 | grep -i enode"
|
||
|
|
```
|
||
|
|
|
||
|
|
**Option 3: Extract from Node Key** (if available)
|
||
|
|
- Check `/data/besu/key` or `/etc/besu/key` directories
|
||
|
|
- Use Besu CLI tools to generate enode from key
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
**Last Updated**: 2025-01-18
|