Everything looks to be working fine, but I am noticing that after some time, I no longer get new messages from dump1090-fa
Logs from piaware:
Oct 22 18:25:34 raspberrypi piaware[496]: 676 msgs recv'd from dump1090-fa (0 in last 5m); 654 msgs sent to FlightAware
Oct 22 18:30:34 raspberrypi piaware[496]: 676 msgs recv'd from dump1090-fa (0 in last 5m); 654 msgs sent to FlightAware
Oct 22 18:35:34 raspberrypi piaware[496]: 676 msgs recv'd from dump1090-fa (0 in last 5m); 654 msgs sent to FlightAware
Oct 22 18:36:19 raspberrypi piaware[496]: mlat-client(684): Receiver status: connected
Oct 22 18:36:19 raspberrypi piaware[496]: mlat-client(684): Server status: not synchronized with any nearby receivers
Oct 22 18:36:19 raspberrypi piaware[496]: mlat-client(684): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)
Oct 22 18:36:19 raspberrypi piaware[496]: mlat-client(684): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
Oct 22 18:36:19 raspberrypi piaware[496]: mlat-client(684): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
Oct 22 18:40:34 raspberrypi piaware[496]: 676 msgs recv'd from dump1090-fa (0 in last 5m); 654 msgs sent to FlightAware
Oct 22 18:45:34 raspberrypi piaware[496]: 676 msgs recv'd from dump1090-fa (0 in last 5m); 654 msgs sent to FlightAware
If I reboot the raspberry pi, everything boots up correctly and I can get data again.
In addition to this, I am also running fr24feed, which is hooked to dump1090-fa on beast-tcp on 127.0.0.1:30005.
During that time, even fr24feed cannot receive data from dump1090-fa
2018-10-22 20:35:36 | [reader][w]Global timeout exceeded, 0 msgs, 0 resyncs, reconnecting
2018-10-22 20:35:36 | [reader][i]Connection terminated
2018-10-22 20:35:37 | [mlat][i]No ADS-B time reference available (0/0)
2018-10-22 20:35:37 | [mlat][i]Pinging the server
2018-10-22 20:35:37 | [mlat][i]Stats 4810/0
2018-10-22 20:35:41 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2018-10-22 20:35:41 | [reader][i]Connected to the receiver, configuring
2018-10-22 20:35:41 | [reader][i]Configured, processing messages
2018-10-22 20:35:43 | [feed][n]ping 102
2018-10-22 20:35:44 | [feed][n]syncing stream result: 1
2018-10-22 20:35:48 | [mlat][i]No ADS-B time reference available (0/0)
2018-10-22 20:35:57 | [mlat][i]No ADS-B time reference available (0/0)
2018-10-22 20:35:57 | [mlat][i]Pinging the server
2018-10-22 20:35:57 | [mlat][i]Stats 4810/0
2018-10-22 20:36:07 | [mlat][i]No ADS-B time reference available (0/0)
2018-10-22 20:36:13 | [feed][n]ping 103
2018-10-22 20:36:14 | [feed][n]syncing stream result: 1
2018-10-22 20:36:17 | [mlat][i]No ADS-B time reference available (0/0)
2018-10-22 20:36:17 | [mlat][i]Pinging the server
2018-10-22 20:36:17 | [mlat][i]Stats 4810/0
2018-10-22 20:36:28 | [mlat][i]No ADS-B time reference available (0/0)
2018-10-22 20:36:37 | [mlat][i]No ADS-B time reference available (0/0)
2018-10-22 20:36:37 | [mlat][i]Pinging the server
2018-10-22 20:36:37 | [mlat][i]Stats 4810/0
2018-10-22 20:36:43 | [feed][n]ping 104
2018-10-22 20:36:44 | [feed][n]syncing stream result: 1
2018-10-22 20:36:47 | [mlat][i]No ADS-B time reference available (0/0)
I can see that the process is still running and listening on those ports. I can even telnet to it and it accepts my connection.
I am using an official RPi power supply & micro-sd cable.
When I run journalctl -t dump1090-fa I get:
Oct 22 22:09:21 raspberrypi dump1090-fa[502]: Mon Oct 22 22:09:21 2018 UTC No data received from the SDR for a long time, it may have wedged
Oct 22 22:10:21 raspberrypi dump1090-fa[502]: Mon Oct 22 22:10:21 2018 UTC No data received from the SDR for a long time, it may have wedged
Oct 22 22:11:21 raspberrypi dump1090-fa[502]: Mon Oct 22 22:11:21 2018 UTC No data received from the SDR for a long time, it may have wedged
Oct 22 22:12:21 raspberrypi dump1090-fa[502]: Mon Oct 22 22:12:21 2018 UTC No data received from the SDR for a long time, it may have wedged
Oct 22 22:13:22 raspberrypi dump1090-fa[502]: Mon Oct 22 22:13:22 2018 UTC No data received from the SDR for a long time, it may have wedged
When I turn off dump1090-fa and run rtl_test -t I get:
pi@raspberrypi:~/adsb-exchange $ rtl_test -t
Found 1 device(s):
0: Realtek, RTL2832U, SN: 00001000
Using device 0: Generic RTL2832U
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.
No E4000 tuner found, aborting.
Another thing that I noticed is that when I try to turn off dump1090-fa with sudo systemctl stop dump1090-fa it never goes down gracefully. I have to kill -9 it
Strangely enough, when I turn on sudo systemctl start dump1090-fa again it starts working
If you want a bandaid that will automatically restart dump1090-fa you can try the following script:
#!/bin/bash
exec &>>/tmp/wedge
sleep 20
journalctl -b -0 -f -n0 | grep 'No data received from the SDR for a long time' --line-buffered | {
while read line
do
date
systemctl kill -s 9 dump1090-fa
sleep .3
systemctl restart dump1090-fa
done
}
First you open a new textfile with an editor, paste the above script, save and exit