Piaware v 3.7.1 on Debian 10.0 (Buster) amd64 / Intel PC

FlightAware ADS-B Flight Tracking
23

pi@raspberrypi:~ $ sudo systemctl restart dump1090-fa
pi@raspberrypi:~ $ sudo journalctl -eu dump1090-fa
Jul 14 18:22:15 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:22:15 2019 BST No data received from the SDR for a
Jul 14 18:23:15 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:23:15 2019 BST No data received from the SDR for a
Jul 14 18:24:16 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:24:16 2019 BST No data received from the SDR for a
Jul 14 18:25:16 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:25:16 2019 BST No data received from the SDR for a
Jul 14 18:26:16 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:26:16 2019 BST No data received from the SDR for a
Jul 14 18:27:16 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:27:16 2019 BST No data received from the SDR for a
Jul 14 18:28:17 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:28:17 2019 BST No data received from the SDR for a
Jul 14 18:29:17 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:29:17 2019 BST No data received from the SDR for a
Jul 14 18:30:17 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:30:17 2019 BST No data received from the SDR for a
Jul 14 18:31:17 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:31:17 2019 BST No data received from the SDR for a
Jul 14 18:32:18 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:32:18 2019 BST No data received from the SDR for a
Jul 14 18:33:18 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:33:18 2019 BST No data received from the SDR for a
Jul 14 18:34:18 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:34:18 2019 BST No data received from the SDR for a
Jul 14 18:35:19 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:35:19 2019 BST No data received from the SDR for a
Jul 14 18:36:19 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:36:19 2019 BST No data received from the SDR for a
Jul 14 18:37:19 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:37:19 2019 BST No data received from the SDR for a
Jul 14 18:38:19 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:38:19 2019 BST No data received from the SDR for a
Jul 14 18:39:20 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:39:20 2019 BST No data received from the SDR for a
Jul 14 18:40:20 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:40:20 2019 BST No data received from the SDR for a
Jul 14 18:41:20 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:41:20 2019 BST No data received from the SDR for a
Jul 14 18:42:20 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:42:20 2019 BST No data received from the SDR for a
Jul 14 18:43:21 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:43:21 2019 BST No data received from the SDR for a
Jul 14 18:44:21 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:44:21 2019 BST No data received from the SDR for a
Jul 14 18:45:21 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:45:21 2019 BST No data received from the SDR for a
Jul 14 18:46:06 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:46:06 2019 BST Caught SIGTERM, shutting downā€¦
Jul 14 18:46:06 raspberrypi systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)ā€¦
Jul 14 18:46:06 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:46:06 2019 BST Waiting for receive thread terminat
Jul 14 18:47:36 raspberrypi systemd[1]: dump1090-fa.service: State ā€˜stop-sigtermā€™ timed out. Killing.
Jul 14 18:47:36 raspberrypi systemd[1]: dump1090-fa.service: Killing process 1383 (dump1090-fa) with signal SIGK
Jul 14 18:47:36 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=killed, status=9/KILL
Jul 14 18:47:36 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ā€˜timeoutā€™.
Jul 14 18:47:36 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Jul 14 18:47:36 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jul 14 18:47:36 raspberrypi dump1090-fa[1513]: Sun Jul 14 18:47:36 2019 BST dump1090-fa 3.7.1 starting up.
Jul 14 18:47:39 raspberrypi dump1090-fa[1513]: rtlsdr: using device #0: Generic RTL2832U OEM (, , SN )
Jul 14 18:47:39 raspberrypi dump1090-fa[1513]: rtlsdr_write_reg failed with -7
Jul 14 18:47:39 raspberrypi dump1090-fa[1513]: Resetting deviceā€¦
lines 554-590/590 (END)
Jul 14 18:22:15 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:22:15 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:23:15 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:23:15 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:24:16 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:24:16 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:25:16 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:25:16 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:26:16 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:26:16 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:27:16 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:27:16 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:28:17 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:28:17 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:29:17 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:29:17 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:30:17 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:30:17 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:31:17 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:31:17 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:32:18 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:32:18 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:33:18 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:33:18 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:34:18 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:34:18 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:35:19 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:35:19 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:36:19 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:36:19 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:37:19 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:37:19 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:38:19 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:38:19 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:39:20 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:39:20 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:40:20 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:40:20 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:41:20 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:41:20 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:42:20 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:42:20 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:43:21 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:43:21 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:44:21 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:44:21 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:45:21 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:45:21 2019 BST No data received from the SDR for a long time, it may have wedged
Jul 14 18:46:06 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:46:06 2019 BST Caught SIGTERM, shutting downā€¦
Jul 14 18:46:06 raspberrypi systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)ā€¦
Jul 14 18:46:06 raspberrypi dump1090-fa[1383]: Sun Jul 14 18:46:06 2019 BST Waiting for receive thread termination
Jul 14 18:47:36 raspberrypi systemd[1]: dump1090-fa.service: State ā€˜stop-sigtermā€™ timed out. Killing.
Jul 14 18:47:36 raspberrypi systemd[1]: dump1090-fa.service: Killing process 1383 (dump1090-fa) with signal SIGKILL.
Jul 14 18:47:36 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=killed, status=9/KILL
Jul 14 18:47:36 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ā€˜timeoutā€™.
Jul 14 18:47:36 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Jul 14 18:47:36 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jul 14 18:47:36 raspberrypi dump1090-fa[1513]: Sun Jul 14 18:47:36 2019 BST dump1090-fa 3.7.1 starting up.
Jul 14 18:47:39 raspberrypi dump1090-fa[1513]: rtlsdr: using device #0: Generic RTL2832U OEM (, , SN )
Jul 14 18:47:39 raspberrypi dump1090-fa[1513]: rtlsdr_write_reg failed with -7

