ADS-B Receiver Project Setup Scripts

An update - it mostly worked although the maximum range and CPU temperature were missing in the graphs (and yes I know about fixing the OrangePi CPU temperature).

So it tried reinstalling to see if those errors got fixed.

Instead a whole world of pain :open_mouth:

“The package “dump1090-fa” could not be installed.”

Error is “dpkg: error: cannot access archive ‘dump1090-fa_3.6.3_*.deb’: No such file or directory”

A bit similar to ADS-B Receiver Project Setup Scripts - #1726 by abcd567 where 3.5.3 was the problem…

So in less than a week something has broken the install - any ideas?

Fortunately my old Piaware install continues to work.

No need to install it if it’s already installed.

Deselect it with space bar and use tab to get to ok.

Also my guess: reinstall won’t help with the problems you stated.
Not sure why those graphs don’t work.

You can run the graph creation script manually and check if there are any errors creating the graph.

I did try reinstalling this morning and it compiled ok. Having tried twice last night with same problem, perhaps something did not download correctly?

But still those two graphs are missing.

Manually running the script gives errors for those two parameters:

ERROR: opening ‘/var/lib/collectd/rrd/localhost/table-localhost/gauge-cpu_temp.rrd’: No such file or directory

ERROR: opening ‘/var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_range-max_range.rrd’: No such file or directory

Off to explore further.

Do you have your location set in /etc/default/dump1090-fa ?

Post your http://pi/dump1090/data/receiver.json please.

Maybe the orange pi does not even have a cpu temperature readout?

Location not set yet - waiting until it is all working. Then I will just swap the SD card in the existing OrangePi setup and change the user id on the SD card so it picks up existing identity.

Orange Pi does have CPU temperature readout - it is working ok in my other OrangePi. But that is using 1.15 mutability and I want to upgrade to 3.63 FA.

Meanwhile I do at least have a working system :relieved: . So no panic to get this fixed - just wondered if anybody had similar problem and an easy fix!.

the cpu temperature readout has literally nothing to do with dump1090.

@idh

Same with me:
temprature graph missing altogather.
max range missing.

Missing temperature graph seems to be a result of issue 425 code being added to the master code.

In bash/portal/graphs.sh at line 203:

if [[ “${HARDWARE_PLATFORM}” = “RPI” ]] ; then

In bash/portal/graphs.sh at line 225:
elif [[ “${HARDWARE_PLATFORM}” = “CHIP” ]] ; then

That logic works fine if you have a RPi or a CHIP, but for everything else it just gets omitted.

Better logic would be to have the CHIP option first and then let the “elif” fall through to the default value without any testing of which system is being used.

Added the following to /etc/collectd/collectd.conf

First search for “# Configure the dump1090 python module” and insert the code above the text box.

<Plugin table>
	<Table "/sys/class/thermal/thermal_zone0/temp">
		Instance localhost
		Separator " "
		<Result>
			Type gauge
			InstancePrefix "cpu_temp"
			ValuesFrom 0
		</Result>
	</Table>
</Plugin>

On the OrangePi, temperature read out is wrong even after applying the known correction but I do have a graph so that is progress.
Edit: Found correction was not required when using Armbian 5.65 Debian so temperature now reading correctly.

1 Like

is the range working now?

Not yet but I wonder if that is because since I don’t have a location entered? I will add a location and then check again.

And for OrangePi PC users, if you use Armbian 5.65 Debian, no correction for the temperature readout is needed. [Previously a change had to be made in “make-collectd-graphs.sh”.]

1 Like

Location added on Flightaware page and range graph works now. TIme to move that SD card to my main receiver.

1 Like

I recently updated my ADS-B Receiver Project on my raspberry pi and I am not getting any reporting from the Dump1090 (graphs or maps). I pulled back the latest scripts using git and reinstalled without any change. It appears I’m getting data but it’s not reporting. The graphs don’t show any data (the system graphs are populated though) and the /dump1090.php shows ‘404 - Not Found’.

Any suggestions?

What does

sudo systemctl status lighttpd

and

sudo systemctl status dump1090-fa
sudo systemctl status dump1090

print?

