Files
proxmox/R630_01_02_COMPLETE_INVENTORY.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 15:46:57 -08:00

10 KiB

R630-01 and R630-02 Complete VMID Inventory

Date: 2026-01-26
Status: Complete Inventory with IP Addresses


Summary

  • R630-01 (192.168.11.11): 60+ LXC containers
  • R630-02 (192.168.11.12): 10 LXC containers
  • LXC Config Location: /etc/pve/lxc/<VMID>.conf on each Proxmox host
  • Config Format: Plain text key-value pairs (not YAML/TOML)

R630-01 (192.168.11.11) - Complete Inventory

VMID Hostname IP Address Status Service Type
100 proxmox-mail-gateway 192.168.11.32 running Infrastructure
101 proxmox-datacenter-manager 192.168.11.33 running Infrastructure
102 cloudflared 192.168.11.34 running Infrastructure
103 omada 192.168.11.30 running Infrastructure
104 gitea 192.168.11.31 running Infrastructure
105 nginxproxymanager 192.168.11.26 running Infrastructure
106 redis-rpc-translator 192.168.11.110 stopped RPC Translator
107 web3signer-rpc-translator 192.168.11.111 stopped RPC Translator
108 vault-rpc-translator 192.168.11.112 stopped RPC Translator
130 monitoring-1 192.168.11.27 running Monitoring
1000 besu-validator-1 192.168.11.100 running Besu Validator
1001 besu-validator-2 192.168.11.101 running Besu Validator
1002 besu-validator-3 192.168.11.102 running Besu Validator
1500 besu-sentry-1 192.168.11.150 running Besu Sentry
1501 besu-sentry-2 192.168.11.151 running Besu Sentry
1502 besu-sentry-3 192.168.11.152 running Besu Sentry
2101 besu-rpc-core-1 192.168.11.211 running Besu RPC
2500 besu-rpc-alltra-1 192.168.11.172 running Besu RPC
2501 besu-rpc-alltra-2 192.168.11.173 running Besu RPC
2502 besu-rpc-alltra-3 192.168.11.174 running Besu RPC
2503 besu-rpc-hybx-1 192.168.11.246 running Besu RPC
2504 besu-rpc-hybx-2 192.168.11.247 running Besu RPC
2505 besu-rpc-hybx-3 192.168.11.248 running Besu RPC
3000 ml110 192.168.11.60 running Service
3001 ml110 192.168.11.61 running Service
3002 ml110 192.168.11.62 running Service
3003 ml110 192.168.11.63 running Service
3500 oracle-publisher-1 192.168.11.29 running Oracle Publisher
3501 ccip-monitor-1 192.168.11.28 running CCIP Monitor
5200 cacti-1 192.168.11.80 running Hyperledger Cacti
5201 cacti-alltra-1 192.168.11.177 running Hyperledger Cacti
5202 cacti-hybx-1 192.168.11.251 running Hyperledger Cacti
6000 fabric-1 192.168.11.113 running Hyperledger Fabric
6001 fabric-alltra-1 192.168.11.178 running Hyperledger Fabric
6002 fabric-hybx-1 192.168.11.252 running Hyperledger Fabric
6400 indy-1 192.168.11.64 running Hyperledger Indy
6401 indy-alltra-1 192.168.11.179 running Hyperledger Indy
6402 indy-hybx-1 192.168.11.253 running Hyperledger Indy
7800 sankofa-api-1 192.168.11.50 running Sankofa API
7801 sankofa-portal-1 192.168.11.51 running Sankofa Portal
7802 sankofa-keycloak-1 192.168.11.52 running Sankofa Keycloak
7803 sankofa-postgres-1 192.168.11.53 running Sankofa PostgreSQL
8640 vault-phoenix-1 192.168.11.200 running Vault
8642 vault-phoenix-3 192.168.11.202 running Vault
10000 (stopped) 192.168.11.44 stopped
10001 (stopped) 192.168.11.45 stopped
10020 (stopped) 192.168.11.48 stopped
10030 (running) 192.168.11.40 running
10040 (running) 192.168.11.41 running
10050 (running) 192.168.11.49 running
10060 (running) 192.168.11.42 running
10070 (running) 192.168.11.54 running
10080 (running) 192.168.11.43 running
10090 (running) 192.168.11.36 running
10091 (running) 192.168.11.35 running
10092 (running) 192.168.11.37 running
10100 (stopped) 192.168.11.105 stopped
10101 (stopped) 192.168.11.106 stopped
10120 (stopped) 192.168.11.125 stopped
10130 dbis-frontend 192.168.11.130 running DBIS Frontend
10150 dbis-api-primary 192.168.11.155 running DBIS API
10151 dbis-api-secondary 192.168.11.156 running DBIS API
10200 (running) 192.168.11.46 running
10201 (running) 192.168.11.47 running
10202 order-opensearch 192.168.11.48 running Order Service
10210 order-haproxy 192.168.11.39 running Order Service
10230 (running) 192.168.11.55 running
10232 (running) 192.168.11.56 running
10233 (stopped) 192.168.11.166 stopped

