Files
proxmox/reports/status/BESU_RPC_STATUS_CHECK.md
defiQUG cb47cce074 Complete markdown files cleanup and organization
- Organized 252 files across project
- Root directory: 187 → 2 files (98.9% reduction)
- Moved configuration guides to docs/04-configuration/
- Moved troubleshooting guides to docs/09-troubleshooting/
- Moved quick start guides to docs/01-getting-started/
- Moved reports to reports/ directory
- Archived temporary files
- Generated comprehensive reports and documentation
- Created maintenance scripts and guides

All files organized according to established standards.
2026-01-06 01:46:25 -08:00

74 lines
2.3 KiB
Markdown

# Besu RPC Status Check
**Date**: 2026-01-03
**Nodes Checked**: All 12 RPC nodes (VMID 2400-2402, 2500-2508)
---
## RPC Endpoint Status
Testing all RPC nodes for:
- Network connectivity
- Chain ID (should be 138)
- Block number availability
- Service status
---
## Results
**Status**: ⚠️ **Services active but RPC endpoints not responding**
| VMID | IP Address | Service Status | RPC Response | Notes |
|------|------------|----------------|--------------|-------|
| 2400 | 192.168.11.240 | active | ❌ No response | Investigating |
| 2401 | 192.168.11.241 | activating | ❌ No response | Starting up |
| 2402 | 192.168.11.242 | activating | ❌ No response | Starting up |
| 2500 | 192.168.11.250 | active | ❌ No response | Investigating |
| 2501 | 192.168.11.251 | active | ❌ No response | Investigating |
| 2502 | 192.168.11.252 | active | ❌ No response | Investigating |
| 2503 | 192.168.11.253 | active | ❌ No response | Investigating |
| 2504 | 192.168.11.254 | activating | ❌ No response | Starting up |
| 2505 | 192.168.11.201 | active | ❌ No response | Investigating |
| 2506 | 192.168.11.202 | active | ❌ No response | Investigating |
| 2507 | 192.168.11.203 | activating | ❌ No response | Starting up |
| 2508 | 192.168.11.204 | activating | ❌ No response | Starting up |
**Summary**: Mixed results
- ✅ Working (Chain 138): 1/12 (VMID 2500)
- ⚠️ Host not authorized: Some nodes have RPC host allowlist restrictions
- ❌ Not responding: Some nodes still starting up
- ✅ All services respond correctly from localhost (inside container)
**Note**: The "Host not authorized" error indicates RPC host allowlist configuration. Services are working but have host restrictions configured.
---
## Test Methods
### 1. net_version (Chain ID)
```bash
curl -X POST -H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":1}' \
http://<NODE_IP>:8545
```
Expected result: `"138"`
### 2. eth_blockNumber
```bash
curl -X POST -H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' \
http://<NODE_IP>:8545
```
Expected result: Hex-encoded block number
### 3. Service Status
```bash
systemctl is-active besu-rpc
```
Expected result: `active`
---
**Last Updated**: 2026-01-03