This morning i have realized that FA stopped receiving data from my device, statistics are not updated any longer:
In the log there’s no transfer documented between 06:08 and 06:50, later transfer of data is documented after 07:00, but no data were shown until i rebooted the whole device at 07:30
Since this time it seem to be working again:
Any ideas what caused this?
Dump1090-fa and all the other feeders were running fine all the time.
Well if you wouldn’t have rebooted, you could have checked the system log.
I checked the previous logs and found this for a certain amount of time:
Nov 8 06:35:26 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.156/1200 failed: handshake failed: software caused connection abort
Nov 8 06:35:26 raspberrypi piaware[573]: reconnecting in 50 seconds...
Nov 8 06:36:16 raspberrypi piaware[573]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Nov 8 06:36:16 raspberrypi piaware[573]: Connection with adept server at piaware.flightaware.com/1200 established
Nov 8 06:36:16 raspberrypi piaware[573]: TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: software caused connection abort
Nov 8 06:36:16 raspberrypi piaware[573]: reconnecting in 72 seconds...
Nov 8 06:37:28 raspberrypi piaware[573]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Nov 8 06:37:29 raspberrypi piaware[573]: Connection with adept server at piaware.flightaware.com/1200 established
Nov 8 06:37:29 raspberrypi piaware[573]: TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: software caused connection abort
Nov 8 06:37:29 raspberrypi piaware[573]: reconnecting in 57 seconds...
Nov 8 06:38:26 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.197/1200
Nov 8 06:38:26 raspberrypi piaware[573]: Connection with adept server at 70.42.6.197/1200 established
Nov 8 06:38:26 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.197/1200 failed: handshake failed: software caused connection abort
Nov 8 06:38:26 raspberrypi piaware[573]: reconnecting in 66 seconds...
Nov 8 06:39:00 raspberrypi piaware[573]: 13062759 msgs recv'd from dump1090-fa (608 in last 5m); 13042808 msgs sent to FlightAware
Nov 8 06:39:32 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.224/1200
Nov 8 06:39:32 raspberrypi piaware[573]: Connection with adept server at 70.42.6.224/1200 established
Nov 8 06:39:32 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.224/1200 failed: handshake failed: software caused connection abort
Nov 8 06:39:32 raspberrypi piaware[573]: reconnecting in 52 seconds...
Nov 8 06:40:24 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.156/1200
Nov 8 06:40:24 raspberrypi piaware[573]: Connection with adept server at 70.42.6.156/1200 established
Nov 8 06:40:25 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.156/1200 failed: handshake failed: software caused connection abort
Nov 8 06:40:25 raspberrypi piaware[573]: reconnecting in 66 seconds...
Nov 8 06:41:31 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.225/1200
Nov 8 06:41:31 raspberrypi piaware[573]: Connection with adept server at 70.42.6.225/1200 established
Nov 8 06:41:31 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.225/1200 failed: handshake failed: software caused connection abort
Nov 8 06:41:31 raspberrypi piaware[573]: reconnecting in 70 seconds...
Nov 8 06:42:41 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.191/1200
Nov 8 06:42:41 raspberrypi piaware[573]: Connection with adept server at 70.42.6.191/1200 established
Nov 8 06:42:41 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.191/1200 failed: handshake failed: software caused connection abort
Nov 8 06:42:41 raspberrypi piaware[573]: reconnecting in 59 seconds...
Nov 8 06:43:40 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.198/1200
Nov 8 06:43:40 raspberrypi piaware[573]: Connection to adept server at 70.42.6.198/1200 failed: connection refused
Nov 8 06:43:40 raspberrypi piaware[573]: reconnecting in 49 seconds...
Nov 8 06:44:00 raspberrypi piaware[573]: 13063461 msgs recv'd from dump1090-fa (702 in last 5m); 13042808 msgs sent to FlightAware
Nov 8 06:44:29 raspberrypi piaware[573]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Nov 8 06:44:29 raspberrypi piaware[573]: Connection with adept server at piaware.flightaware.com/1200 established
Nov 8 06:44:30 raspberrypi piaware[573]: TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: software caused connection abort
Nov 8 06:44:30 raspberrypi piaware[573]: reconnecting in 72 seconds...
Nov 8 06:45:42 raspberrypi piaware[573]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Nov 8 06:45:42 raspberrypi piaware[573]: Connection with adept server at piaware.flightaware.com/1200 established
Nov 8 06:45:42 raspberrypi piaware[573]: TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: software caused connection abort
Nov 8 06:45:42 raspberrypi piaware[573]: reconnecting in 54 seconds...
Nov 8 06:46:36 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.225/1200
Nov 8 06:46:36 raspberrypi piaware[573]: Connection with adept server at 70.42.6.225/1200 established
Nov 8 06:46:36 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.225/1200 completed
Nov 8 06:46:36 raspberrypi piaware[573]: FlightAware server certificate validated
Nov 8 06:46:36 raspberrypi piaware[573]: encrypted session established with FlightAware
Nov 8 06:46:51 raspberrypi piaware[573]: Lost connection to adept server at 70.42.6.225/1200: server closed connection
Nov 8 06:46:51 raspberrypi piaware[573]: reconnecting in 55 seconds...
Nov 8 06:47:46 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.156/1200
Nov 8 06:47:46 raspberrypi piaware[573]: Connection with adept server at 70.42.6.156/1200 established
Nov 8 06:47:47 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.156/1200 failed: handshake failed: software caused connection abort
Nov 8 06:47:47 raspberrypi piaware[573]: reconnecting in 62 seconds...
Nov 8 06:48:49 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.197/1200
Nov 8 06:48:49 raspberrypi piaware[573]: Connection with adept server at 70.42.6.197/1200 established
Nov 8 06:48:49 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.197/1200 failed: handshake failed: software caused connection abort
Nov 8 06:48:49 raspberrypi piaware[573]: reconnecting in 49 seconds...
Nov 8 06:49:00 raspberrypi piaware[573]: 13064355 msgs recv'd from dump1090-fa (894 in last 5m); 13042808 msgs sent to FlightAware
Nov 8 06:49:38 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.198/1200
Nov 8 06:49:38 raspberrypi piaware[573]: Connection to adept server at 70.42.6.198/1200 failed: connection refused
Nov 8 06:49:38 raspberrypi piaware[573]: reconnecting in 62 seconds...
Nov 8 06:50:40 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.224/1200
Nov 8 06:50:40 raspberrypi piaware[573]: Connection with adept server at 70.42.6.224/1200 established
Nov 8 06:50:40 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.224/1200 completed
Nov 8 06:50:40 raspberrypi piaware[573]: FlightAware server certificate validated
Nov 8 06:50:41 raspberrypi piaware[573]: encrypted session established with FlightAware
Nov 8 06:50:41 raspberrypi piaware[573]: logged in to FlightAware as user foxhunter
Nov 8 06:50:41 raspberrypi piaware[573]: my feeder ID is <removed<y
Nov 8 06:50:41 raspberrypi piaware[573]: site statistics URL: https://flightaware.com/adsb/stats/user/foxhunter#stats-107325
Wonder what caused this server connect issues
It started somewhere at 06AM
> Nov 8 05:54:12 raspberrypi piaware[573]: NOTICE from adept server: 12% of multilateration messages (UDP) are not reaching the server - check your network?
> Nov 8 05:55:12 raspberrypi piaware[573]: NOTICE from adept server: 10% of multilateration messages (UDP) are not reaching the server - check your network?
> Nov 8 05:59:00 raspberrypi piaware[573]: 13058984 msgs recv'd from dump1090-fa (404 in last 5m); 13041965 msgs sent to FlightAware
> Nov 8 06:04:00 raspberrypi piaware[573]: 13059397 msgs recv'd from dump1090-fa (413 in last 5m); 13042378 msgs sent to FlightAware
> Nov 8 06:08:19 raspberrypi piaware[573]: mlat-client(27619): Receiver status: connected
> Nov 8 06:08:19 raspberrypi piaware[573]: mlat-client(27619): Server status: synchronized with 285 nearby receivers
> Nov 8 06:08:19 raspberrypi piaware[573]: mlat-client(27619): Receiver: 382.4 msg/s received 64.5 msg/s processed (17%)
> Nov 8 06:08:19 raspberrypi piaware[573]: mlat-client(27619): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.8kB/s UDP to server
> Nov 8 06:08:19 raspberrypi piaware[573]: mlat-client(27619): Results: 2.7 positions/minute
> Nov 8 06:08:19 raspberrypi piaware[573]: mlat-client(27619): Aircraft: 0 of 1 Mode S, 20 of 20 ADS-B used
> Nov 8 06:09:00 raspberrypi piaware[573]: 13059813 msgs recv'd from dump1090-fa (416 in last 5m); 13042794 msgs sent to FlightAware
> Nov 8 06:09:10 raspberrypi piaware[573]: timed out waiting for alive message from FlightAware, reconnecting...
> Nov 8 06:09:10 raspberrypi piaware[573]: multilateration data no longer required, disabling mlat client
> Nov 8 06:09:11 raspberrypi piaware[573]: fa-mlat-client exited normally
> Nov 8 06:09:11 raspberrypi piaware[573]: reconnecting in 64 seconds...
> Nov 8 06:09:11 raspberrypi piaware[573]: mlat-client(27619): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
> Nov 8 06:09:11 raspberrypi piaware[573]: mlat-client(27619): Exiting on connection loss
> Nov 8 06:10:15 raspberrypi piaware[573]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
> Nov 8 06:10:45 raspberrypi piaware[573]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
> Nov 8 06:10:45 raspberrypi piaware[573]: reconnecting in 58 seconds...
> Nov 8 06:11:43 raspberrypi piaware[573]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
> Nov 8 06:12:13 raspberrypi piaware[573]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
> Nov 8 06:12:13 raspberrypi piaware[573]: reconnecting in 57 seconds...
> Nov 8 06:13:10 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.191/1200
> Nov 8 06:13:40 raspberrypi piaware[573]: Connection attempt with adept server at 70.42.6.191/1200 timed out
> Nov 8 06:13:40 raspberrypi piaware[573]: reconnecting in 59 seconds...
> Nov 8 06:14:00 raspberrypi piaware[573]: 13060218 msgs recv'd from dump1090-fa (405 in last 5m); 13042808 msgs sent to FlightAware
> Nov 8 06:14:39 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.156/1200
> Nov 8 06:15:09 raspberrypi piaware[573]: Connection attempt with adept server at 70.42.6.156/1200 timed out
> Nov 8 06:15:09 raspberrypi piaware[573]: reconnecting in 62 seconds...
> Nov 8 06:16:11 raspberrypi piaware[573]: Connecting to FlightAware adept server at 70.42.6.225/1200
> Nov 8 06:16:11 raspberrypi piaware[573]: Connection with adept server at 70.42.6.225/1200 established
> Nov 8 06:16:11 raspberrypi piaware[573]: TLS handshake with adept server at 70.42.6.225/1200 failed: handshake failed: software caused connection abort
> Nov 8 06:16:11 raspberrypi piaware[573]: reconnecting in 60 seconds...
Currently it’s working again
Oh they had server issues for around an hour, times in UTC:
Nov 08 05:09:06 pi piaware[555]: timed out waiting for alive message from FlightAware, reconnecting...
Nov 08 05:10:48 pi piaware[555]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Nov 08 05:56:24 pi piaware[555]: encrypted session established with FlightAware
Roughly 0500Z to 0600Z.
Ok, that fits to what i have seen.
Maybe my reboot wasn’t necessary, but it did not hurt 
This was due to a problem during planned network maintenance that caused everything to lose connectivity for a short time; then the adept servers rate-limited new connections to protect themselves from 25k clients all reconnecting at once, so it took a while for everything to reconnect fully. Sorry for the hassle.