24

What system is this on?
pi4?

Maybe insufficient power for the dongle, is it connected directly or via cable?
Try another port.

25

i tried retart several times but this time i got aircraft working now
yes on pi4
connected directly and or via lead and usb hub
but for now its all working strange
but happy

26

Havenā€™t you read in the pi4 thread? ā€¦

It doesnā€™t work yet, wait for the system to be updated.
The fix is found but itā€™s gonna be a few days before it is available.

When itā€™s available you can

sudo apt update
sudo apt dist-upgrade
27

i been following thread
will watch and wait
many thanks
john

28

Itā€™s completely random. In rare cases it works.

29

pi4 and buster working fine now

30

As i stated in the post above, itā€™s completely random if it works.

Also i really donā€™t understand why you are posting in this thread.
amd64 / Intel PC is NOT Raspberry Pi.

31

Sorry about wrong section
but i only used info on this thread to get my pi4 working
john

32

Is there any way of knowing it is in the files you get via apt-get? Apart from just trying whether it works :wink:

33

Youā€™ll have to monitor RPi kernel releases on github or something:
xhci: add quirk for host controllers that don't update endpoint DCS by P33M Ā· Pull Request #3066 Ā· raspberrypi/linux Ā· GitHub

Releases Ā· raspberrypi/linux Ā· GitHub

So you check if the release has the commit.

1 Like
34

While awaiting the amplifiers from China. I built a second unit for another location. However, using Debian Buster, Iā€™ve encountered problems with lighttpd. The localhost/dump1090-fa and localhost:8080 did not load and lighttpd at 80 showed placeholder html only when pihole was installed. The lighttpd had a bunch of errors. Am I correct in assuming that dump1090-fa and lighttpd under Buster have some issues working together?

35

Not always.
Did you by chance update to Buster?

The main lighttpd configuration file needs some changes when upgrading to Buster.
So itā€™s better to install the maintainers version.

You can either fix it by hand or try

sudo apt purge lighttpd
sudo apt install lighttpd

The relevant log:

sudo journalctl --no-pager -u lighttpd

Edit: I realize now that i already pretty much typed this, oh well.

1 Like
36

This is a 2nd Pi 0W on which a new SD with the Buster image was installed. The other chip running Stretch is running as usual, separately.
Iā€™ll have to try your suggestion this weekend.
I had an error closely resembling this: Raspbian Buster lighttpd failed to start - Help - Pi-hole Userspace

37

Did you install Debian Buster or Raspbian Buster?

38

Just post the journalctl log. That will show the ACTUAL error.

39

