How to troubleshoot: multilateration Anomalies

A day or so ago, a new tracker I put up on top of a tall building, out doors (in the cold), had this message in the ads-b page on FA:

This feeder is not being used for multilateration because its timing information appears to be unreliable. This can be caused by the site location being incorrect, or because your Pi is running out of free CPU.

I’ve updated the software, rebooted, CPU load isn’t higher than any other rPi3 that I have running the same software, disk space free, etc. I’m at a loss.

Any suggestions on how to troubleshoot this?

Thanks

Looks OK now:

Multilateration (MLAT): Supported / Enabled (synchronized with 8 nearby receivers)

It is normal for synchronization to occasionally fail (it’s just a hardware limitation), it’s only a real problem if it persists.

Thanks - Seemed like it persisted for a few days but honestly could have been looking at the wrong time.