Runbook · Maxedge

VM / Proxmox host issues

Host

Symptom

Whole Maxedge unreachable — no dashboard, no SSH, but crane network otherwise fine.

Investigate

Open Proxmox UI https://192.168.30.110:8006 (root, password in Vault → lh/maxedge/proxmox). Is the VM running? Host resource alarms (disk, RAM)? If the host UI is also down, the IPC may be powered off — check cabinet.

Fix

# Proxmox UI: node -> VM maxedge -> Start / Reboot
# host shell (from UI or ssh root@192.168.30.110):
qm list
qm start <vmid>
journalctl -p err -b

After unplanned power loss the VM auto-starts; if it doesn't, check 'Start at boot' option and host storage health (smartctl).

Steps

ping 192.168.30.110. No reply → IPC powered off or its OT link down; check the cabinet (power LED, switch port 5–6 link lights).
Proxmox UI reachable → Datacenter → node → VM maxedge: stopped → Start; hung → Reboot.
Host alarms: disk > 90 % or RAM pressure → journalctl -p err -b, smartctl -a /dev/nvme0. Failing NVMe → plan IPC swap via Masterdata ticket.
VM did not auto-start after power loss → VM → Options → Start at boot: yes.
Verify: dashboard on :8080 and SSH back; docker ps all Up.

Not resolved? Escalate to Product Engineering with docker ps -a, the relevant docker logs and the unit's Masterdata link.