Jul 29 20:05:23 SenPi1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Jul 29 20:05:23 SenPi1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 116.
Jul 29 20:05:23 SenPi1 systemd[1]: Stopped Lighttpd Daemon.
Jul 29 20:05:23 SenPi1 systemd[1]: Starting Lighttpd Daemonā€¦
Jul 29 20:05:25 SenPi1 lighttpd[20586]: 2019-07-29 20:05:23: (mod_openssl.c.445) SSL: BIO_read_filename(ā€˜/etc/lighttpd/server.pemā€™) failed
Jul 29 20:05:25 SenPi1 lighttpd[20586]: 2019-07-29 20:05:23: (server.c.1183) Initialization of plugins failed. Going down.
Jul 29 20:05:25 SenPi1 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 29 20:05:25 SenPi1 systemd[1]: lighttpd.service: Failed with result ā€˜exit-codeā€™.
Jul 29 20:05:25 SenPi1 systemd[1]: Failed to start Lighttpd Daemon.
Jul 29 20:05:25 SenPi1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Jul 29 20:05:25 SenPi1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 117.
Jul 29 20:05:25 SenPi1 systemd[1]: Stopped Lighttpd Daemon.
Jul 29 20:05:25 SenPi1 systemd[1]: Starting Lighttpd Daemonā€¦
Jul 29 20:05:27 SenPi1 lighttpd[20604]: 2019-07-29 20:05:25: (mod_openssl.c.445) SSL: BIO_read_filename(ā€˜/etc/lighttpd/server.pemā€™) failed
Jul 29 20:05:27 SenPi1 lighttpd[20604]: 2019-07-29 20:05:25: (server.c.1183) Initialization of plugins failed. Going down.
Jul 29 20:05:27 SenPi1 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 29 20:05:27 SenPi1 systemd[1]: lighttpd.service: Failed with result ā€˜exit-codeā€™.
Jul 29 20:05:27 SenPi1 systemd[1]: Failed to start Lighttpd Daemon.
Jul 29 20:05:28 SenPi1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Jul 29 20:05:28 SenPi1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 118.
Jul 29 20:05:28 SenPi1 systemd[1]: Stopped Lighttpd Daemon.
Jul 29 20:05:28 SenPi1 systemd[1]: Starting Lighttpd Daemonā€¦
Jul 29 20:05:29 SenPi1 lighttpd[20663]: 2019-07-29 20:05:28: (mod_openssl.c.445) SSL: BIO_read_filename(ā€˜/etc/lighttpd/server.pemā€™) failed
Jul 29 20:05:29 SenPi1 lighttpd[20663]: 2019-07-29 20:05:28: (server.c.1183) Initialization of plugins failed. Going down.
Jul 29 20:05:29 SenPi1 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 29 20:05:29 SenPi1 systemd[1]: lighttpd.service: Failed with result ā€˜exit-codeā€™.
Jul 29 20:05:29 SenPi1 systemd[1]: Failed to start Lighttpd Daemon.
Jul 29 20:05:30 SenPi1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Jul 29 20:05:30 SenPi1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 119.
Jul 29 20:05:30 SenPi1 systemd[1]: Stopped Lighttpd Daemon.
Jul 29 20:05:30 SenPi1 systemd[1]: Starting Lighttpd Daemonā€¦
Jul 29 20:05:32 SenPi1 lighttpd[20697]: 2019-07-29 20:05:30: (mod_openssl.c.445) SSL: BIO_read_filename(ā€˜/etc/lighttpd/server.pemā€™) failed
Jul 29 20:05:32 SenPi1 lighttpd[20697]: 2019-07-29 20:05:30: (server.c.1183) Initialization of plugins failed. Going down.
Jul 29 20:05:32 SenPi1 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 29 20:05:32 SenPi1 systemd[1]: lighttpd.service: Failed with result ā€˜exit-codeā€™.
Jul 29 20:05:32 SenPi1 systemd[1]: Failed to start Lighttpd Daemon.
Jul 29 20:05:32 SenPi1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Jul 29 20:05:32 SenPi1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 120.
Jul 29 20:05:32 SenPi1 systemd[1]: Stopped Lighttpd Daemon.
Jul 29 20:05:32 SenPi1 systemd[1]: Starting Lighttpd Daemonā€¦
Jul 29 20:05:34 SenPi1 lighttpd[20729]: 2019-07-29 20:05:32: (mod_openssl.c.445) SSL: BIO_read_filename(ā€˜/etc/lighttpd/server.pemā€™) failed
Jul 29 20:05:34 SenPi1 lighttpd[20729]: 2019-07-29 20:05:32: (server.c.1183) Initialization of plugins failed. Going down.
Jul 29 20:05:34 SenPi1 systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 29 20:05:34 SenPi1 systemd[1]: lighttpd.service: Failed with result ā€˜exit-codeā€™.
Jul 29 20:05:34 SenPi1 systemd[1]: Failed to start Lighttpd Daemon.
Jul 29 20:05:34 SenPi1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Jul 29 20:05:34 SenPi1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 121.
Jul 29 20:05:34 SenPi1 systemd[1]: Stopped Lighttpd Daemon.
Jul 29 20:05:34 SenPi1 systemd[1]: Starting Lighttpd Daemonā€¦
Jul 29 20:05:36 SenPi1 systemd[1]: Started Lighttpd Daemon.
Jul 29 20:05:52 SenPi1 systemd[1]: Reloading Lighttpd Daemon.
Jul 29 20:05:52 SenPi1 systemd[1]: Reloaded Lighttpd Daemon.

40

Oops! I had meant Raspbian Buster.

41

You have enabled mod_openssl and the certificate file (/etc/lighttpd/server.pem) is missing.

42

Youā€™re right. Since I had purged lighttpd and pihole, the original errors that showed up are no longer present.
Lighty-enable mod is now using dump1090-fa, dump1090-fa-stratcache, status, and unfigured.
The placeholder file is back at port 80.

While uninstalling pihole, many dependencies like PHP, etc. were left. How to remove them?
Also, resolv.conf is showing ā€œnameserver 127.0.0.1ā€. Changing this to 1.1.1.1/4.4.4.4 helps as without it, sudo apt update does not resolve and work. However, it changes back to namserver.