Piaware: permission denied

keukenrol · February 15, 2023, 11:31am

I have 2 rpi 3b+ setups for adsb, already running dump1090-fa for other feeding websites. I wanted to add flightaware to the list, unfortunately after installation it does not seem to start due to a permission issue. Both pi’s are running bullseye 64 bit.

pi@SDRsetup:~ $ piaware
2023-02-15 11:30:15Z failed to reopen /var/log/piaware.log: couldn't open "/var/log/piaware.log": permission denied
2023-02-15 11:30:15Z ****************************************************
2023-02-15 11:30:15Z piaware version 8.2 is running, process ID 33389
2023-02-15 11:30:15Z your system info is: Linux SDRsetup 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
2023-02-15 11:30:16Z Connecting to FlightAware adept server at piaware.flightaware.com/1200
2023-02-15 11:30:16Z Connection with adept server at piaware.flightaware.com/1200 established
2023-02-15 11:30:17Z TLS handshake with adept server at piaware.flightaware.com/1200 completed
2023-02-15 11:30:17Z FlightAware server certificate validated
2023-02-15 11:30:17Z encrypted session established with FlightAware
2023-02-15 11:30:18Z logged in to FlightAware as user guest
2023-02-15 11:30:18Z my feeder ID is [HIDDEN]
2023-02-15 11:30:18Z Failed to update feeder ID file at /var/cache/piaware/feeder_id: couldn't open "/var/cache/piaware/feeder_id.new": permission denied
2023-02-15 11:30:18Z site statistics URL: https://flightaware.com/adsb/stats/site/192551
2023-02-15 11:30:18Z ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
2023-02-15 11:30:18Z Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
2023-02-15 11:30:18Z Started faup1090 (pid 33430) to connect to dump1090-fa
2023-02-15 11:30:18Z UAT support disabled by local configuration setting: uat-receiver-type
2023-02-15 11:30:18Z piaware received a message from dump1090-fa!
2023-02-15 11:30:18Z piaware has successfully sent several msgs to FlightAware!

Any idea how to get it to work?
I have followed the following link for 64 bit installs:

github.com

abcd567a/rpi/blob/master/README.md

## RPi Model 3 & 4 with 64-bit OS (arm64 / aarch64) <br> 
## Pre-built packages of piaware 8.2, dump1090-fa 8.2, piaware-web 8.2, dump978-fa 8.2, and beast-splitter 8.2, on following OS </br>
## (1) 64-bit Raspberry Pi OS Bullseye </br> 
## (2) 64-bit DietPi OS Bullseye </br>  
### [Links to download 64-bit OS](https://github.com/abcd567a/rpi/blob/master/README.md#links-to-download-64-bit-os-)
## How To Install Piaware arm64 Packages on Bullseye from this Personal Package Archive (PPA):


### STEP-1: Add this repository to list of apt sources by following 3 commands:
**First two commands are long. Please scroll right to see and copy them in FULL.** 
```
sudo wget -O /etc/apt/sources.list.d/abcd567a.list https://abcd567a.github.io/rpi/abcd567a.list
```
```
sudo wget -O /etc/apt/trusted.gpg.d/abcd567a-key.gpg https://abcd567a.github.io/rpi/KEY2.gpg
```
```
sudo apt update  
```

This file has been truncated. show original

Jonseyt23 · February 15, 2023, 11:59am

You might want to delete the feeder I’d out of the text

abcd567 · February 15, 2023, 12:57pm

@keukenrol
Permission denied error message will go away when you CLAIM the new piaware feeder.

Claim your PiAware client on FlightAware

You should wait about four or five minutes for your PiAware to start and then you can associate your FlightAware account with your PiAware device to receive all the benefits.

Once your device is running, please:

Look up the IP address in your router admin and go to the assigned IP address in a browser on the same network. If the device hasn’t been claimed a link to claim the PiAware device will display.

NOTE:
You will need to install piaware-web to see the page shown below at IP-OF-PI in your browser.

sudo apt install piaware-web

ALTERNATIVELY CLAIM BY FOLLOWING METHOD

Click the link below:

https://flightaware.com/adsb/piaware/claim

