Yesterday I noticed that my stats page was showing MLAT was down. On my device I saw in the log entries like: “mlat-client(873): Server status: clock unstable”.
Noting the time that entry started appearing I looked at other logs and saw that was when I had installed and set up the motion app in order to use a USB web cam to feed my surveillance system. Disabling that app and restarting the system fixed the issue.
It does not appear to be a CPU usage problem as top showed nothing with high CPU, so I’m thinking either a network port conflict or something in the USB device access. I’m running on a Raspberry Pi 3B.
Has anyone else seen this?