lighttpd

  • lighttpd.service - Lighttpd Daemon
    Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled)
    Active: active (running) since Tue 2018-11-20 10:09:15 EST; 26min ago
    Process: 810 ExecStartPre=/usr/sbin/lighttpd -t -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
    Main PID: 1046 (lighttpd)
    CGroup: /system.slice/lighttpd.service
    |-1046 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
    |-1073 /usr/bin/php-cgi
    |-1086 /usr/bin/php-cgi
    |-1087 /usr/bin/php-cgi
    |-1088 /usr/bin/php-cgi
    `-1089 /usr/bin/php-cgi

Nov 20 10:09:15 FlightScan lighttpd[810]: Syntax OK
Nov 20 10:09:15 FlightScan systemd[1]: Started Lighttpd Daemon.
Nov 20 10:09:15 FlightScan lighttpd[1046]: 2018-11-20 10:09:15: (plugin.c.131) Cannot load plugin mod_setenv mor…eases
Hint: Some lines were ellipsized, use -l to show in full.

dump1090-fa

  • dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
    Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled)
    Active: active (running) since Tue 2018-11-20 10:09:13 EST; 27min ago
    Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
    Main PID: 809 (dump1090-fa)
    CGroup: /system.slice/dump1090-fa.service
    `-809 /usr/bin/dump1090-fa --device-index 0 --gain -10 --ppm 0 --net-bo-port 30005 --max-range 360 --net -…

Nov 20 10:09:13 FlightScan systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Nov 20 10:09:14 FlightScan dump1090-fa[809]: Tue Nov 20 10:09:14 2018 EST dump1090-fa 3.6.3 starting up.
Nov 20 10:09:14 FlightScan dump1090-fa[809]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHID…0001)
Nov 20 10:09:14 FlightScan dump1090-fa[809]: Found Rafael Micro R820T tuner
Nov 20 10:09:14 FlightScan dump1090-fa[809]: rtlsdr: enabling tuner AGC
Hint: Some lines were ellipsized, use -l to show in full.

dump1090

  • dump1090.service
    Loaded: not-found (Reason: No such file or directory)
    Active: inactive (dead)

Do I need to set up another instance of dump1090?

No i just wasn’t sure which version you were using so it was the famous shotgun approach.
Let’s get some more detail on lighttpd:

sudo journalctl -u lighttpd --no-pager  -n50

Does
http://ADDRESS/dump1090/

with ADDRESS being the address of your pi show the local map?

– Logs begin at Tue 2018-11-20 10:09:05 EST, end at Tue 2018-11-20 11:18:47 EST. –
Nov 20 10:09:13 FlightScan systemd[1]: Starting Lighttpd Daemon…
Nov 20 10:09:15 FlightScan lighttpd[810]: Syntax OK
Nov 20 10:09:15 FlightScan systemd[1]: Started Lighttpd Daemon.
Nov 20 10:09:15 FlightScan lighttpd[1046]: 2018-11-20 10:09:15: (plugin.c.131) Cannot load plugin mod_setenv more than once, please fix your config (we may not accept such configs in future releases

http://192.168.1.99/dump1090/ redirects to http://192.168.1.99/dump1090/gmap.html and gives the 404 - Not Found error page.

somehow your configuration is screwed up.

seems like the adsb-receiverproject install script is not properly detecting that you are using dump1090-fa.

did you choose any feeders or did you just say don’t install dump1090?

Can you check which configs are active:

cd /etc/lighttpd/conf-enabled
ls

Also post the output of

cat /etc/lighttpd/conf-enabled/89-adsb-portal.conf

Modifying it to properly point to the dump1090-fa data folder will make it work.

Thank you for the help!

I always have it re-install dump1090 in case there were updates.

/etc/lighttpd/conf-enabled:
10-fastcgi.conf 15-fastcgi-php.conf 89-adsb-portal.conf 89-dump1090.conf 89-dump1090-fa.conf

output of 89-adsb-portal.conf:
# Add dump1090 as an alias to the dump1090-fa HTML folder.
alias.url += (
“/dump1090/data/” => “/run/dump1090-fa/”,
“/dump1090/” => “/usr/share/dump1090-fa/html/”
)
# Redirect the slash-less dump1090 URL
url.redirect += (
“^/dump1090$” => “/dump1090/”
)
# Add CORS header
server.modules += ( “mod_setenv” )
$HTTP[“url”] =~ “^/dump1090/data/..json$" {
setenv.add-response-header = ( “Access-Control-Allow-Origin” => "
” )
}
# Block all access to the data directory accept for local requests.
$HTTP[“remoteip”] !~ “127.0.0.1” {
$HTTP[“url”] =~ “^/data/” {
url.access-deny = ( “” )
}
}

Ok i believe i see the problem:

sudo rm /etc/lighttpd/conf-enabled/89-dump1090.conf
service lighttpd force-reload 

That should make it work.

If you are using the packet install of dump1090-fa just don’t make it reinstall dump1090 please it leads to this problem. (especially if you don’t choose dump1090-fa)

Not sure maybe something else installed dump1090 or tried.

1 Like

Thank you wiedehopf! That fixed the issue. Looking at the logs it appears to have stopped working after an update in mid September. I might have changed a setting or something during the install.

Thanks again!