I dug the piaware.log and found this at the time the 978 messages stop (near 11:00 AM on the 24th):
Dec 24 10:59:46 piaware2 piaware[27328]: no new messages received in 3889 seconds, it might just be that there haven't been any aircraft nearby but I'm going to try to restart everything, just in case...
Dec 24 10:59:47 piaware2 piaware[27328]: faup978 exited with SIG SIGHUP
Dec 24 10:59:47 piaware2 piaware[27328]: attempting to restart dump978..
Dec 24 10:59:47 piaware2 piaware[27328]: attempting to restart dump978-fa using 'systemctl --no-block try-restart dump978-fa.service < /dev/null'...
Dec 24 10:59:47 piaware2 piaware[27328]: dump978 restart appears to have been successful
Dec 24 10:59:57 piaware2 piaware[27328]: ADS-B data program 'dump978-fa' is listening on port 30978, so far so good
Dec 24 10:59:57 piaware2 piaware[27328]: Starting faup978: /usr/lib/piaware/helpers/faup978 --connect localhost:30978
Dec 24 10:59:57 piaware2 piaware[27328]: Started faup978 (pid 10872) to connect to dump978-fa
Dec 24 10:59:57 piaware2 piaware[27328]: faup978(10872): Connecting to localhost:30978
Dec 24 10:59:57 piaware2 piaware[27328]: faup978(10872): Connected to [::1]:30978
Dec 24 11:00:00 piaware2 piaware[27328]: faup978(10872): Connection failed: End of file
Dec 24 11:00:00 piaware2 piaware[27328]: lost connection to dump978-fa via faup978
Dec 24 11:00:00 piaware2 piaware[27328]: faup978 exited normally
Dec 24 11:00:00 piaware2 piaware[27328]: will reconnect to dump978-fa in 30 seconds
these type of messages repeat over and over.
I ran piaware-status and I see this:
pi@piaware2:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 25922.
PiAware ADS-B client (faup1090) is running with pid 25981.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is running with pid 25978.
Local ADS-B receiver (dump1090-fa) is running with pid 570.
Local ADS-B UAT receiver (dump978-fa) is running with pid 20013.
dump1090-fa (pid 570) is listening for ES connections on port 30005.
dump978-fa (pid 20013) is listening for UAT connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
dump978 is producing data on localhost:30978.
dump1090 is producing data on localhost:30005.
Your feeder ID is 6xxxxxxxxxxxxxxxxxxx3 (configured at /etc/piaware.conf:9)
pi@piaware2:~ $
Dec 27 21:40:06 piaware2 systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
Dec 27 21:40:06 piaware2 systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
Dec 27 21:40:36 piaware2 systemd[1]: dump978-fa.service: Service RestartSec=30s expired, scheduling restart.
Dec 27 21:40:36 piaware2 systemd[1]: dump978-fa.service: Scheduled restart job, restart counter is at 7833.
Dec 27 21:40:36 piaware2 systemd[1]: Stopped dump978 ADS-B UAT receiver.
Dec 27 21:40:36 piaware2 systemd[1]: Started dump978 ADS-B UAT receiver.
Dec 27 21:40:36 piaware2 dump978-fa[11768]: raw-port: listening for connections on 0.0.0.0:30978
Dec 27 21:40:36 piaware2 dump978-fa[11768]: raw-port: listening for connections on [::]:30978
Dec 27 21:40:36 piaware2 dump978-fa[11768]: json-port: listening for connections on 0.0.0.0:30979
Dec 27 21:40:36 piaware2 dump978-fa[11768]: json-port: listening for connections on [::]:30979
Dec 27 21:40:36 piaware2 dump978-fa[11768]: Detached kernel driver
Dec 27 21:40:37 piaware2 dump978-fa[11768]: Found Rafael Micro R820T tuner
Dec 27 21:40:37 piaware2 dump978-fa[11768]: Reattached kernel driver
Dec 27 21:40:37 piaware2 dump978-fa[11768]: usb_claim_interface error -6
Dec 27 21:40:37 piaware2 dump978-fa[11768]: Detached kernel driver
Dec 27 21:40:37 piaware2 dump978-fa[11768]: Found Rafael Micro R820T tuner
Dec 27 21:40:38 piaware2 dump978-fa[11768]: Exact sample rate is: 2083333.135571 Hz
Dec 27 21:40:38 piaware2 dump978-fa[11768]: [R82XX] PLL not locked!
Dec 27 21:40:38 piaware2 dump978-fa[11768]: SoapySDR: using maximum manual gain 49.6 dB
Dec 27 21:40:38 piaware2 dump978-fa[11768]: SoapySDR: using stream setting buffsize=262144
Dec 27 21:40:38 piaware2 dump978-fa[11768]: Allocating 15 zero-copy buffers
Dec 27 21:40:43 piaware2 dump978-fa[11768]: Message source reports error: TIMEOUT
Dec 27 21:40:44 piaware2 dump978-fa[11768]: Reattached kernel driver
Dec 27 21:40:44 piaware2 dump978-fa[11768]: Abnormal exit
Dec 27 21:40:44 piaware2 systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
Dec 27 21:40:44 piaware2 systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
Dec 27 21:41:14 piaware2 systemd[1]: dump978-fa.service: Service RestartSec=30s expired, scheduling restart.
Dec 27 21:41:14 piaware2 systemd[1]: dump978-fa.service: Scheduled restart job, restart counter is at 7834.
Dec 27 21:41:14 piaware2 systemd[1]: Stopped dump978 ADS-B UAT receiver.
Dec 27 21:41:14 piaware2 systemd[1]: Started dump978 ADS-B UAT receiver.
Dec 27 21:41:14 piaware2 dump978-fa[12287]: raw-port: listening for connections on 0.0.0.0:30978
Dec 27 21:41:14 piaware2 dump978-fa[12287]: raw-port: listening for connections on [::]:30978
Dec 27 21:41:14 piaware2 dump978-fa[12287]: json-port: listening for connections on 0.0.0.0:30979
Dec 27 21:41:14 piaware2 dump978-fa[12287]: json-port: listening for connections on [::]:30979
Dec 27 21:41:15 piaware2 dump978-fa[12287]: Detached kernel driver
Dec 27 21:41:15 piaware2 dump978-fa[12287]: Found Rafael Micro R820T tuner
Dec 27 21:41:15 piaware2 dump978-fa[12287]: Reattached kernel driver
Dec 27 21:41:15 piaware2 dump978-fa[12287]: usb_claim_interface error -6
Dec 27 21:41:15 piaware2 dump978-fa[12287]: Detached kernel driver
Dec 27 21:41:15 piaware2 dump978-fa[12287]: Found Rafael Micro R820T tuner
Dec 27 21:41:16 piaware2 dump978-fa[12287]: Exact sample rate is: 2083333.135571 Hz
Dec 27 21:41:16 piaware2 dump978-fa[12287]: [R82XX] PLL not locked!
Dec 27 21:41:16 piaware2 dump978-fa[12287]: SoapySDR: using maximum manual gain 49.6 dB
Dec 27 21:41:16 piaware2 dump978-fa[12287]: SoapySDR: using stream setting buffsize=262144
Dec 27 21:41:16 piaware2 dump978-fa[12287]: Allocating 15 zero-copy buffers
Dec 27 21:41:17 piaware2 dump978-fa[12287]: [::]:30978: accepted a connection from [::1]:55592
Dec 27 21:41:17 piaware2 dump978-fa[12287]: [::]:30978: accepted a connection from [::1]:55594
Dec 27 21:41:21 piaware2 dump978-fa[12287]: Message source reports error: TIMEOUT
Dec 27 21:41:22 piaware2 dump978-fa[12287]: Reattached kernel driver
Dec 27 21:41:22 piaware2 dump978-fa[12287]: Abnormal exit
Dec 27 21:41:22 piaware2 systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
Dec 27 21:41:22 piaware2 systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
This usually means a hardware problem, the dongle has got wedged and is no longer streaming data.
In my experience there’s not a lot that can be done beyond power-cycling the dongle (which happens on reboot) to reset it. If you wanted to avoid a full reboot, GitHub - mvp/uhubctl: uhubctl - USB hub per-port power control can be used to power-cycle the USB ports.
I’m experiencing something similar right now. I updated both my 978 &1090 receivers a day or so after Christmas to FA 8.2.
The 1090 is rock solid. The 978 radio went cold and dark a few days later, and hasn’t functioned since. The 978 RPi is OK, but the orange radio seems dead.
It probably wouldn’t be a big deal, but I’d already had an orange radio failure within 45 days of setting up the 978 back in September.
Is this a common failure? Both receivers are right next to each other, so if conditions were the issue, I’d expect the 1090 radio to show a similar issue.
