explorer-monorepo/CONTAINERS_RESTARTED_FOR_PERSISTENCE.md

Containers Restarted for Network Persistence

Date: 2026-01-22
Status: ✅ RESTART COMPLETE - All containers restarted and network activated

---

Purpose

Restart containers that had network configuration changes to ensure persistent network settings:

• IP address reassignments
• Network interface fixes
• Gateway and routing configuration

---

Containers Restarted

1. VMID 6000 (fabric-1)

• IP Address: 192.168.11.113
• Reason: Network interface fix (was DOWN, IP not assigned)
• Host: r630-01
• Status: ✅ Restarted and network activated (requires manual activation after restart)

2. VMID 10020 (order-redis)

• IP Address: 192.168.11.48 (reassigned from 192.168.11.46)
• Reason: IP conflict resolution
• Host: r630-01
• Status: ✅ Restarted successfully

3. VMID 10234 (npmplus-secondary)

• IP Address: 192.168.11.168 (reassigned from 192.168.11.167)
• Reason: IP conflict resolution
• Host: r630-02
• Status: ✅ Restarted successfully

---

Restart Process

For each container:

1. Stop container: pct stop <VMID>
2. Wait 2 seconds
3. Start container: pct start <VMID>
4. Wait 3 seconds for initialization
5. Verify status: pct status <VMID>

---

Results

✅ Successful Restarts

• VMID 10020: ✅ Network working, IP 192.168.11.48 reachable
• VMID 10234: ✅ Network working, IP 192.168.11.168 reachable

⚠️ VMID 6000 Issue

• Status: Container restarted, but interface requires manual activation
• Issue: Proxmox not automatically bringing interface UP and assigning IP
• Fix Applied: Manual interface activation completed
• Current Status: ✅ Network working, IP 192.168.11.113 reachable

---

VMID 6000 Manual Fix

The interface needs to be brought up manually:

# On Proxmox host (r630-01)
pct exec 6000 -- ip link set eth0 up
pct exec 6000 -- ip addr add 192.168.11.113/24 dev eth0
pct exec 6000 -- ip route add default via 192.168.11.1 dev eth0

Note: This suggests a deeper configuration issue with VMID 6000 that may need investigation.

---

Verification

Network Connectivity

• ✅ 192.168.11.48 (VMID 10020): Reachable
• ✅ 192.168.11.168 (VMID 10234): Reachable
• ✅ 192.168.11.113 (VMID 6000): Reachable (manually activated)

---

Summary

Status: ✅ ALL CONTAINERS RESTARTED AND NETWORK ACTIVATED

• VMID 10020: ✅ Persistent network configuration (automatic)
• VMID 10234: ✅ Persistent network configuration (automatic)
• VMID 6000: ✅ Network activated (requires manual activation after restart)

---

Next Steps:

1. Manually activate VMID 6000 interface
2. Investigate why Proxmox isn't automatically bringing up the interface for VMID 6000