happened to be looking at my adsb site on the website and noticed this
[2019-07-04 05:57 MDT] no ADS-B data program seen listening on port 30978 for 371 seconds, trying to start it…
[2019-07-04 05:57 MDT] attempting to start dump978-fa using ‘systemctl --no-block restart dump978-fa.service < /dev/null’…
[2019-07-04 05:58 MDT] no ADS-B data program seen listening on port 30978 for 10 seconds, next check in 60s
[2019-07-04 05:59 MDT] no ADS-B data program seen listening on port 30978 for 70 seconds, next check in 60s
[2019-07-04 06:00 MDT] no ADS-B data program seen listening on port 30978 for 130 seconds, next check in 60s
[2019-07-04 06:01 MDT] no ADS-B data program seen listening on port 30978 for 191 seconds, next check in 60s
it appears that dump 978 is intermittent for some reason.
here’s the output of piaware-status
pi@piaware:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 377.
PiAware ADS-B client (faup1090) is running with pid 1420.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is running with pid 23430.
Local ADS-B receiver (dump1090-fa) is running with pid 1012.
Local ADS-B UAT receiver (dump978) is not running.
dump1090-fa (pid 1012) is listening for connections on port 30005.
no program appears to be listening for 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.
got ‘couldn’t open socket: connection refused’
dump978 is NOT producing data on localhost:30978.
dump1090 is producing data on localhost:30005.
after a reboot
pi@piaware:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 371.
PiAware ADS-B client (faup1090) is running with pid 519.
PiAware ADS-B UAT client (faup978) is running with pid 528.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-fa) is running with pid 362.
Local ADS-B UAT receiver (dump978-fa) is running with pid 361.
dump1090-fa (pid 362) is listening for connections on port 30005.
dump978-fa (pid 361) is listening for connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
it looks to me like the 978 dongle isn’t working reliably. I didn’t get a screengrab but rtl_test didn’t show the 978 dongle before the reboot, it does now
pi@piaware:~ $ sudo rtl_test
Found 2 device(s):
0: Realtek, RTL2832U, SN: 00001090
1: Realtek, RTL2838UHIDIR, SN: 00000978
Using device 0: Generic RTL2832U
usb_claim_interface error -6
Failed to open rtlsdr device #0.
would you concur that it’s time to replace the 978 dongle?