Runbook · Maxedge

export-maxcloud stopped — no data in MaxCloud

Export

Symptom

Unit's last-seen timestamp in MaxCloud is stale; customer dashboard shows no new data.

Investigate

SSH in, run docker ps — is export-maxcloud Up? Check logs for auth/TLS errors or full disk (df -h). Confirm outbound internet from the VM (curl to the AWS endpoint).

Fix

docker logs --tail 200 export-maxcloud
docker restart export-maxcloud
# if disk full:
df -h && docker system prune

Buffered data uploads automatically after restart. If auth errors persist, the unit's cloud credentials may have rotated — check Edge Manager.

Steps

Check MaxCloud → unit → last seen. Crane running but last seen > 15 min → export problem.
SSH in (guide) and run docker ps. Container not Up → docker logs --tail 200 export-maxcloud.
Disk full (df -h at 100 %): docker system prune, then restart the container.
TLS / DNS errors: from the VM run curl -sI https://ingest.maxcloud.lh.internal. Fails → crane firewall / customer uplink problem, not Maxedge.
401 / auth errors: credentials rotated. Edge Manager → device → Cloud credentials → re-issue.
Verify: last seen updates within 5 minutes; the buffer backfills in the background.

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