My MLAT dips significantly every day at 10:30 AM. My regular ADS-b reports seem regular and unassociated. They seem to be a bit erratic at other times, but nothing as regular as the 10:30 AM dip.
Seems to have started doing this a few weeks ago.
Ive changed nothing.
Any ideas?
DRS
This is a “me too” reply. I have only noticed this for the past two days but it may have happened more often. My piaware logs indicates that UDP packets are not being received, e.g.
02/19/2017 21:49:10 1807469 msgs recv'd from dump1090-mutab (2638 in last 5m); 1804403 msgs sent to FlightAware
02/19/2017 21:49:58 NOTICE from adept server: 10% of multilateration messages (UDP) are not reaching the server - check your network?
02/19/2017 21:54:10 1810308 msgs recv'd from dump1090-mutab (2839 in last 5m); 1807242 msgs sent to FlightAware
02/19/2017 21:59:10 1813127 msgs recv'd from dump1090-mutab (2819 in last 5m); 1810061 msgs sent to FlightAware
02/19/2017 22:01:51 mlat-client(12391): Receiver status: connected
02/19/2017 22:01:51 mlat-client(12391): Server status: synchronized with 105 nearby receivers
or
02/19/2017 20:09:10 1750771 msgs recv'd from dump1090-mutab (2951 in last 5m); 1749582 msgs sent to FlightAware
02/19/2017 20:14:10 1753828 msgs recv'd from dump1090-mutab (3057 in last 5m); 1752639 msgs sent to FlightAware
02/19/2017 20:14:49 data isn't making it to FlightAware, reconnecting...
02/19/2017 20:14:49 multilateration data no longer required, disabling mlat client
02/19/2017 20:14:50 fa-mlat-client exited normally.
02/19/2017 20:14:50 reconnecting in 57 seconds...
02/19/2017 20:14:50 mlat-client(16131): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
02/19/2017 20:14:50 mlat-client(16131): Exiting on connection loss
02/19/2017 20:14:52 TLS error:
02/19/2017 20:15:47 Connecting to FlightAware adept server at piaware.flightaware.com/1200
02/19/2017 20:15:47 Connection with adept server at piaware.flightaware.com/1200 established
02/19/2017 20:15:48 TLS handshake with adept server at piaware.flightaware.com/1200 completed
02/19/2017 20:15:48 FlightAware server certificate validated
02/19/2017 20:15:48 encrypted session established with FlightAware
02/19/2017 20:15:49 logged in to FlightAware as user tdrane
02/19/2017 20:15:49 multilateration data requested
02/19/2017 20:15:49 Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --udp-transport 70.4
2.6.197:6857:4227747785
02/19/2017 20:15:49 mlat-client(11201): fa-mlat-client 0.2.6 starting up
02/19/2017 20:15:49 mlat-client(11201): Using UDP transport to 70.42.6.197 port 6857
02/19/2017 20:15:49 mlat-client(11201): Input connected to localhost:30005
02/19/2017 20:15:49 mlat-client(11201): Input format changed to BEAST, 12MHz clock
02/19/2017 20:15:50 mlat-client(11201): Beast-format results connection with 127.0.0.1:30104: connection established
02/19/2017 20:19:10 1756769 msgs recv'd from dump1090-mutab (2941 in last 5m); 1754986 msgs sent to FlightAware
02/19/2017 20:24:10 1759666 msgs recv'd from dump1090-mutab (2897 in last 5m); 1757883 msgs sent to FlightAware
02/19/2017 20:29:10 1762628 msgs recv'd from dump1090-mutab (2962 in last 5m); 1760845 msgs sent to FlightAware
02/19/2017 20:30:49 mlat-client(11201): Receiver status: connected
02/19/2017 20:30:49 mlat-client(11201): Server status: synchronized with 108 nearby receivers
Other times the log shows that 100% of UDP packets are not reaching the server.
I have checked nearby feeders that do not show any anomaly with their mlat graphs so I would think the issue is a local one. That said, my ads-b data is flowing normally to Flightaware and my feed to flightradar24 shows no interruption.
While it may be totally coincidental and unrelated, I notice that my statistics update more slowly than nearby feeders. At 00:00 UTC others start accumulating counts for the new day whereas it is often 01:00 or later that my statistics for the new day are displayed. One would think that at least couple of nearby feeders would exhibit the same issues but I have not seen this occur. Is there an issue with the server at 70.42.6.197?
TD
When is “10:30AM local” in UTC?
My dips are actually 11:00 AM (I was reading the scale wrong! LOL) Im -5 UTC