I’m running the latest version of piaware. It seems that, around midnight it stopped being able to communicate with FlightAware and could never reconnect on its own. SSH accepted username and password but could never start a shell, which made me believe that the system could have run out of memory, but I had no other way to check. Once I rebooted the raspberry pi, everything started working fine again.
When the problem started, the piaware log was showing:
Dec 31 04:58:08 piaware piaware[478]: mlat-client(17885): Receiver status: connected
Dec 31 04:58:08 piaware piaware[478]: mlat-client(17885): Server status: synchronized with 69 nearby receivers
Dec 31 04:58:08 piaware piaware[478]: mlat-client(17885): Receiver: 22.3 msg/s received 8.6 msg/s processed (39%)
Dec 31 04:58:08 piaware piaware[478]: mlat-client(17885): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
Dec 31 04:58:08 piaware piaware[478]: mlat-client(17885): Results: 28.5 positions/minute
Dec 31 04:58:08 piaware piaware[478]: mlat-client(17885): Aircraft: 1 of 6 Mode S, 3 of 3 ADS-B used
Dec 31 04:58:36 piaware piaware[478]: 130244 msgs recv'd from dump1090-fa (137 in last 5m); 130088 msgs sent to FlightAware
Dec 31 05:03:36 piaware piaware[478]: 130384 msgs recv'd from dump1090-fa (140 in last 5m); 130228 msgs sent to FlightAware
Dec 31 05:04:50 piaware piaware[478]: timed out waiting for alive message from FlightAware, reconnecting...
Dec 31 05:04:50 piaware piaware[478]: multilateration data no longer required, disabling mlat client
Dec 31 05:04:51 piaware piaware[478]: fa-mlat-client exited normally
Dec 31 05:04:51 piaware piaware[478]: reconnecting in 52 seconds...
And piaware kept retrying every minute or so, until I restarted the raspberry pi.
Has anyone seen something similar? I’m not sure I can reproduce the problem at will, but will keep an eye and do more troubleshooting if it happens again.
Thanks,
Flavio