Numerous lost connections

After some time of reliable 24/7 operation my piaware is starting to give some issues with lost connections.

In an effort to narrow it down I renewed the piaware.log file. Over a 5 hour period it has not stopped displaying aircraft but a search on the word ‘lost’ shows the following;

Jul 8 18:59:40 PiAware-26 piaware[485]: mlat-client(664): Beast-format results connection with ::1:30104: connection lost
Jul 8 18:59:40 PiAware-26 piaware[485]: lost connection to dump1090-fa via faup1090
Jul 8 19:00:10 PiAware-26 piaware[485]: mlat-client(664): Connection to localhost:30005 lost: [Errno 111] Connection refused
Jul 8 19:59:41 PiAware-26 piaware[485]: mlat-client(664): Beast-format results connection with ::1:30104: connection lost
Jul 8 19:59:41 PiAware-26 piaware[485]: lost connection to dump1090-fa via faup1090
Jul 8 20:00:11 PiAware-26 piaware[485]: mlat-client(664): Connection to localhost:30005 lost: [Errno 111] Connection refused
Jul 8 21:01:38 PiAware-26 piaware[487]: mlat-client(799): Beast-format results connection with ::1:30104: connection lost
Jul 8 21:01:38 PiAware-26 piaware[487]: lost connection to dump1090-fa via faup1090
Jul 8 21:02:08 PiAware-26 piaware[487]: mlat-client(799): Connection to localhost:30005 lost: [Errno 111] Connection refused
Jul 8 21:02:09 PiAware-26 piaware[487]: mlat-client(799): Connection to localhost:30005 lost: [Errno 111] Connection refused

Sometimes it will just lose connections, cannot ping, ssh and no local display.

Running on a Pi Zero W - power consumption around 450mA and using buster 32 bit

I have tried an alternative PSU but as mentioned, very low current draw.

Any suggestions what I might look for in log file for more info?

Geoff

I used to get that with my older v4.0 SD card PiAware. It would still be reporting aircraft to FlightAware, but the local services – map, SSH – would no longer respond. In all those cases I was able to reboot the Pi using the cogwheel menu on the logged-in FlightAware stats page.

reboot piaware

I was never able to track down the cause. It’s not happened since I reimaged to v8.2.

Maybe your SD card is nearing its end of life. You could reimage and setup your station with a new card. This will give you also the possibility to upgrade your OS to Bullseye, the newest one, Bookworm isn’t completely compatible yet (MLAT issues).
That way you will have an easier upgrade path later on instead of doing it twice when upgrading from Buster

1 Like

It is a well used card and I shall most liked burn a new microSD, currently it seems to be working OK but any more let downs and bulls eye it is :sunglasses:

Geoff