Piaware 6.1 or Dump1090 Problem

FlightAware ADS-B Flight Tracking
1

Hi
since a few days i have this problem. A reboot of the pi wil help for a couple of minutes or hours
but then it happened again.

I added some cli querys, seems to be a dump1090 problem? but what exactly.
I hope i found the right category.

sudo systemctl status dump1090-fa.service
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sat 2021-10-16 17:28:59 CEST; 11s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 11224 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, status=1/FAILURE)
Main PID: 11224 (code=exited, status=1/FAILURE)

Okt 16 17:28:59 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
pi@raspberrypi:~ $

sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-10-16 17:10:01 CEST; 17min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 1614 (piaware)
Tasks: 3 (limit: 2059)
CGroup: /system.slice/piaware.service
├─1614 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
└─2605 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --resu

Okt 16 17:27:11 raspberrypi piaware[1614]: mlat-client(2605): Connection to localhost:30005 lost: [Errno 111] Connection refused
Okt 16 17:27:11 raspberrypi piaware[1614]: mlat-client(2605): Reconnecting in 0.5 seconds
Okt 16 17:27:12 raspberrypi piaware[1614]: mlat-client(2605): Connection to localhost:30005 lost: [Errno 111] Connection refused
Okt 16 17:27:12 raspberrypi piaware[1614]: mlat-client(2605): Reconnecting in 30.0 seconds
Okt 16 17:27:22 raspberrypi piaware[1614]: mlat-client(2605): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Okt 16 17:27:42 raspberrypi piaware[1614]: mlat-client(2605): Connection to localhost:30005 lost: [Errno 111] Connection refused
Okt 16 17:27:42 raspberrypi piaware[1614]: mlat-client(2605): Reconnecting in 0.5 seconds
Okt 16 17:27:43 raspberrypi piaware[1614]: mlat-client(2605): Connection to localhost:30005 lost: [Errno 111] Connection refused
Okt 16 17:27:43 raspberrypi piaware[1614]: mlat-client(2605): Reconnecting in 30.0 seconds
Okt 16 17:27:52 raspberrypi piaware[1614]: mlat-client(2605): Beast-format results connection with ::1:30104: [Errno 111] Connection refused

pi@raspberrypi:~ $ piaware-status
PiAware master process (piaware) is running with pid 1614.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is running with pid 2605.
Local ADS-B receiver (dump1090) is not running.

no program appears to be listening for ES connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is connected to FlightAware.

got ‘couldn’t open socket: connection refused’
dump1090 is NOT producing data on localhost:30005.

Your feeder ID is fc------------------------ (from /var/cache/piaware/feeder_id)

pi@raspberrypi:~ $ tail /var/log/piaware.log
Oct 16 17:21:27 raspberrypi piaware[1614]: mlat-client(2605): Reconnecting in 0.5 seconds
Oct 16 17:21:28 raspberrypi piaware[1614]: mlat-client(2605): Connection to localhost:30005 lost: [Errno 111] Connection refused
Oct 16 17:21:28 raspberrypi piaware[1614]: mlat-client(2605): Reconnecting in 30.0 seconds
Oct 16 17:21:49 raspberrypi piaware[1614]: mlat-client(2605): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Oct 16 17:21:57 raspberrypi piaware[1614]: no ADS-B data program seen listening on port 30005 for 131 seconds, next check in 60s
Oct 16 17:21:59 raspberrypi piaware[1614]: mlat-client(2605): Connection to localhost:30005 lost: [Errno 111] Connection refused
Oct 16 17:21:59 raspberrypi piaware[1614]: mlat-client(2605): Reconnecting in 0.5 seconds
Oct 16 17:21:59 raspberrypi piaware[1614]: mlat-client(2605): Connection to localhost:30005 lost: [Errno 111] Connection refused
Oct 16 17:21:59 raspberrypi piaware[1614]: mlat-client(2605): Reconnecting in 30.0 seconds
Oct 16 17:22:19 raspberrypi piaware[1614]: mlat-client(2605): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused

2

https://github.com/wiedehopf/adsb-wiki/wiki/Debug-commands#dump1090-fa

Show the log please.

3

That usually means low voltage at the SDR or the SDR is dying.

Check undervoltage … if you have that you know it’s the power supply for sure:
https://github.com/wiedehopf/adsb-wiki/wiki/Debug-commands#undervoltage

4

Hi, here are the results of the tests.

for the dump1090 grep only a few minutest the rest is all the same.