R630-02 (192.168.11.12) - Complete Inventory

VMID Hostname IP Address Status Service Type
2201 besu-rpc-public-1 192.168.11.221 running Besu RPC
2303 besu-rpc-ali-0x8a 192.168.11.233 running Besu RPC
2401 besu-rpc-thirdweb-0x8a-1 192.168.11.241 running Besu RPC
5000 blockscout-1 192.168.11.140 running Blockchain Explorer
6200 firefly-1 192.168.11.35 running Hyperledger Firefly
6201 firefly-ali-1 192.168.11.57 stopped Hyperledger Firefly
7810 mim-web-1 192.168.11.37 running Miracles in Motion
7811 mim-api-1 192.168.11.36 running Miracles in Motion
8641 vault-phoenix-2 192.168.11.201 running Vault
10234 npmplus-secondary 192.168.11.168 stopped NPM Plus

LXC Container Configuration Files

Location

LXC container configuration files are stored on each Proxmox host at:

  • Path: /etc/pve/lxc/<VMID>.conf
  • Format: Plain text key-value pairs (NOT YAML or TOML)
  • Permissions: root:www-data (644)

Example Configuration File

VMID 100 (proxmox-mail-gateway) on r630-01:

arch: amd64
cores: 2
hostname: proxmox-mail-gateway
memory: 4096
net0: name=eth0,bridge=vmbr0,gw=192.168.11.1,hwaddr=BC:24:11:3F:A2:B0,ip=192.168.11.32/24,type=veth
onboot: 1
ostype: debian
rootfs: thin1:vm-100-disk-0,size=10G
swap: 512
unprivileged: 1

VMID 5000 (blockscout-1) on r630-02:

arch: amd64
cores: 4
hostname: blockscout-1
memory: 2147483648
net0: name=eth0,bridge=vmbr0,gw=192.168.11.1,hwaddr=BC:24:11:3C:58:2B,ip=192.168.11.140/24,type=veth
onboot: 1
ostype: ubuntu
rootfs: thin1-r630-02:vm-5000-disk-0,size=200G
swap: 1073741824
unprivileged: 1

Accessing Configuration Files

# View config for a specific container on r630-01
ssh root@192.168.11.11 "cat /etc/pve/lxc/100.conf"

# View config for a specific container on r630-02
ssh root@192.168.11.12 "cat /etc/pve/lxc/5000.conf"

# List all config files on r630-01
ssh root@192.168.11.11 "ls -la /etc/pve/lxc/*.conf"

# List all config files on r630-02
ssh root@192.168.11.12 "ls -la /etc/pve/lxc/*.conf"

# View config using pct command (recommended)
ssh root@192.168.11.11 "pct config 100"
ssh root@192.168.11.12 "pct config 5000"

Quick Reference Commands

