Can you help me troubleshoot these logs?

FlightAware ADS-B Flight Tracking
1

2022-04-11 13:55 EDT] piaware (process 420) is shutting down because it received a shutdown signal (SIGTERM) from the system…
[2022-04-11 13:55 EDT] performing manual update, action: reboot
[2022-04-11 13:55 EDT] piaware (process 420) is exiting…
[2022-04-11 13:55 EDT] fa-mlat-client exited with SIG SIGTERM
[2022-04-11 13:55 EDT] rebooting…
[2022-04-11 13:55 EDT] update request complete
[2022-04-11 13:55 EDT] multilateration data no longer required, disabling mlat client
[2022-04-11 13:56 EDT] adept reported location: 30.64941, -81.46300, 20ft AMSL
[2022-04-11 13:56 EDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2022-04-11 13:56 EDT] my feeder ID is xxx
[2022-04-11 13:56 EDT] site statistics URL: https://flightaware.com/adsb/stats/user/xxx
[2022-04-11 13:56 EDT] multilateration data requested
[2022-04-11 13:56 EDT] logged in to FlightAware as user xxx
[2022-04-11 13:56 EDT] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2022-04-11 13:56 EDT] no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
[2022-04-11 13:57 EDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2022-04-11 13:57 EDT] no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s

…REPEAT:

[2022-04-11 13:58 EDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2022-04-11 13:58 EDT] no ADS-B data program seen listening on port 30005 for 183 seconds, next check in 60s

2

First: Remove your feeder ID from logs above. This is a unique number you should not share.

Second: Seen to be that your dump1090-fa is not running. This is required for piaware.

Check with the following command:
sudo systemctl status dump1090-fa

If it’s not working also add te output of this command here:
sudo journalctl -xe|grep dump1090-fa

3

Thanks for the response. This is immediately following a reboot (I have to constantly reboot and it works for a “few” minutes. Note: the previous boot was without the USB dongle attached (I had to enable SSH).

As requested:
pi@piaware : ~ $ sudo systemctl status dump1090-fa

● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)

Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor pres

Active: active (running) since Mon 2022-04-11 16:26:20 EDT; 8min ago

Docs: PiAware - ADS-B and MLAT Receiver - FlightAware

Main PID: 870 (dump1090-fa)

Tasks: 3 (limit: 2059)

CGroup: /system.slice/dump1090-fa.service

└─870 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --device-inde

Apr 11 16:26:20 piaware dump1090-fa[870]: Found Rafael Micro R820T tuner

Apr 11 16:26:20 piaware dump1090-fa[870]: rtlsdr: tuner gain set to about 58.6 d

Apr 11 16:26:20 piaware dump1090-fa[870]: adaptive: using 50% duty cycle

Apr 11 16:26:20 piaware dump1090-fa[870]: adaptive: enabled adaptive gain contro

Apr 11 16:26:20 piaware dump1090-fa[870]: adaptive: enabled dynamic range contro

Apr 11 16:26:20 piaware dump1090-fa[870]: Allocating 4 zero-copy buffers

Apr 11 16:26:31 piaware dump1090-fa[870]: adaptive: available dynamic range (21.

Apr 11 16:26:31 piaware dump1090-fa[870]: adaptive: changing gain from 58.6dB (s

Apr 11 16:26:31 piaware dump1090-fa[870]: rtlsdr: tuner gain set to 49.6 dB (gai

Apr 11 16:26:41 piaware dump1090-fa[870]: adaptive: available dynamic range (31.

lines 1-19/19 (END)

pi@piaware : ~ $ sudo journalctl -xe|grep dump1090-fa

Apr 11 16:17:06 piaware generate-receiver-config[326]: Updating /etc/default/ dump1090-fa …

– Subject: A start job for unit dump1090-fa .service has finished successfully

– A start job for unit dump1090-fa .service has finished successfully.

Apr 11 16:17:07 piaware dump1090-fa [420]: Mon Apr 11 16:17:07 2022 EDT dump1090-fa 7.2~bpo10+1 starting up.

Apr 11 16:17:07 piaware dump1090-fa [420]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)

Apr 11 16:17:07 piaware dump1090-fa [420]: Detached kernel driver

Apr 11 16:17:08 piaware dump1090-fa [420]: Found Rafael Micro R820T tuner

Apr 11 16:17:08 piaware dump1090-fa [420]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)

Apr 11 16:17:08 piaware dump1090-fa [420]: adaptive: using 50% duty cycle

Apr 11 16:17:08 piaware dump1090-fa [420]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) … 58.6dB (step 29)

Apr 11 16:17:08 piaware dump1090-fa [420]: adaptive: enabled dynamic range control, target dynamic range 30.0dB

Apr 11 16:17:08 piaware dump1090-fa [420]: Allocating 4 zero-copy buffers

Apr 11 16:17:11 piaware piaware[421]: ADS-B data program ’ dump1090-fa ’ is listening on port 30005, so far so good

Apr 11 16:17:11 piaware piaware[421]: Started faup1090 (pid 481) to connect to dump1090-fa

Apr 11 16:17:12 piaware piaware[421]: piaware received a message from dump1090-fa !

Apr 11 16:17:18 piaware dump1090-fa [420]: adaptive: available dynamic range (20.1dB) < required dynamic range (30.0dB), switching to downward scan

Apr 11 16:17:18 piaware dump1090-fa [420]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound

Apr 11 16:17:18 piaware dump1090-fa [420]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)