If after 5 minutes your device hasn’t displayed as claimed try restarting the device, if that still doesn’t work re-confirm the Wi-Fi settings (if using Wi-Fi) are correct. Lastly contact us at ADSBsupport@FlightAware.com. Check your stats page (link below) to confirm it was claimed.

https://flightaware.com/adsb/stats/user/

obj · February 15, 2023, 5:49pm

piaware is started by systemd as a separate dedicated user. You shouldn’t run it by hand as pi.

abcd567 · February 15, 2023, 7:04pm

Oops, I missed/overlooked this.

keukenrol · February 15, 2023, 9:00pm

I already have a lighttpd webserver running on the ip of my pi, I suppose the piaware-web will conflict with it if no configuration is asked after installation?

I did try the claiming method but no piaware communication was found on my ip. That’s why I manually tried to run piaware in order to be able to see it.

Today the claim page just remains on loading…

abcd567 · February 16, 2023, 12:27am

No, the piaware-web is completely compatible to lighttpd webserver. In fact both the dump1090-fa and piaware-web depend on lighttpd webserver and both automatically configure lighttpd at their installation. The user does NOT have to do any manual configuration.

This may be a temporary situation. Try again after a while.

keukenrol · February 16, 2023, 9:00am

Ok, installed the web agian but nothing to see on port 8080 or 8081 for example. Where do I get to see the webpage then? The main ip has a webpage made by myself so…

Used the top command to check if piaware is running and it sure is, however using the claim page still tells me that no device is found on my ip…
" Unfortunately, FlightAware hasn’t found a new, unclaimed PiAware feeder to claim."

abcd567 · February 16, 2023, 1:38pm

Try:

IP-of-Pi (without any port number)

OR

IP-of-Pi:80

The file index.html inside folder
/var/www/html/
displays the piaware-web page

pi@raspberrypi:~ $ ls /var/www/html/ 

favicon.ico  index.js             logo.gif
 index.lighttpd.html  translations
index.html   lib

keukenrol · February 16, 2023, 2:45pm

As mentioned before, I already have my own “website” running on the IP-of-PI of my pi using lighttpd. It is a php file with different status indications and a node red dashboard.
Thanks for the link, I will merge the code of piaware web with my implementation to get it running on a new link.
This is what I get:

Also, still no device to claim…
The top command does show that piaware is running…

abcd567 · February 16, 2023, 3:51pm

What the output of these commands?

sudo systemctl status piaware

sudo journalctl -u piaware -e

