I followed the instructions and compiled dump1090 and piaware on StretchARM64 on an Odroid N2. Feeds like a charm, except it appears that the log-files are not created for airspy_adsb, dump1090. It is created for piaware.
When I reboot the N2 everything looks normal, but after a brief period of time I see this:
root@odroid-stretch64 : ~ # systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-07-08 15:31:42 PDT; 1 day 4h ago
Main PID: 2158 (dump1090-fa)
Tasks: 1 (limit: 4915)
└─2158 /usr/bin/dump1090-fa --net-only --max-range 360 --net --net-heartbeat 60 --net-ro-size 1000 --net-ro-interval 1 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 1 --lat 37.53022 --lon -122.29481 --write-json /run/dump1090-fa --quiet
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
root@odroid-stretch64 : ~ # journalctl -eu dump1090
– No entries –
root@odroid-stretch64 : ~ #
Similarly, for airspy_adsb I get no love. piaware actually does give some more accurate but is not clear where it gets its input from, like this (emphasis added):
Jul 09 19:19:05 odroid-stretch64 piaware: 2153006 msgs recv’d from unknown process (4003 in last 5m); 2147260 msgs sent to FlightAware
Is there some setting I need to change?