Apr 11 16:17:28 piaware dump1090-fa [420]: adaptive: available dynamic range (30.5dB) >= required dynamic range (30.0dB), stopping downwards scan here

Apr 11 16:17:42 piaware piaware[421]: 103 msgs recv’d from dump1090-fa ; 52 msgs sent to FlightAware

Apr 11 16:25:08 piaware piaware[421]: 314 msgs recv’d from dump1090-fa (211 in last 7m); 211 msgs sent to FlightAware

Apr 11 16:25:13 piaware dump1090-fa [420]: cb transfer status: 1, canceling…

Apr 11 16:25:13 piaware dump1090-fa [420]: rtlsdr: rtlsdr_read_async returned unexpectedly, probably lost the USB device, bailing out

Apr 11 16:25:13 piaware dump1090-fa [420]: Mon Apr 11 16:25:13 2022 EDT Waiting for receive thread termination

Apr 11 16:25:13 piaware dump1090-fa [420]: Reattaching kernel driver failed!

Apr 11 16:25:13 piaware dump1090-fa [420]: Mon Apr 11 16:25:13 2022 EDT Abnormal exit.

Apr 11 16:25:13 piaware systemd[1]: dump1090-fa .service: Main process exited, code=exited, status=1/FAILURE

– An ExecStart= process belonging to unit dump1090-fa .service has exited.

Apr 11 16:25:13 piaware systemd[1]: dump1090-fa .service: Failed with result ‘exit-code’.

– The unit dump1090-fa .service has entered the ‘failed’ state with result ‘exit-code’.

Apr 11 16:25:14 piaware piaware[421]: lost connection to dump1090-fa via faup1090

Apr 11 16:25:14 piaware piaware[421]: reconnecting to dump1090-fa

Apr 11 16:25:44 piaware systemd[1]: dump1090-fa .service: Service RestartSec=30s expired, scheduling restart.

Apr 11 16:25:44 piaware systemd[1]: dump1090-fa .service: Scheduled restart job, restart counter is at 1.

– Automatic restarting of the unit dump1090-fa .service has been scheduled, as the result for

– Subject: A stop job for unit dump1090-fa .service has finished

– A stop job for unit dump1090-fa .service has finished.

Apr 11 16:25:44 piaware generate-receiver-config[827]: Updating /etc/default/ dump1090-fa …

– Subject: A start job for unit dump1090-fa .service has finished successfully

– A start job for unit dump1090-fa .service has finished successfully.

Apr 11 16:25:44 piaware dump1090-fa [828]: Mon Apr 11 16:25:44 2022 EDT dump1090-fa 7.2~bpo10+1 starting up.

Apr 11 16:25:44 piaware dump1090-fa [828]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)

Apr 11 16:25:44 piaware dump1090-fa [828]: Detached kernel driver

Apr 11 16:25:44 piaware dump1090-fa [828]: Found Rafael Micro R820T tuner

Apr 11 16:25:45 piaware dump1090-fa [828]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)

Apr 11 16:25:45 piaware dump1090-fa [828]: adaptive: using 50% duty cycle

