# PiAware 5.0

**URL:** https://discussions.flightaware.com/t/piaware-5-0/74588
**Category:** ADS-B Flight Tracking
**Created:** [March 11, 2021, 4:03pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588 "2021-03-11T16:03:47Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![timothydykstra82](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/timothydykstra82/32/113872_2.png) [@timothydykstra82](https://discussions.flightaware.com/u/timothydykstra82)
#### Post date: [March 11, 2021, 4:03pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/1 "2021-03-11T16:03:48Z")

</div>

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. 😆

 ![Screenshot_20210311-110006-01](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/0/5/05215889e19656c3eb44c74f1d1135efc24b5d51.jpeg)

---

<div class="post-metadata">

### Author: ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)
#### Post date: [March 11, 2021, 4:51pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/3 "2021-03-11T16:51:02Z")

</div>

![image](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/3/1/31d1f68b04532bd9e21f89f8c39b4ee527cc4fde.png)

---

<div class="post-metadata">

### Author: ![eric1tran](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/eric1tran/32/119986_2.png) [@eric1tran](https://discussions.flightaware.com/u/eric1tran)
#### Post date: [March 11, 2021, 4:53pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/4 "2021-03-11T16:53:36Z")

</div>

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

---

<div class="post-metadata">

### Author: ![CallMeDaz](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/callmedaz/32/113481_2.png) [@CallMeDaz](https://discussions.flightaware.com/u/CallMeDaz)
#### Post date: [March 11, 2021, 4:58pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/5 "2021-03-11T16:58:34Z")

</div>

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

---

<div class="post-metadata">

### Author: ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)
#### Post date: [March 11, 2021, 5:10pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/6 "2021-03-11T17:10:28Z")

</div>

> [@CallMeDaz](#):
>
> I have just upgraded now i can’t access tar1090 or graphs but it is feeding.

```auto
ls /run/dump1090-fa | grep -v history

```

```auto
cat /usr/local/share/tar1090/nginx-tar1090.conf | grep alias

```

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

---

<div class="post-metadata">

### Author: ![CallMeDaz](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/callmedaz/32/113481_2.png) [@CallMeDaz](https://discussions.flightaware.com/u/CallMeDaz)
#### Post date: [March 11, 2021, 5:12pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/7 "2021-03-11T17:12:17Z")

</div>

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:~ $

---

<div class="post-metadata">

### Author: ![NigelRichardson](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/nigelrichardson/32/113310_2.png) [@NigelRichardson](https://discussions.flightaware.com/u/NigelRichardson)
#### Post date: [March 11, 2021, 5:12pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/8 "2021-03-11T17:12:29Z")

</div>

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

---

<div class="post-metadata">

### Author: ![timothydykstra82](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/timothydykstra82/32/113872_2.png) [@timothydykstra82](https://discussions.flightaware.com/u/timothydykstra82)
#### Post date: [March 11, 2021, 5:14pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/9 "2021-03-11T17:14:15Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![eric1tran](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/eric1tran/32/119986_2.png) [@eric1tran](https://discussions.flightaware.com/u/eric1tran)
#### Post date: [March 11, 2021, 5:15pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/10 "2021-03-11T17:15:49Z")

</div>

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

---

<div class="post-metadata">

### Author: ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)
#### Post date: [March 11, 2021, 5:16pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/11 "2021-03-11T17:16:31Z")

</div>

> [@NigelRichardson](#):
>
> problems here and even the new Skyaware address (New SkyAware URL: /skyaware or :8080) doesn’t connect

Sounds like a lighttpd issue.

```auto
sudo journalctl -u lighttpd | tail -n30

```

> [@CallMeDaz](#):
>
> 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

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

---

<div class="post-metadata">

### Author: ![CallMeDaz](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/callmedaz/32/113481_2.png) [@CallMeDaz](https://discussions.flightaware.com/u/CallMeDaz)
#### Post date: [March 11, 2021, 5:19pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/12 "2021-03-11T17:19:16Z")

</div>

> [@wiedehopf](#):
>
> `sudo journalctl -u lighttpd | tail -n30`

> **[log - Pastebin.com](https://pastebin.com/mF8d8r5v)**
>
> Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

is this ok for you?

thanks

---

<div class="post-metadata">

### Author: ![NigelRichardson](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/nigelrichardson/32/113310_2.png) [@NigelRichardson](https://discussions.flightaware.com/u/NigelRichardson)
#### Post date: [March 11, 2021, 5:23pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/13 "2021-03-11T17:23:15Z")

</div>

Tried

sudo journalctl -u lighttpd | tail -n30

and got the attached error messages

Thanks

 ![Error message](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/c/a/ca3ee305b0c73d850686d88b86ff1b2da3f16619.jpeg)

---

<div class="post-metadata">

### Author: ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)
#### Post date: [March 11, 2021, 5:24pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/14 "2021-03-11T17:24:17Z")

</div>

> [@eric1tran](#):
>
> @wiedehopf Let me know what you find.

Yeah you’re breaking lighttpd mod\_setenv by loading it twice.  
[dump1090/debian/lighttpd/89-skyaware.conf at master · flightaware/dump1090 · GitHub](https://github.com/flightaware/dump1090/blob/master/debian/lighttpd/89-skyaware.conf)  
[https://github.com/flightaware/dump1090/blob/master/debian/lighttpd/89-dump1090-fa.conf](https://github.com/flightaware/dump1090/blob/master/debian/lighttpd/89-dump1090-fa.conf)

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

```auto
server.modules += ( "mod_setenv" )

```

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

```auto
 # 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

```auto
# 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.

---

<div class="post-metadata">

### Author: ![NigelRichardson](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/nigelrichardson/32/113310_2.png) [@NigelRichardson](https://discussions.flightaware.com/u/NigelRichardson)
#### Post date: [March 11, 2021, 5:28pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/15 "2021-03-11T17:28:35Z")

</div>

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

![Tar1090](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/a/e/ae30837b350205c8209e74037727c0441e4611bb.jpeg)

---

<div class="post-metadata">

### Author: ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)
#### Post date: [March 11, 2021, 5:29pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/16 "2021-03-11T17:29:08Z")

</div>

Hmmm … i might have spoken too soon.

```auto
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.

---

<div class="post-metadata">

### Author: ![eric1tran](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/eric1tran/32/119986_2.png) [@eric1tran](https://discussions.flightaware.com/u/eric1tran)
#### Post date: [March 11, 2021, 5:31pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/17 "2021-03-11T17:31:54Z")

</div>

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

---

<div class="post-metadata">

### Author: ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)
#### Post date: [March 11, 2021, 5:32pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/18 "2021-03-11T17:32:19Z")

</div>

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

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

```

Can you post the complete output to pastebin @NigelRichardson ?

---

<div class="post-metadata">

### Author: ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)
#### Post date: [March 11, 2021, 5:35pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/19 "2021-03-11T17:35:38Z")

</div>

> [@eric1tran](#):
>
> just installed tar1090 on top of 5.0 and seems to be ok

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?

```auto
sudo apt update
sudo apt install lighttpd

```

---

<div class="post-metadata">

### Author: ![CallMeDaz](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/callmedaz/32/113481_2.png) [@CallMeDaz](https://discussions.flightaware.com/u/CallMeDaz)
#### Post date: [March 11, 2021, 5:35pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/20 "2021-03-11T17:35:57Z")

</div>

> **[pi@piaware:~ $ cat /etc/lighttpd/conf-enabled/89-\*# Allows access to the stati...](https://pastebin.com/xDm13P2X)**
>
> Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

---

<div class="post-metadata">

### Author: ![CallMeDaz](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/callmedaz/32/113481_2.png) [@CallMeDaz](https://discussions.flightaware.com/u/CallMeDaz)
#### Post date: [March 11, 2021, 5:37pm UTC](https://discussions.flightaware.com/t/piaware-5-0/74588/21 "2021-03-11T17:37:46Z")

</div>

> [@wiedehopf](#):
>
> `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) …

[Next page](https://discussions.flightaware.com/t/piaware-5-0/74588.md?page=2)