sudo dmesg --ctime | grep voltage
pi@raspberrypi:~ $ bash -c “$(wget -nv -O - https://raw.githubusercontent.com/wiedehopf/adsb-scripts/master/throttled.sh)”
2021-10-17 18:40:10 URL:https://raw.githubusercontent.com/wiedehopf/adsb-scripts/master/throttled.sh [1421/1421] → “-” [1]
Status: 0x0
Undervolted:
Now: NO
Run: NO
Throttled:
Now: NO
Run: NO
Frequency Capped:
Now: NO
Run: NO
Softlimit:
Now: NO
Run: NO
pi@raspberrypi:~ $

Lost samples in the first 2 seconds after starting the test are common and not a problem!
Starting 30 second rtl_test, standby!

No supported devices found.

Test finished!
More than 2 lost samples per million or other errors probably mean the receiver isn’t working correctly.
Try another power supply before condemning the receiver though!

No undervoltage detected, looking fine!
If the dongle is not directly plugged into the Raspberry Pi, lack of power/volta ge could still be an issue.
Even without detected undervoltage a better power supply can often improve recep tion!
For optimum performance i would recommend the Official Raspberry Pi power supply .

Okt 17 18:32:27 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:32:27 raspberrypi dump1090-fa[21534]: Sun Oct 17 18:32:27 2021 CEST dump1090-fa 6.1 starting up.
Okt 17 18:32:27 raspberrypi dump1090-fa[21534]: rtlsdr: no supported devices found.
Okt 17 18:32:27 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Okt 17 18:32:27 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Okt 17 18:32:57 raspberrypi systemd[1]: dump1090-fa.service: Service RestartSec=30s expired, scheduling restart.
Okt 17 18:32:57 raspberrypi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 2949.
Okt 17 18:32:57 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:32:57 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:32:58 raspberrypi dump1090-fa[21601]: Sun Oct 17 18:32:58 2021 CEST dump1090-fa 6.1 starting up.
Okt 17 18:32:58 raspberrypi dump1090-fa[21601]: rtlsdr: no supported devices found.
Okt 17 18:32:58 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Okt 17 18:32:58 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Okt 17 18:33:28 raspberrypi systemd[1]: dump1090-fa.service: Service RestartSec=30s expired, scheduling restart.
Okt 17 18:33:28 raspberrypi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 2950.
Okt 17 18:33:28 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:33:28 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:33:28 raspberrypi dump1090-fa[21671]: Sun Oct 17 18:33:28 2021 CEST dump1090-fa 6.1 starting up.
Okt 17 18:33:28 raspberrypi dump1090-fa[21671]: rtlsdr: no supported devices found.
Okt 17 18:33:28 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Okt 17 18:33:28 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Okt 17 18:33:58 raspberrypi systemd[1]: dump1090-fa.service: Service RestartSec=30s expired, scheduling restart.
Okt 17 18:33:58 raspberrypi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 2951.
Okt 17 18:33:58 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:33:58 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:33:58 raspberrypi dump1090-fa[21739]: Sun Oct 17 18:33:58 2021 CEST dump1090-fa 6.1 starting up.
Okt 17 18:33:58 raspberrypi dump1090-fa[21739]: rtlsdr: no supported devices found.
Okt 17 18:33:58 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Okt 17 18:33:58 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Okt 17 18:34:06 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:34:06 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:34:06 raspberrypi dump1090-fa[21772]: Sun Oct 17 18:34:06 2021 CEST dump1090-fa 6.1 starting up.
Okt 17 18:34:06 raspberrypi dump1090-fa[21772]: rtlsdr: no supported devices found.
Okt 17 18:34:06 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Okt 17 18:34:06 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Okt 17 18:34:36 raspberrypi systemd[1]: dump1090-fa.service: Service RestartSec=30s expired, scheduling restart.
Okt 17 18:34:36 raspberrypi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 2952.
Okt 17 18:34:36 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:34:36 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Okt 17 18:34:36 raspberrypi dump1090-fa[22052]: Sun Oct 17 18:34:36 2021 CEST dump1090-fa 6.1 starting up.
Okt 17 18:34:36 raspberrypi dump1090-fa[22052]: rtlsdr: no supported devices found.
Okt 17 18:34:36 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Okt 17 18:34:36 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.

5

The Pi can’t see your dongle on the USB bus; probably a hardware failure.

6

Hi, thanks for all help,

i connected now the dongle directly (there was an extention line to the usb port) and it started directly. I will see if it keeps running or still stops working. My Pi power supply is an original but you never know.
Good to knew these scripts from wiedehopf :+1: :+1: :+1:

7

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.