Apr 11 16:25:45 piaware dump1090-fa [828]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) … 58.6dB (step 29)

Apr 11 16:25:45 piaware dump1090-fa [828]: adaptive: enabled dynamic range control, target dynamic range 30.0dB

Apr 11 16:25:45 piaware dump1090-fa [828]: Allocating 4 zero-copy buffers

Apr 11 16:25:49 piaware dump1090-fa [828]: cb transfer status: 1, canceling…

Apr 11 16:25:49 piaware dump1090-fa [828]: rtlsdr: rtlsdr_read_async returned unexpectedly, probably lost the USB device, bailing out

Apr 11 16:25:49 piaware dump1090-fa [828]: Mon Apr 11 16:25:49 2022 EDT Waiting for receive thread termination

Apr 11 16:25:49 piaware dump1090-fa [828]: Reattaching kernel driver failed!

Apr 11 16:25:49 piaware dump1090-fa [828]: Mon Apr 11 16:25:49 2022 EDT Abnormal exit.

Apr 11 16:25:49 piaware systemd[1]: dump1090-fa .service: Main process exited, code=exited, status=1/FAILURE

– An ExecStart= process belonging to unit dump1090-fa .service has exited.

Apr 11 16:25:49 piaware systemd[1]: dump1090-fa .service: Failed with result ‘exit-code’.

– The unit dump1090-fa .service has entered the ‘failed’ state with result ‘exit-code’.

Apr 11 16:26:19 piaware systemd[1]: dump1090-fa .service: Service RestartSec=30s expired, scheduling restart.

Apr 11 16:26:19 piaware systemd[1]: dump1090-fa .service: Scheduled restart job, restart counter is at 2.

– Automatic restarting of the unit dump1090-fa .service has been scheduled, as the result for

– Subject: A stop job for unit dump1090-fa .service has finished

– A stop job for unit dump1090-fa .service has finished.

Apr 11 16:26:20 piaware generate-receiver-config[869]: Updating /etc/default/ dump1090-fa …

– Subject: A start job for unit dump1090-fa .service has finished successfully

– A start job for unit dump1090-fa .service has finished successfully.

Apr 11 16:26:20 piaware dump1090-fa [870]: Mon Apr 11 16:26:20 2022 EDT dump1090-fa 7.2~bpo10+1 starting up.

Apr 11 16:26:20 piaware dump1090-fa [870]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)

Apr 11 16:26:20 piaware dump1090-fa [870]: Detached kernel driver

Apr 11 16:26:20 piaware dump1090-fa [870]: Found Rafael Micro R820T tuner

Apr 11 16:26:20 piaware dump1090-fa [870]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)

Apr 11 16:26:20 piaware dump1090-fa [870]: adaptive: using 50% duty cycle

Apr 11 16:26:20 piaware dump1090-fa [870]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) … 58.6dB (step 29)

Apr 11 16:26:20 piaware dump1090-fa [870]: adaptive: enabled dynamic range control, target dynamic range 30.0dB

Apr 11 16:26:20 piaware dump1090-fa [870]: Allocating 4 zero-copy buffers

Apr 11 16:26:31 piaware dump1090-fa [870]: adaptive: available dynamic range (21.6dB) < required dynamic range (30.0dB), switching to downward scan

Apr 11 16:26:31 piaware dump1090-fa [870]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound

Apr 11 16:26:31 piaware dump1090-fa [870]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)

Apr 11 16:26:41 piaware dump1090-fa [870]: adaptive: available dynamic range (31.2dB) >= required dynamic range (30.0dB), stopping downwards scan here

Apr 11 16:27:15 piaware piaware[421]: ADS-B data program ’ dump1090-fa ’ is listening on port 30005, so far so good

Apr 11 16:27:15 piaware piaware[421]: Started faup1090 (pid 943) to connect to dump1090-fa

Apr 11 16:27:31 piaware sudo[944]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl status dump1090-fa

Apr 11 16:28:54 piaware sudo[991]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl status dump1090-fa

Apr 11 16:30:08 piaware piaware[421]: 729 msgs recv’d from dump1090-fa (415 in last 5m); 626 msgs sent to FlightAware

Apr 11 16:34:41 piaware sudo[1118]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl status dump1090-fa