List All Containers with IPs

# Use the provided script
./scripts/list-r630-containers.sh all

# Or manually for r630-01
ssh root@192.168.11.11 "pct list | tail -n +2 | while read vmid status lock name; do 
  ip=\$(pct config \$vmid 2>/dev/null | grep '^net0:' | sed -n 's/.*ip=\([^\/]*\).*/\1/p' || echo 'N/A')
  hostname=\$(pct config \$vmid 2>/dev/null | grep '^hostname:' | cut -d' ' -f2 || echo 'N/A')
  echo \"\$vmid|\$hostname|\$ip|\$status\"
done" | column -t -s'|' -N 'VMID,Hostname,IP,Status'

# Or manually for r630-02
ssh root@192.168.11.12 "pct list | tail -n +2 | while read vmid status lock name; do 
  ip=\$(pct config \$vmid 2>/dev/null | grep '^net0:' | sed -n 's/.*ip=\([^\/]*\).*/\1/p' || echo 'N/A')
  hostname=\$(pct config \$vmid 2>/dev/null | grep '^hostname:' | cut -d' ' -f2 || echo 'N/A')
  echo \"\$vmid|\$hostname|\$ip|\$status\"
done" | column -t -s'|' -N 'VMID,Hostname,IP,Status'

View Specific Container Config

# View full config for VMID 100 on r630-01
ssh root@192.168.11.11 "pct config 100"

# View full config for VMID 5000 on r630-02
ssh root@192.168.11.12 "pct config 5000"

# View config file directly
ssh root@192.168.11.11 "cat /etc/pve/lxc/100.conf"
ssh root@192.168.11.12 "cat /etc/pve/lxc/5000.conf"

Deployment Configuration Files

Found in Codebase

The following deployment-related files were found in the codebase:

  1. LXC Deployment Scripts:

    • explorer-monorepo/deployment/scripts/deploy-lxc.sh - Explorer LXC deployment
    • rpc-translator-138/LXC_DEPLOYMENT.md - RPC Translator LXC guide
    • smom-dbis-138-proxmox/scripts/deployment/deploy-services.sh - Service deployment
    • smom-dbis-138-proxmox/scripts/deployment/deploy-hyperledger-services.sh - Hyperledger services
    • smom-dbis-138-proxmox/scripts/deployment/deploy-besu-nodes.sh - Besu node deployment
  2. Configuration Templates:

    • smom-dbis-138-proxmox/config/proxmox.conf.example - Proxmox configuration template
  3. Kubernetes Deployment Files (NOT for LXC):

    • Multiple deployment.yaml files found, but these are for Kubernetes, not LXC containers

Important Note: LXC vs Kubernetes

LXC Containers in Proxmox:

  • Use configuration files: /etc/pve/lxc/<VMID>.conf (on Proxmox hosts)
  • Created with: pct create commands
  • Deployed via: Bash scripts that use pct commands
  • Format: Plain text key-value pairs

Kubernetes Deployments:

  • Use YAML files: deployment.yaml
  • Deployed to: Kubernetes clusters
  • Format: YAML

The deployment.yaml files found in the codebase are for Kubernetes deployments, not LXC containers.


Key Findings

  1. LXC Config Files Location: /etc/pve/lxc/<VMID>.conf on each Proxmox host
  2. Config Format: Plain text key-value pairs (not YAML/TOML)
  3. Total Containers: 70+ containers across both hosts
  4. Oracle Publisher: VMID 3500 on r630-01 (192.168.11.29) - This is the container that needs CoinGecko API key update
  5. Blockscout Explorer: VMID 5000 on r630-02 (192.168.11.140)

Next Steps

  1. Inventory complete
  2. IP addresses extracted
  3. Config file locations identified
  4. ⚠️ Update Oracle Publisher (VMID 3500) with CoinGecko API key (see scripts/update-oracle-publisher-coingecko-key.sh)

Last Updated: 2026-01-26
Generated By: Automated inventory script