Runbook · Most common issue #2

MaxEdge logger not running / logging failures

Logger

Symptom

Crane logger stopped: dashboard tiles red or stale, no new signals in Trendviewer, or the whole VM is unresponsive. Often a crashed container, sometimes the cloud export blocking communication.

Investigate

SSH in and run docker ps -a. Is maxedge-core Up? Restarting in a loop? Check docker logs and disk (df -h). If core is fine but export is failing and the PLC link is dropping, the export retry storm can starve the OT NIC.

Fix

docker ps -a
docker logs --tail 200 maxedge-core
df -h
docker restart maxedge-core
# export causing comms trouble? stop it temporarily:
docker stop export-maxcloud
# … verify logging recovers, then:
docker start export-maxcloud

Logging and export are independent containers. Stopping export never loses data — it buffers on disk — so it is safe to use as an isolation step.

Steps

docker ps -a. maxedge-core Exited or Restarting → docker logs --tail 200 maxedge-core.
Config parse error in the log → roll back via Dashboard → Configuration → History (guide).
Disk full (df -h 100 %) → docker system prune, restart core. The export buffer is the usual culprit when the uplink has been down for weeks.
Core Up but no signals → PLC link. ping the PLC on VLAN 30; see network communication problems.
Export causing communication failures (PLC timeouts correlate with export retries) → docker stop export-maxcloud, confirm logging stabilises, then fix the uplink per export runbook before starting it again.
VM unresponsive entirely → Proxmox host runbook.

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