Apr 11 16:35:08 piaware piaware[421]: 1444 msgs recv’d from dump1090-fa (715 in last 5m); 1341 msgs sent to FlightAware

pi@piaware : ~ $

4

You’re posting tons of logs but you never even mentioned what the problem is that you’re trying to troubleshoot by looking at those logs.

5

Bad power supply or bad SDR or USB extension to SDR dropping power.

General power you can check like this:

sudo dmesg --ctime | grep voltage || echo No Undervoltage in dmesg.
6

The problem is displayed in the last sentence of his first log. And therefore i have requested more logs about dump1090-fa as it did not seem to be running.

@ckallen
wiedehopf suggested already to check power and USB.
I had one case where the USB connect was not tightened enough on the USB connector.
Try squeezing the connect of the stick a bit so that it’s harder to connect.

Unlikely but in my case it helped

7

Ah, I missed that. It’s hard to tell what’s causing the problem but I’m leaning toward a power issue on the USB bus or an intermittent bad USB connection to the dongle. Check your power supply and move the dongle to a different USB port, and if you’re using a USB extension cable between the Pi and dongle remove it. Also if you have any other USB devices plugged into the Pi remove those.

8

Yes, not well-formatted logs are hard to read.
My experience i made with the Airspy regarding USB. Fixed it as described above.

Never had issues with the FA sticks.

But giving it a try won’t hurt

9

Thanks for the power suggestion - I had seen that in other posts and ordered a new power supply to be safe… did not seem to matter. I waited until after it failed again with the new power supply before starting this post.

Here’s the output of this command:
pi@piaware : ~ $ sudo dmesg --ctime | grep voltage || echo No Undervoltage in dmesg.

No Undervoltage in dmesg.

10

I think you may be onto something here with the USB connection. I tried a different USB “position” and it seemed to stay up longer (a few hours versus not at all or just a few minutes). I’m wondering if my dongle is bad - but replacement ones seem to be hard to find now. I’ll try “squeezing the connector” and trying yet another USB position - nothing else plugged in and plugged directly in to the pi.

11

Here’s the same command after failure:

pi@piaware : ~ $ sudo 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: activating (auto-restart) (Result: exit-code) since Tue 2022-04-12 15:21:39 EDT; 5s

Docs: PiAware - ADS-B and MLAT Receiver - FlightAware

Process: 3972 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-f

Main PID: 3972 (code=exited, status=1/FAILURE)

12

Please add again the results of

sudo journalctl -xe|grep dump1090

Hint: Please format the logs as code, this make it better readable.
How?
Highligt the whole log text and click on the icon in the toolbar:

image

13

Seems to be repeating (I trimmed from the end - hopefully didn’t cut off anything important):



**pi@piaware** : **~ $** sudo journalctl -xe|grep dump1090

Apr 12 20:06:58 piaware piaware[422]: attempting to start **dump1090** ..

Apr 12 20:06:58 piaware sudo[1579]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/invoke-rc.d --query **dump1090** -fa start

Apr 12 20:06:58 piaware piaware[422]: attempting to start **dump1090** -fa using 'systemctl --no-block restart **dump1090** -fa.service < /dev/null'...

Apr 12 20:06:58 piaware sudo[1583]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl --no-block restart **dump1090** -fa.service

Apr 12 20:06:58 piaware systemd[1]: Stopped **dump1090** ADS-B receiver (FlightAware customization).

-- Subject: A stop job for unit **dump1090** -fa.service has finished

-- A stop job for unit **dump1090** -fa.service has finished.

Apr 12 20:06:58 piaware piaware[422]: **dump1090** start appears to have been successful

Apr 12 20:06:58 piaware generate-receiver-config[1585]: Updating /etc/default/ **dump1090** -fa ..

Apr 12 20:06:58 piaware systemd[1]: Started **dump1090** ADS-B receiver (FlightAware customization).

-- Subject: A start job for unit **dump1090** -fa.service has finished successfully

-- A start job for unit **dump1090** -fa.service has finished successfully.

Apr 12 20:06:58 piaware **dump1090** -fa[1586]: Tue Apr 12 20:06:58 2022 EDT **dump1090** -fa 7.2~bpo10+1 starting up.

Apr 12 20:06:58 piaware **dump1090** -fa[1586]: rtlsdr: no supported devices found.

