FlightAware Discussions

HOWTO: Airspy mini and Airspy R2: Piaware / dump1090-fa configuration

The command limits how much backlog it looks at, you can add -n 20000 or even higher numbers to look at more log entries.

Also Log goes to memory and is limited so it might have been pushed out.

Depends a lot how “noisy” your journalctl is overall.

1 Like

It happened again. Short power blip in my house, at about 7:41. After that, the aisrpy_adsb wasn’t working anymore.
To make things clearer, the decoder runs on a laptop (with battery) but the network switch that serves that has no battery back-up.
I have to go to the laptop and manually log in in the login-screen, and then everything works.

This is the airpsy_adsb log:

Nov 24 08:22:39 ubuntu airspy_adsb[5323]: Push client connected to 127.0.0.1:30004 (beast)
Nov 28 07:41:14 ubuntu airspy_adsb[5323]: /!\ Lost 196608 samples /!\
Nov 28 07:41:14 ubuntu airspy_adsb[5323]: /!\ Lost 196608 samples /!\
Nov 28 07:41:14 ubuntu airspy_adsb[5323]: /!\ Lost 196608 samples /!\
Nov 28 07:41:14 ubuntu airspy_adsb[5323]: /!\ Lost 393216 samples /!\
Nov 28 07:41:14 ubuntu airspy_adsb[5323]: /!\ Lost 196608 samples /!\
Nov 28 07:41:14 ubuntu airspy_adsb[5323]: /!\ Lost 393216 samples /!\
Nov 28 07:41:14 ubuntu airspy_adsb[5323]: /!\ Lost 196608 samples /!\
Nov 28 07:56:57 ubuntu airspy_adsb[5323]: Decoding stopped
Nov 28 07:56:57 ubuntu airspy_adsb[5323]: Push client disconnected from 127.0.0.1:30004 (beast)
Nov 28 07:56:58 ubuntu airspy_adsb[5323]: Acquired Airspy device with serial 26A464DC28232193
Nov 28 07:56:58 ubuntu airspy_adsb[5323]: Decoding started at 24 MSPS (Gain: auto; CPU target: 90 %)
Nov 28 07:57:10 ubuntu airspy_adsb[5323]: Push client connected to 127.0.0.1:30004 (beast)

Any ideas? It might be something else, network related?

Try another Ubuntu version.

1 Like

Hi SoNic
mines ok but using dietpi :slight_smile:
root@DietPi:~# sudo journalctl -eu airspy_adsb -f
– Journal begins at Sat 2021-11-27 03:48:25 GMT. –
Nov 27 03:48:25 DietPi systemd[1]: Started Airspy ADS-B receiver.
Nov 27 03:48:26 DietPi airspy_adsb[245]: airspy_adsb v2.2-RC30
Nov 27 03:48:26 DietPi airspy_adsb[245]: Listening for beast clients on port 47787
Nov 27 03:48:26 DietPi airspy_adsb[245]: Acquired Airspy device with serial 62CC68FF218F5F17
Nov 27 03:48:26 DietPi airspy_adsb[245]: Decoding started at 24 MSPS (Gain: auto; Preamble Filter: 4.0)
Nov 27 03:48:27 DietPi airspy_adsb[245]: Push client connected to 127.0.0.1:30004 (beast)
Nov 27 03:48:27 DietPi airspy_adsb[245]: Push client disconnected from 127.0.0.1:30004 (beast)
Nov 27 03:48:40 DietPi airspy_adsb[245]: Push client connected to 127.0.0.1:30004 (beast)

Ubuntu 20.04.3 LTS

I think it has to do with the fact that I keep the laptop lid closed and Ubuntu needs to use “tweaks” to disable suspend.

Are you sure about that? I am using Kubuntu 21.10 as my desktop version. In the energy settings of KDE i can completely disable the suspend mode while lid is closed.

Well, you might need a desktop environment to set it. No idea if this is working on a headless install.

Hmmm… yes mine is a desktop environment, but I feel like that app is not starting soon enough.

I’ll try this:
How to Change Lid Close Behavior in Ubuntu 20.04 | UbuntuHandbook

Oh, that’s i did not think of so far. Sorry, no idea how to get this running.
I use it from time to time while watching TV on a bigger screen where the device is connected via HDMI. For this, i close the lid to disable the internal screen which i do not need during that time.

1 Like