I’m a ZeroW user. Nil else installed. 20% increase in CPU from 60 to 80% total. Runs remote from battery and solar power, so could do to reduce that before next winter! I’ve tried the --no-df-fix option in Decoder Options in /etc/default/dump1090-fa as suggested. But it gives a blank map in SkyAware and an error message of decoder not working in tar1090. So I guess I must be doing something wrong! An idiots guide as to exactly how to implement the --no-df-fix would be very much appreciated. Thanks
Try like this:
# dump1090-fa won't automatically start unless ENABLED=yes
ENABLED=yes
RECEIVER_OPTIONS="--device-index 0 --gain 43.9 --ppm 0"
DECODER_OPTIONS="--max-range 360 --fix --no-fix-df"
NET_OPTIONS="--net --net-heartbeat 60 --net-ro-size 1300 --net-ro-interval 0.2 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005"
JSON_OPTIONS="--json-location-accuracy 1"
# Use a machine-specific wisdom file if it exists
if [ -f /etc/dump1090-fa/wisdom.local ]
then
RECEIVER_OPTIONS="${RECEIVER_OPTIONS} --wisdom /etc/dump1090-fa/wisdom.local"
fi
edit: fixed --no-fix-df … was backwards.
Reducing the gain will also help reduce CPU usage.
Thanks for such prompt help. That is what I had tried previously. I’ve just tried it again exactly as above cut and pasted, and it doesn’t work I’m afraid. I get a error in tar1090 saying
“Problem fetching data from the server:
Seems the decoder / receiver / backend isn’t working correctly!”
and SkyAware just has a blank map with no aircraft but no error message.
Thanks for trying anyway.
Check how to get the log for dump1090-fa:
Debug commands · wiedehopf/adsb-wiki Wiki · GitHub
Put it on pastebin.com or something similar and link it.
This is not an piaware sd-card image install is it?
(prompt would be pi@piaware instead of pi@raspberrypi)
Thanks for taking time to help. It’s much appreciated.
ps. it’s not a piaware image install.
EDIT FOUND IT !
should be --no-fix-df NOT --no-df-fix
All working well now. Will recheck CPU usage after a little while.
Thanks
pps to mods. May be worth changing intial posting in this thread as it may mislead!
1 Like
Just an update. CPU usage only minimally reduced by implementing --no-fix-df setting. ADSB CPU usage dropped from 55% to 52%. Using v4 it was 35%. So my poor PiZeroW is still having work very hard and using lots of battery!
I’m not really seeing any improvement in messages/range or anything else either. So not a great update from my perspective.
Stupidly I didn’t have a backup of the v4 version, which is entirely my own fault! But I’m wondering if I can roll back to v4 dump1090 somehow?
1 Like
You could try the dev version, it has some further tweaks to reduce the CPU use when --no-fix-df is in use.
If you want to downgrade, the old package is here: dump1090-fa 4.0 package (it may not stay there forever)
Thank you for your help.
How can we try the dev version?
You will have to build and install dump1090-fa using source code of it’s development branch.
sudo apt install -y git build-essential debhelper pkg-config dh-systemd
sudo apt install -y librtlsdr-dev libncurses5-dev lighttpd
sudo apt install -y libbladerf-dev libhackrf-dev liblimesuite-dev
git clone --branch dev https://github.com/flightaware/dump1090
cd dump1090
sudo dpkg-buildpackage -b --no-sign
cd ../
sudo dpkg -i dump1090-fa_*.deb
Machine: Raspberry PI Model 4
OS-1: 32-bit Kali Linux 2021 armv7l
OS-2: 64-bit Kali LInux 2020 aarch64
Successfully built & installed
(1) dump1090-fa v5.1~dev
(2) Piaware v5.0
Automated install scrips used:
(1) dump1090-fa
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/install-dump1090-fa.sh)"
(2) piaware
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/install-piaware.sh)"
Hi,
given that I am a new user, following the instructions on the site I struggled to find a Raspberry PI 3 B + and yesterday I downloaded and installed the PiAware 5.0 software.
I had no major problems configuring everything except the coordinates of the Location which are wrong.
I tried to edit them from the control panel page but the Edit Location and Configure Height buttons are not visible even using different browsers.
I tried to enter the coordinates in the config.js file but the coordinates remain wrong for about 30 km.
How can I solve this issue?
Thanks
1 Like
Yes, me too.
ADS-B CPU Utilization went from average of about 30% to 44% right after 5.0 upgrade. Overall CPU Utilization jumped by about 5%.
Hello,
After the update my feeder stopped working. LOG and pic below
Any advices?
Thnk you!
[2021-03-30 18:08 EEST] 1232516 msgs recv’d from dump1090-fa (64 in last 5m); 1223173 msgs sent to FlightAware
[2021-03-30 18:11 EEST] mlat-client(13039): Aircraft: 2 of 2 Mode S, 2 of 2 ADS-B used
[2021-03-30 18:11 EEST] mlat-client(13039): Receiver status: connected
[2021-03-30 18:11 EEST] mlat-client(13039): Receiver: 13.9 msg/s received 4.2 msg/s processed (30%)
[2021-03-30 18:11 EEST] mlat-client(13039): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2021-03-30 18:11 EEST] mlat-client(13039): Server status: synchronized with 6 nearby receivers
[2021-03-30 18:13 EEST] 1232565 msgs recv’d from dump1090-fa (49 in last 5m); 1223222 msgs sent to FlightAware
[2021-03-30 18:18 EEST] 1232647 msgs recv’d from dump1090-fa (82 in last 5m); 1223304 msgs sent to FlightAware
[2021-03-30 18:23 EEST] 1232760 msgs recv’d from dump1090-fa (113 in last 5m); 1223417 msgs sent to FlightAware
[2021-03-30 18:26 EEST] mlat-client(13039): Receiver: 7.2 msg/s received 4.4 msg/s processed (61%)
[2021-03-30 18:26 EEST] mlat-client(13039): Receiver status: connected
[2021-03-30 18:26 EEST] mlat-client(13039): Server status: synchronized with 38 nearby receivers
[2021-03-30 18:26 EEST] mlat-client(13039): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2021-03-30 18:26 EEST] mlat-client(13039): Results: 5.8 positions/minute
[2021-03-30 18:26 EEST] mlat-client(13039): Aircraft: 3 of 3 Mode S, 2 of 2 ADS-B used
[2021-03-30 18:28 EEST] 1232864 msgs recv’d from dump1090-fa (104 in last 5m); 1223521 msgs sent to FlightAware
[2021-03-30 18:33 EEST] 1232963 msgs recv’d from dump1090-fa (99 in last 5m); 1223620 msgs sent to FlightAware
[2021-03-30 18:38 EEST] 1233014 msgs recv’d from dump1090-fa (51 in last 5m); 1223671 msgs sent to FlightAware
[2021-03-30 18:41 EEST] mlat-client(13039): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
[2021-03-30 18:41 EEST] mlat-client(13039): Server status: synchronized with 14 nearby receivers
[2021-03-30 18:41 EEST] mlat-client(13039): Receiver status: connected
[2021-03-30 18:41 EEST] mlat-client(13039): Receiver: 6.8 msg/s received 3.2 msg/s processed (47%)
[2021-03-30 18:41 EEST] mlat-client(13039): Aircraft: 2 of 2 Mode S, 1 of 1 ADS-B used
[2021-03-30 18:43 EEST] 1233045 msgs recv’d from dump1090-fa (31 in last 5m); 1223702 msgs sent to FlightAware
[2021-03-30 18:48 EEST] 1233067 msgs recv’d from dump1090-fa (22 in last 5m); 1223724 msgs sent to FlightAware
[2021-03-30 18:53 EEST] 1233085 msgs recv’d from dump1090-fa (18 in last 5m); 1223742 msgs sent to FlightAware
[2021-03-30 18:56 EEST] mlat-client(13039): Aircraft: 1 of 1 Mode S, 1 of 1 ADS-B used
[2021-03-30 18:56 EEST] mlat-client(13039): Server status: synchronized with 6 nearby receivers
[2021-03-30 18:56 EEST] mlat-client(13039): Results: 1.3 positions/minute
[2021-03-30 18:56 EEST] mlat-client(13039): Receiver status: connected
[2021-03-30 18:56 EEST] mlat-client(13039): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
[2021-03-30 18:56 EEST] mlat-client(13039): Receiver: 3.5 msg/s received 2.0 msg/s processed (58%)
[2021-03-30 18:58 EEST] 1233119 msgs recv’d from dump1090-fa (34 in last 5m); 1223776 msgs sent to FlightAware
[2021-03-30 19:03 EEST] 1233178 msgs recv’d from dump1090-fa (59 in last 5m); 1223835 msgs sent to FlightAware
[2021-03-30 19:08 EEST] 1233265 msgs recv’d from dump1090-fa (87 in last 5m); 1223922 msgs sent to FlightAware
[2021-03-30 19:11 EEST] mlat-client(13039): Receiver: 7.1 msg/s received 3.5 msg/s processed (49%)
[2021-03-30 19:11 EEST] mlat-client(13039): Aircraft: 1 of 1 Mode S, 2 of 2 ADS-B used
[2021-03-30 19:11 EEST] mlat-client(13039): Receiver status: connected
[2021-03-30 19:11 EEST] mlat-client(13039): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
[2021-03-30 19:11 EEST] mlat-client(13039): Server status: clock unstable
[2021-03-30 19:13 EEST] 1233326 msgs recv’d from dump1090-fa (61 in last 5m); 1223983 msgs sent to FlightAware
[2021-03-30 19:18 EEST] 1233387 msgs recv’d from dump1090-fa (61 in last 5m); 1224044 msgs sent to FlightAware
[2021-03-30 19:23 EEST] 1233432 msgs recv’d from dump1090-fa (45 in last 5m); 1224089 msgs sent to FlightAware
[2021-03-30 19:26 EEST] mlat-client(13039): Server status: synchronized with 7 nearby receivers
[2021-03-30 19:26 EEST] mlat-client(13039): Aircraft: 3 of 3 Mode S, 1 of 1 ADS-B used
[2021-03-30 19:26 EEST] mlat-client(13039): Receiver status: connected
[2021-03-30 19:26 EEST] mlat-client(13039): Results: 2.8 positions/minute
[2021-03-30 19:26 EEST] mlat-client(13039): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2021-03-30 19:26 EEST] mlat-client(13039): Receiver: 6.5 msg/s received 3.5 msg/s processed (54%)
[2021-03-30 19:28 EEST] 1233468 msgs recv’d from dump1090-fa (36 in last 5m); 1224125 msgs sent to FlightAware
[2021-03-30 19:33 EEST] 1233497 msgs recv’d from dump1090-fa (29 in last 5m); 1224154 msgs sent to FlightAware
[2021-03-30 19:38 EEST] 1233523 msgs recv’d from dump1090-fa (26 in last 5m); 1224180 msgs sent to FlightAware
[2021-03-30 19:41 EEST] mlat-client(13039): Receiver status: connected
[2021-03-30 19:41 EEST] mlat-client(13039): Results: 5.4 positions/minute
[2021-03-30 19:41 EEST] mlat-client(13039): Receiver: 3.5 msg/s received 3.0 msg/s processed (85%)
[2021-03-30 19:41 EEST] mlat-client(13039): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2021-03-30 19:41 EEST] mlat-client(13039): Aircraft: 2 of 2 Mode S, 0 of 0 ADS-B used
[2021-03-30 19:41 EEST] mlat-client(13039): Server status: not synchronized with any nearby receivers
[2021-03-30 19:43 EEST] 1233552 msgs recv’d from dump1090-fa (29 in last 5m); 1224209 msgs sent to FlightAware
[2021-03-30 19:48 EEST] 1233590 msgs recv’d from dump1090-fa (38 in last 5m); 1224247 msgs sent to FlightAware
[2021-03-30 19:53 EEST] 1233630 msgs recv’d from dump1090-fa (40 in last 5m); 1224287 msgs sent to FlightAware
[2021-03-30 19:56 EEST] mlat-client(13039): Aircraft: 2 of 2 Mode S, 2 of 2 ADS-B used
[2021-03-30 19:56 EEST] mlat-client(13039): Receiver: 2.2 msg/s received 1.1 msg/s processed (50%)
[2021-03-30 19:56 EEST] mlat-client(13039): Receiver status: connected
[2021-03-30 19:56 EEST] mlat-client(13039): Server status: synchronized with 14 nearby receivers
[2021-03-30 19:56 EEST] mlat-client(13039): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
[2021-03-30 19:58 EEST] 1233668 msgs recv’d from dump1090-fa (38 in last 5m); 1224325 msgs sent to FlightAware
[2021-03-30 20:03 EEST] 1233711 msgs recv’d from dump1090-fa (43 in last 5m); 1224368 msgs sent to FlightAware
[2021-03-30 20:08 EEST] 1233779 msgs recv’d from dump1090-fa (68 in last 5m); 1224436 msgs sent to FlightAware
[2021-03-30 20:11 EEST] mlat-client(13039): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
[2021-03-30 20:11 EEST] mlat-client(13039): Server status: synchronized with 9 nearby receivers
[2021-03-30 20:11 EEST] mlat-client(13039): Aircraft: 0 of 0 Mode S, 2 of 2 ADS-B used
[2021-03-30 20:11 EEST] mlat-client(13039): Receiver status: connected
[2021-03-30 20:11 EEST] mlat-client(13039): Receiver: 2.9 msg/s received 1.8 msg/s processed (62%)
[2021-03-30 20:13 EEST] 1233841 msgs recv’d from dump1090-fa (62 in last 5m); 1224498 msgs sent to FlightAware
[2021-03-30 20:18 EEST] 1233872 msgs recv’d from dump1090-fa (31 in last 5m); 1224529 msgs sent to FlightAware
[2021-03-30 20:19 EEST] mlat-client(13039): Beast-format results connection with 127.0.0.1:30104: connection lost
[2021-03-30 20:19 EEST] mlat-client(13039): Reconnecting in 30.0 seconds
[2021-03-30 20:19 EEST] faup1090 exited normally
[2021-03-30 20:19 EEST] mlat-client(13039): Lost connection to localhost:30005
[2021-03-30 20:19 EEST] lost connection to dump1090-fa via faup1090
[2021-03-30 20:19 EEST] reconnecting to dump1090-fa
[2021-03-30 20:19 EEST] no ADS-B data program seen listening on port 30005 for 2 seconds, next check in 60s
[2021-03-30 20:19 EEST] piaware (process 607) is exiting…
[2021-03-30 20:19 EEST] piaware (process 607) is shutting down because it received a shutdown signal (SIGTERM) from the system…
[2021-03-30 20:19 EEST] multilateration data no longer required, disabling mlat client
[2021-03-30 20:19 EEST] fa-mlat-client exited with SIG SIGTERM
[2021-03-30 20:22 EEST] site statistics URL: https://flightaware.com/adsb/stats/user/EELaur#stats-122913
[2021-03-30 20:22 EEST] no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
[2021-03-30 20:22 EEST] adept reported location: 61.01326, 24.49677, 236ft AMSL
[2021-03-30 20:22 EEST] my feeder ID is 8fb74893-12fc-4a5f-bd39-2a9c3ae41906
[2021-03-30 20:22 EEST] logged in to FlightAware as user EELaur
[2021-03-30 20:22 EEST] UAT support disabled by local configuration setting: uat-receiver-type
[2021-03-30 20:22 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:22 EEST] multilateration data requested
[2021-03-30 20:22 EEST] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2021-03-30 20:23 EEST] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 61.013 --lon 24.497
[2021-03-30 20:23 EEST] ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good
[2021-03-30 20:23 EEST] mlat-client(2162): Listening for Extended Basestation-format results connection on port 30106
[2021-03-30 20:23 EEST] mlat-client(2162): Route MTU changed to 1500
[2021-03-30 20:23 EEST] mlat-client(2162): Input connected to localhost:30005
[2021-03-30 20:23 EEST] mlat-client(2162): Listening for Beast-format results connection on port 30105
[2021-03-30 20:23 EEST] mlat-client(2162): Input format changed to BEAST, 12MHz clock
[2021-03-30 20:23 EEST] mlat-client(2162): Beast-format results connection with ::1:30104: connection established
[2021-03-30 20:25 EEST] piaware (process 30256) is exiting…
[2021-03-30 20:25 EEST] piaware (process 30256) is shutting down because it received a shutdown signal (SIGTERM) from the system…
[2021-03-30 20:25 EEST] faup1090 exited with SIG SIGTERM
[2021-03-30 20:25 EEST] fa-mlat-client exited with SIG SIGTERM
[2021-03-30 20:25 EEST] multilateration data no longer required, disabling mlat client
[2021-03-30 20:26 EEST] adept reported location: 61.01326, 24.49677, 236ft AMSL
[2021-03-30 20:26 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:26 EEST] multilateration data requested
[2021-03-30 20:26 EEST] logged in to FlightAware as user EELaur
[2021-03-30 20:26 EEST] my feeder ID is 8fb74893-12fc-4a5f-bd39-2a9c3ae41906
[2021-03-30 20:26 EEST] site statistics URL: https://flightaware.com/adsb/stats/user/EELaur#stats-122913
[2021-03-30 20:26 EEST] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2021-03-30 20:27 EEST] no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
[2021-03-30 20:27 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:27 EEST] multilateration data requested
[2021-03-30 20:27 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:27 EEST] site statistics URL: https://flightaware.com/adsb/stats/user/EELaur#stats-122913
[2021-03-30 20:27 EEST] my feeder ID is 8fb74893-12fc-4a5f-bd39-2a9c3ae41906
[2021-03-30 20:27 EEST] logged in to FlightAware as user EELaur
[2021-03-30 20:27 EEST] no ADS-B data program seen listening on port 30005 for 124 seconds, next check in 60s
[2021-03-30 20:28 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:28 EEST] no ADS-B data program seen listening on port 30005 for 184 seconds, next check in 60s
[2021-03-30 20:29 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:29 EEST] no ADS-B data program seen listening on port 30005 for 244 seconds, next check in 60s
[2021-03-30 20:30 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:30 EEST] no ADS-B data program seen listening on port 30005 for 304 seconds, next check in 60s
[2021-03-30 20:31 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:31 EEST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2021-03-30 20:31 EEST] attempting to start dump1090…
[2021-03-30 20:31 EEST] no ADS-B data program seen listening on port 30005 for 364 seconds, trying to start it…
[2021-03-30 20:31 EEST] dump1090 start appears to have been successful
[2021-03-30 20:31 EEST] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2021-03-30 20:32 EEST] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2021-03-30 20:32 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:33 EEST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2021-03-30 20:33 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:34 EEST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2021-03-30 20:34 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:35 EEST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2021-03-30 20:35 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:36 EEST] no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
[2021-03-30 20:36 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:36 EEST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2021-03-30 20:36 EEST] multilateration data no longer required, disabling mlat client
[2021-03-30 20:36 EEST] piaware (process 611) is shutting down because it received a shutdown signal (SIGTERM) from the system…
[2021-03-30 20:36 EEST] piaware (process 611) is exiting…
[2021-03-30 20:37 EEST] multilateration data requested
[2021-03-30 20:37 EEST] logged in to FlightAware as user EELaur
[2021-03-30 20:37 EEST] site statistics URL: https://flightaware.com/adsb/stats/user/EELaur#stats-122913
[2021-03-30 20:37 EEST] adept reported location: 61.01326, 24.49677, 236ft AMSL
[2021-03-30 20:38 EEST] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2021-03-30 20:38 EEST] no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
[2021-03-30 20:38 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:39 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:39 EEST] logged in to FlightAware as user EELaur
[2021-03-30 20:39 EEST] my feeder ID is 8fb74893-12fc-4a5f-bd39-2a9c3ae41906
[2021-03-30 20:39 EEST] no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s
[2021-03-30 20:40 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:40 EEST] my feeder ID is 8fb74893-12fc-4a5f-bd39-2a9c3ae41906
[2021-03-30 20:40 EEST] multilateration data requested
[2021-03-30 20:40 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:40 EEST] logged in to FlightAware as user EELaur
[2021-03-30 20:40 EEST] site statistics URL: https://flightaware.com/adsb/stats/user/EELaur#stats-122913
[2021-03-30 20:40 EEST] no ADS-B data program seen listening on port 30005 for 183 seconds, next check in 60s
[2021-03-30 20:41 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:41 EEST] no ADS-B data program seen listening on port 30005 for 243 seconds, next check in 60s
[2021-03-30 20:42 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:42 EEST] no ADS-B data program seen listening on port 30005 for 303 seconds, next check in 60s
[2021-03-30 20:42 EEST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2021-03-30 20:43 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:43 EEST] no ADS-B data program seen listening on port 30005 for 363 seconds, trying to start it…
[2021-03-30 20:43 EEST] attempting to start dump1090…
[2021-03-30 20:43 EEST] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2021-03-30 20:43 EEST] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2021-03-30 20:44 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:44 EEST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2021-03-30 20:45 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:45 EEST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2021-03-30 20:46 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:46 EEST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2021-03-30 20:47 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:47 EEST] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2021-03-30 20:47 EEST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2021-03-30 20:48 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:48 EEST] no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
[2021-03-30 20:49 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:49 EEST] multilateration data no longer required, disabling mlat client
[2021-03-30 20:49 EEST] piaware (process 615) is shutting down because it received a shutdown signal (SIGTERM) from the system…
[2021-03-30 20:49 EEST] piaware (process 615) is exiting…
[2021-03-30 20:50 EEST] adept reported location: 61.01326, 24.49677, 236ft AMSL
[2021-03-30 20:50 EEST] logged in to FlightAware as user EELaur
[2021-03-30 20:50 EEST] my feeder ID is 8fb74893-12fc-4a5f-bd39-2a9c3ae41906
[2021-03-30 20:50 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:50 EEST] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2021-03-30 20:51 EEST] no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
[2021-03-30 20:51 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:51 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:51 EEST] logged in to FlightAware as user EELaur
[2021-03-30 20:51 EEST] site statistics URL: https://flightaware.com/adsb/stats/user/EELaur#stats-122913
[2021-03-30 20:51 EEST] no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s
[2021-03-30 20:52 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:52 EEST] no ADS-B data program seen listening on port 30005 for 183 seconds, next check in 60s
[2021-03-30 20:53 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:53 EEST] no ADS-B data program seen listening on port 30005 for 243 seconds, next check in 60s
[2021-03-30 20:54 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:54 EEST] no ADS-B data program seen listening on port 30005 for 303 seconds, next check in 60s
[2021-03-30 20:55 EEST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2021-03-30 20:55 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:55 EEST] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2021-03-30 20:55 EEST] no ADS-B data program seen listening on port 30005 for 364 seconds, trying to start it…
[2021-03-30 20:55 EEST] attempting to start dump1090…
[2021-03-30 20:55 EEST] dump1090 start appears to have been successful
[2021-03-30 20:56 EEST] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2021-03-30 20:56 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:57 EEST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2021-03-30 20:57 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:58 EEST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2021-03-30 20:58 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 20:59 EEST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2021-03-30 20:59 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 21:00 EEST] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2021-03-30 21:00 EEST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2021-03-30 21:00 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 21:01 EEST] no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
[2021-03-30 21:01 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 21:02 EEST] no ADS-B data program seen listening on port 30005 for 370 seconds, trying to start it…
[2021-03-30 21:02 EEST] dump1090 start appears to have been successful
[2021-03-30 21:02 EEST] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2021-03-30 21:02 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 21:03 EEST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2021-03-30 21:03 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 21:04 EEST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2021-03-30 21:04 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 21:05 EEST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2021-03-30 21:05 EEST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2021-03-30 21:05 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 21:06 EEST] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2021-03-30 21:06 EEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2021-03-30 21:07 EEST] no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
Did you do this bit of the update?
Actually I did not and I have no idea how to do it 
The instructions are in the first post in the thread:
I don´t have those options there for some reason 
Give these command, then go to stats page again and check
sudo piaware-config allow-manual-updates yes
sudo piaware-config allow-auto-updates yes
1 Like