Apr 12 20:06:58 piaware systemd[1]: **dump1090** -fa.service: Main process exited, code=exited, status=1/FAILURE

-- An ExecStart= process belonging to unit **dump1090** -fa.service has exited.

Apr 12 20:06:58 piaware systemd[1]: **dump1090** -fa.service: Failed with result 'exit-code'.

-- The unit **dump1090** -fa.service has entered the 'failed' state with result 'exit-code'.

Apr 12 20:07:29 piaware systemd[1]: **dump1090** -fa.service: Service RestartSec=30s expired, scheduling restart.

Apr 12 20:07:29 piaware systemd[1]: **dump1090** -fa.service: Scheduled restart job, restart counter is at 60.

-- Automatic restarting of the unit **dump1090** -fa.service has been scheduled, as the result for

Apr 12 20:07:29 piaware systemd[1]: Stopped **dump1090** ADS-B receiver (FlightAware customization).

-- Subject: A stop job for unit **dump1090** -fa.service has finished

-- A stop job for unit **dump1090** -fa.service has finished.

Apr 12 20:07:29 piaware generate-receiver-config[1619]: Updating /etc/default/ **dump1090** -fa ..

Apr 12 20:07:29 piaware systemd[1]: Started **dump1090** ADS-B receiver (FlightAware customization).

-- Subject: A start job for unit **dump1090** -fa.service has finished successfully

-- A start job for unit **dump1090** -fa.service has finished successfully.

Apr 12 20:07:29 piaware **dump1090** -fa[1620]: Tue Apr 12 20:07:29 2022 EDT **dump1090** -fa 7.2~bpo10+1 starting up.

Apr 12 20:07:29 piaware **dump1090** -fa[1620]: rtlsdr: no supported devices found.

Apr 12 20:07:29 piaware systemd[1]: **dump1090** -fa.service: Main process exited, code=exited, status=1/FAILURE

-- An ExecStart= process belonging to unit **dump1090** -fa.service has exited.

Apr 12 20:07:29 piaware systemd[1]: **dump1090** -fa.service: Failed with result 'exit-code'.

-- The unit **dump1090** -fa.service has entered the 'failed' state with result 'exit-code'.

Apr 12 20:07:59 piaware systemd[1]: **dump1090** -fa.service: Service RestartSec=30s expired, scheduling restart.

Apr 12 20:07:59 piaware systemd[1]: **dump1090** -fa.service: Scheduled restart job, restart counter is at 61.

-- Automatic restarting of the unit **dump1090** -fa.service has been scheduled, as the result for

Apr 12 20:07:59 piaware systemd[1]: Stopped **dump1090** ADS-B receiver (FlightAware customization).

-- Subject: A stop job for unit **dump1090** -fa.service has finished

-- A stop job for unit **dump1090** -fa.service has finished.

Apr 12 20:07:59 piaware generate-receiver-config[1627]: Updating /etc/default/ **dump1090** -fa ..

Apr 12 20:07:59 piaware systemd[1]: Started **dump1090** ADS-B receiver (FlightAware customization).

-- Subject: A start job for unit **dump1090** -fa.service has finished successfully

-- A start job for unit **dump1090** -fa.service has finished successfully.

Apr 12 20:07:59 piaware **dump1090** -fa[1628]: Tue Apr 12 20:07:59 2022 EDT **dump1090** -fa 7.2~bpo10+1 starting up.

Apr 12 20:08:00 piaware **dump1090** -fa[1628]: rtlsdr: no supported devices found.

Apr 12 20:08:00 piaware systemd[1]: **dump1090** -fa.service: Main process exited, code=exited, status=1/FAILURE

-- An ExecStart= process belonging to unit **dump1090** -fa.service has exited.

Apr 12 20:08:00 piaware systemd[1]: **dump1090** -fa.service: Failed with result 'exit-code'.

-- The unit **dump1090** -fa.service has entered the 'failed' state with result 'exit-code'.

...
14

Just ask people to use pastebin instead …

dead.

1 Like
15

Yeah, thanks for the reminder. I always forget it.

16

Hopefully closing this out. My new (replacement) USB Pro Stick came today and I replaced. So far, so good. We’ll chock this up to bad hardware if this new one continues to work.

17

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