Runbook · Most common issue #4

No live data in eHawk

Live data

Symptom

The eHawk session opens and the Maxedge logger is reachable, but the live crane data view shows no values or values frozen at an old timestamp.

Investigate

Confirm the logger really logs: Maxedge dashboard → Signals shows updating values? Yes → the eHawk live-data relay is the problem. No → PLC link or logger — this is not an eHawk issue.

Fix

# on the Maxedge VM
docker ps | grep -E 'maxedge-core|ehawk-agent'
docker logs --tail 100 ehawk-agent
docker restart ehawk-agent
# is the relay socket up?
ss -tlnp | grep 7443

The eHawk live view is fed by the ehawk-agent container relaying from maxedge-core over the tunnel. The agent restarts cleanly and does not affect logging.

Steps

Open the Maxedge dashboard (:8080) through the session. Signals updating → logging is fine, continue. Frozen → follow logger not running.
docker ps: ehawk-agent Up? Not running → docker restart ehawk-agent.
Agent Up but no data → docker logs --tail 100 ehawk-agent. subscription rejected → the signal list in the agent config is stale after a config upload; Dashboard → System → eHawk → Re-sync signals.
Timestamps hours off → clock skew on the VM. timedatectl; NTP goes via the crane firewall — check it is allowed.
Still nothing → tunnel bandwidth. The live view is throttled on links below 256 kbit/s; use Trendviewer export instead.

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