Piaware dies

Hello everyone,

Since last night suddenly the PiAware process on my Raspberry dies randomly. I can’t figure out what’s the issue.

The piaware.log file shows just this:

Aug 27 12:06:38 ads-b piaware[5135]: mlat-client(5175): Receiver status: connected
Aug 27 12:06:38 ads-b piaware[5135]: mlat-client(5175): Server status: clock unstable
Aug 27 12:06:38 ads-b piaware[5135]: mlat-client(5175): Receiver: 405.9 msg/s received 68.5 msg/s processed (17%)
Aug 27 12:06:38 ads-b piaware[5135]: mlat-client(5175): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.9kB/s UDP to server
Aug 27 12:06:38 ads-b piaware[5135]: mlat-client(5175): Aircraft: 10 of 21 Mode S, 29 of 34 ADS-B used
Aug 27 12:07:02 ads-b piaware[5135]: 41746 msgs recv’d from dump1090-fa (803 in last 5m); 41746 msgs sent to FlightAware
Aug 27 13:27:10 ads-b piaware[1176]: creating pidfile /run/piaware/piaware.pid
Aug 27 13:27:10 ads-b piaware[1176]: ****************************************************
Aug 27 13:27:10 ads-b piaware[1176]: piaware version 3.8.1 is running, process ID 1176
Aug 27 13:27:10 ads-b piaware[1176]: your system info is: Linux ads-b 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux
Aug 27 13:27:12 ads-b piaware[1176]: Connecting to FlightAware adept server at
Aug 27 13:27:12 ads-b piaware[1176]: Connection with adept server at
Aug 27 13:27:12 ads-b piaware[1176]: TLS handshake with adept server at completed

So, no reason given why in this log snippet the process dies at around 12:06…
How to continue my investigation?

You mean the gap between 12:07 and 13:27?

What is syslog telling you at this time? There should be more documented

What does syslog say?

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.