FlightAware Discussions

PiAware 5.0

Just successfully updated to 5.0 and everything seems to be running properly. I’m assuming this will be formally announced and a full change log posted at some point.

Only issue I see is the My ADS-B page seems to think I should “upgrade” to 4.0. :laughing:


Y’all are quick. It should say 5.0 now for everyone. Announcement/changelog coming soon!

I have just upgraded now i can’t access tar1090 or graphs but it is feeding. I have checked and my local ip address hasn’t changed, Status page is showing it being online and feeding

ls /run/dump1090-fa | grep -v history
cat /usr/local/share/tar1090/nginx-tar1090.conf | grep alias

Let’s see if the json files are there and how tar1090 is configured.

pi@piaware:~ ls /run/dump1090-fa | grep -v history aircraft.json receiver.json stats.json pi@piaware:~ cat /usr/local/share/tar1090/nginx-tar1090.conf | grep alias
alias /run/dump1090-fa/;
alias /var/globe_history/;
alias /run/tar1090/;
alias /usr/local/share/tar1090/aircraft_sil/;
alias /usr/local/share/tar1090/html/;
pi@piaware:~ $

Same problems here and even the new Skyaware address (New SkyAware URL: /skyaware or :8080) doesn’t connect

1 Like

SkyAware works perfectly fine for me, but I did notice a new quirk regarding aircraft trails in tar1090 that was introduced with the PiAware 5.0 upgrade. I posted more details in the tar1090 thread.

The aircraft.json files shouldn’t have been altered. @wiedehopf Let me know what you find.

Sounds like a lighttpd issue.

sudo journalctl -u lighttpd | tail -n30

Please also show your lighttpd log using the above command.
Using https://pastebin.com/ will be easier to read than pasting the log here without properly quoting it.

is this ok for you?



sudo journalctl -u lighttpd | tail -n30

and got the attached error messages


Yeah you’re breaking lighttpd mod_setenv by loading it twice.
dump1090/89-skyaware.conf at master · flightaware/dump1090 · GitHub
dump1090/89-dump1090-fa.conf at master · flightaware/dump1090 · GitHub

I already have code in the tar1090 install script to comment out automatically this line from all config files:

server.modules += ( "mod_setenv" )

Then i’ll add it in its own config file …

 # cat 07-mod_setenv.conf 
server.modules += ( "mod_setenv" )

So people having issue with tar1090 … please just rerun the tar1090 setup script it will hopefully fix the issue.

@eric1tran @obj
Sorry for messing with the lighttpd config stuff like this but there really isn’t a good solution for this.

Oh by the way i do pretty much the same for stat-cache

# cat 47-stat-cache.conf
server.stat-cache-engine = "disable"

The same problem existed with skyaware978 and dump1090-fa already … thus why i added those somewhat ugly workarounds.
Now that the config file name has changed the issue surfaces once again.

I’ve rerun tar1090 installation and get the following error message


Hmmm … i might have spoken too soon.

Mar 11 16:51:29 piaware lighttpd[1123]: Duplicate array-key '/data/'
Mar 11 16:51:29 piaware lighttpd[1123]: 2021-03-11 16:51:28: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-skyaware.conf line: 41 pos: 1 parser failed somehow near here: (EOL)
Mar 11 16:51:29 piaware lighttpd[1123]: 2021-03-11 16:51:28: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 48 pos: 15 parser failed somehow near here: (EOL)

I’ve seen this error before and i believe it’s a bugged lighttpd version …
But i can’t remember the work around.

I just installed tar1090 on top of 5.0 and seems to be ok

Let’s just check all the files that might be doing stuff here…

cat /etc/lighttpd/conf-enabled/89-*

Can you post the complete output to pastebin @NigelRichardson ?

Yeah the mod_setenv and mod_alias aren’t causing the issue it’s something else … there was some discussion about a similar error on this forum.
A lighttpd dev even got involved i think.

@NigelRichardson @CallMeDaz
can you also just to exclude that possibility get the most recent lighttpd version?

sudo apt update
sudo apt install lighttpd

● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2021-03-11 17:36:27 UTC; 20ms ago
Process: 20477 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)
Failed to start Lighttpd. Maybe another webserver is already listening on port 80?
Processing triggers for man-db (2.8.5-2) …
Processing triggers for systemd (241-7~deb10u3+rpi1) …