sudo journalctl -u piaware -b | grep “logged in” `

sudo journalctl -u piaware -b | grep msgs

keukenrol · February 16, 2023, 7:03pm

pi@SDRsetup:~ $ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2023-02-16 19:53:26 CET; 6min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 850 (piaware)
Tasks: 3 (limit: 779)
CPU: 8.551s
CGroup: /system.slice/piaware.service
├─ 850 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
└─1168 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout

pi@SDRsetup:~ $ sudo journalctl -u piaware -e
Feb 16 19:53:29 SDRsetup sudo[1137]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all →
Feb 16 19:53:29 SDRsetup sudo[1137]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=998)
Feb 16 19:53:29 SDRsetup sudo[1137]: pam_unix(sudo:session): session closed for user root
Feb 16 19:53:30 SDRsetup sudo[1165]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all →
Feb 16 19:53:30 SDRsetup sudo[1165]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=998)
Feb 16 19:53:30 SDRsetup sudo[1165]: pam_unix(sudo:session): session closed for user root
Feb 16 19:53:30 SDRsetup piaware[850]: ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good
Feb 16 19:53:30 SDRsetup piaware[850]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost →
Feb 16 19:53:30 SDRsetup piaware[850]: Started faup1090 (pid 1168) to connect to dump1090-fa
Feb 16 19:53:30 SDRsetup piaware[850]: UAT support disabled by local configuration setting: uat-receiver-type
Feb 16 19:53:30 SDRsetup piaware[850]: piaware received a message from dump1090-fa!
Feb 16 19:53:30 SDRsetup piaware[850]: logged in to FlightAware as user guest
Feb 16 19:53:30 SDRsetup piaware[850]: my feeder ID is [HIDDEN]
Feb 16 19:53:30 SDRsetup piaware[850]: site statistics URL: Site 192551 ADSB-B Feeder Statistics - FlightAware
Feb 16 19:53:31 SDRsetup piaware[850]: piaware has successfully sent several msgs to FlightAware!
Feb 16 19:54:01 SDRsetup piaware[850]: 304 msgs recv’d from dump1090-fa; 302 msgs sent to FlightAware
Feb 16 19:54:42 SDRsetup piaware[850]: timed out waiting for alive message from FlightAware, reconnecting…
Feb 16 19:54:42 SDRsetup piaware[850]: reconnecting in 6 seconds…
Feb 16 19:54:48 SDRsetup piaware[850]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 16 19:54:49 SDRsetup piaware[850]: Connection with adept server at piaware.flightaware.com/1200 established
Feb 16 19:54:49 SDRsetup piaware[850]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Feb 16 19:54:49 SDRsetup piaware[850]: FlightAware server certificate validated
Feb 16 19:54:49 SDRsetup piaware[850]: encrypted session established with FlightAware
Feb 16 19:54:49 SDRsetup sudo[2708]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all →
Feb 16 19:54:49 SDRsetup sudo[2708]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=998)
Feb 16 19:54:49 SDRsetup sudo[2708]: pam_unix(sudo:session): session closed for user root
Feb 16 19:54:50 SDRsetup piaware[850]: logged in to FlightAware as user guest
Feb 16 19:54:50 SDRsetup piaware[850]: my feeder ID is [HIDDEN]
Feb 16 19:54:50 SDRsetup piaware[850]: site statistics URL: Site 192551 ADSB-B Feeder Statistics - FlightAware
Feb 16 19:59:01 SDRsetup piaware[850]: 2118 msgs recv’d from dump1090-fa (1814 in last 5m); 2077 msgs sent to FlightAware

pi@SDRsetup:~ $ sudo journalctl -u piaware -b | grep “logged in”
grep: in”: No such file or directory

pi@SDRsetup:~ $ sudo journalctl -u piaware -b | grep msgs
Feb 16 19:53:31 SDRsetup piaware[850]: piaware has successfully sent several msgs to FlightAware!
Feb 16 19:54:01 SDRsetup piaware[850]: 304 msgs recv’d from dump1090-fa; 302 msgs sent to FlightAware
Feb 16 19:59:01 SDRsetup piaware[850]: 2118 msgs recv’d from dump1090-fa (1814 in last 5m); 2077 msgs sent to FlightAware
////////////////////////////////////////////////////////////////////

If I click the ADS-B Feeder statistics I can see data is being sent, but for some reason it still does not show up on the claim page.
I also notice the nearest airport is incorrect, despite the correct coordinates are set in dump1090-fa.

abcd567 · February 16, 2023, 8:41pm

If you are unable to use the automatic claim feature, please contact ADS-B Support.

adsbsupport@flightaware.com
Subject: Manually Claim PiAware

eric1tran · February 17, 2023, 2:40pm

Try the direct claim link while logged into your FA account

https://flightaware.com/adsb/piaware/claim/

keukenrol · February 17, 2023, 4:36pm

That is what i mentioned multiple times without success… got support via mail and it works now.

Looking at the interface, it seems the pi only uses an ipv6 wan address while flightaware is looking for ipv4. I think the clue lies here. Worth investigating? Both pi’s use the same ISP.

system · February 17, 2024, 4:36pm

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Piaware: permission denied FlightAware	0	326	February 14, 2023
Failed to read / can’t open / permission denied ADS-B Flight Tracking	10	2917	February 6, 2023
Piaware connection time out (no syn,ack reply from server) ADS-B Flight Tracking	1	386	December 23, 2021
PiAware Site 5252 is not currently sending live flight data to FlightAware ADS-B Flight Tracking	2	734	February 27, 2023
V3.81 new user failed to claim feed ADS-B Flight Tracking	6	845	May 30, 2020

Piaware: permission denied

Claim your PiAware client on FlightAware

ALTERNATIVELY CLAIM BY FOLLOWING METHOD

Related topics