Failed to read / can’t open / permission denied


#1

Can someone help me?
I installed dump1090-mutability and it seems to be connected to flightaware and wending messages.
However I can’t acces the local web interface and it is givving read/open errors.
No problem wending data to plane Finder, local dump1090 map is working.
What am I doing wrong here?

this the log output from command piaware

pi@raspberrypi-emiel:/var/cache/piaware $ piaware
2017-12-18 08:01:25Z warning: /etc/piaware.conf: failed to read config file: couldn't open "/etc/piaware.conf": permission denied
2017-12-18 08:01:25Z failed to reopen /var/log/piaware.log: couldn't open "/var/log/piaware.log": permission denied
2017-12-18 08:01:25Z ****************************************************
2017-12-18 08:01:25Z piaware version 3.5.3 is running, process ID 3384
2017-12-18 08:01:25Z your system info is: Linux raspberrypi-emiel 4.9.59+ #1047 Sun Oct 29 11:47:10 GMT 2017 armv6l GNU/Linux
2017-12-18 08:01:27Z Connecting to FlightAware adept server at piaware.flightaware.com/1200
2017-12-18 08:01:27Z Connection with adept server at piaware.flightaware.com/1200 established
2017-12-18 08:01:28Z TLS handshake with adept server at piaware.flightaware.com/1200 completed
2017-12-18 08:01:28Z FlightAware server certificate validated
2017-12-18 08:01:28Z encrypted session established with FlightAware
2017-12-18 08:01:28Z warning: /etc/piaware.conf: failed to read config file: couldn't open "/etc/piaware.conf": permission denied
2017-12-18 08:01:30Z ADS-B data program 'dump1090-mutabi' is listening on port 30005, so far so good
2017-12-18 08:01:30Z Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
2017-12-18 08:01:30Z Started faup1090 (pid 3411) to connect to dump1090-mutabi
2017-12-18 08:01:31Z logged in to FlightAware as user katwijk
2017-12-18 08:01:31Z my feeder ID is 99ca8f01-9894-406b-99e6-adb2bf135479
2017-12-18 08:01:31Z Failed to update feeder ID file at /var/cache/piaware/feeder_id: couldn't open "/var/cache/piaware/feeder_id.new": permission denied
2017-12-18 08:01:31Z site statistics URL: https://flightaware.com/adsb/stats/user/katwijk#stats-70193
2017-12-18 08:01:31Z piaware received a message from dump1090-mutabi!
2017-12-18 08:01:34Z piaware has successfully sent several msgs to FlightAware!
2017-12-18 08:02:00Z 22 msgs recv'd from dump1090-mutabi; 22 msgs sent to FlightAware
^C2017-12-18 08:02:57Z piaware (process 3384) is shutting down because it received a shutdown signal (SIGINT) from the system...
2017-12-18 08:02:57Z faup1090 exited with SIG SIGINT
2017-12-18 08:02:57Z piaware (process 3384) is exiting...
pi@raspberrypi-emiel:/var/cache/piaware $ 

Thanks


#2

try ls -l /var/log/piawa*
and check the permissions.
Are you starting the process as superuser?


#3

I tried reinstalling everything and now use dump1090-fa / piaware
The local interface is working on port 8080 and it still connects to flightaware, however the same problem as above.

The output from the above command will give the following output:

pi@raspberrypi-emiel:~ $ ls -l /var/log/piawa* -rw-r----- 1 root adm 167221 Dec 19 08:36 /var/log/piaware.log

I should notice this is installed on the raspbian stretch lite image.
I just installed this with the user pi (changed pwd ofcourse) which is standard setup from the image. Don’t know if this is a superuser…

Any idee?

Edit: It is running now because I have set the feeder id manually with
sudo piaware-config feeder-id xxxxxxxxxxxxxxxxx

However I still get this strange problems

pi@raspberrypi-emiel:~ $ piaware
2017-12-19 08:03:55Z warning: /etc/piaware.conf: failed to read config file: couldn’t open “/etc/piaware.conf”: permission denied
2017-12-19 08:03:55Z failed to reopen /var/log/piaware.log: couldn’t open “/var/log/piaware.log”: permission denied
2017-12-19 08:03:55Z ****************************************************
2017-12-19 08:03:55Z piaware version 3.5.3 is running, process ID 860
2017-12-19 08:03:55Z your system info is: Linux raspberrypi-emiel 4.9.59+ #1047 Sun Oct 29 11:47:10 GMT 2017 armv6l GNU/Linux
2017-12-19 08:03:57Z Connecting to FlightAware adept server at piaware.flightaware.com/1200
2017-12-19 08:03:57Z Connection with adept server at piaware.flightaware.com/1200 established
2017-12-19 08:03:57Z TLS handshake with adept server at piaware.flightaware.com/1200 completed
2017-12-19 08:03:58Z FlightAware server certificate validated
2017-12-19 08:03:58Z encrypted session established with FlightAware
2017-12-19 08:03:58Z warning: /etc/piaware.conf: failed to read config file: couldn’t open “/etc/piaware.conf”: permission denied
2017-12-19 08:03:59Z ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good
2017-12-19 08:03:59Z Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 52.200 --lon 4.398
2017-12-19 08:03:59Z Started faup1090 (pid 915) to connect to dump1090-fa
2017-12-19 08:04:00Z adept reported location: 52.19994, 4.39787, 62ft AMSL
2017-12-19 08:04:00Z logged in to FlightAware as user katwijk
2017-12-19 08:04:00Z my feeder ID is faeb5c99-9b3f-417e-9269-b85a4571976d
2017-12-19 08:04:00Z Failed to update feeder ID file at /var/cache/piaware/feeder_id: couldn’t open “/var/cache/piaware/feeder_id.new”: permission denied
2017-12-19 08:04:00Z site statistics URL: https://flightaware.com/adsb/stats/user/katwijk#stats-63667
2017-12-19 08:04:00Z multilateration data requested
2017-12-19 08:04:00Z Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.254:6636:3465743775
2017-12-19 08:04:00Z piaware received a message from dump1090-fa!
2017-12-19 08:04:01Z piaware has successfully sent several msgs to FlightAware!
2017-12-19 08:04:01Z mlat-client(924): fa-mlat-client 0.2.10 starting up
2017-12-19 08:04:01Z mlat-client(924): Using UDP transport to 70.42.6.254 port 6636
2017-12-19 08:04:01Z mlat-client(924): Warning: Could not create results output ‘beast,listen,30105’: [Errno 98] Address already in use
2017-12-19 08:04:02Z mlat-client(924): Warning: Could not create results output ‘ext_basestation,listen,30106’: [Errno 98] Address already in use
2017-12-19 08:04:02Z mlat-client(924): Input connected to localhost:30005
2017-12-19 08:04:02Z mlat-client(924): Input format changed to BEAST, 12MHz clock
2017-12-19 08:04:02Z mlat-client(924): Beast-format results connection with ::1:30104: connection established
2017-12-19 08:04:30Z 39 msgs recv’d from dump1090-fa; 39 msgs sent to FlightAware


#4

Did you get it to work? I’m having similar problems. I started with Raspian stretch desktop. I get similar errors, even though it seems to be working. In my case I can’t get anything in the web browser, using any of options I read about (:8080/, :80/, etc.), the page comes up with the map but it just spins greyed out and never finishes, either on the pie or another PC on the LAN. I can’t paste the dump because this board thinks it needs to prevent me from including the links in the dump…

Thoughts?
Thanks, Scott


#5

I removed/purged all relevant packages including lighttpd.

Then used the web portal setup script

I still get the write/read errors when I run “piaware” from the terminal.
However it sends data just fine to flightaware/fr24/planefinder.
Also the web interface map from dump1090 is working.
(View here http://emiel1234.ddns.net/ )

I never found out what exactly went wrong.
And still don’t know why it gives the errors in the log.

Just left it with that since everything is working now.


#7

Thanks. Well, it’s the usual Linux/Open Source adventure. I tried so many things I’m not sure exactly how I got where I am, but it sort of works now. I used sudo chmod 777 on each directory or file called out in the error messages, and those messages went away. Mine was already working on FA at the time. Since then, I installed a GPS dongle, think I got it working with gpsd. I think the gpsd error messages went away too. I can now click on “view live data” and get my local feed at 192.168.1.8:8080, works locally and on my LAN. Not sure why that now works. I am tracking lots of planes, including some reported as MLAT, so I think even that may be working? But now (lol), my FA stats page reports I haven’t been connected in a day (even though my log says it’s working fine), reports estimated position and no MLAT. What the heck?!


#8

Interesting. Just tried the remote restart and reboot commands from the FA site, they don’t do anything.


#9

I think you have to enable that in the config file

$ sudo piaware-config allow-auto-updates yes
$ sudo piaware-config allow-manual-updates yes

#10

Thanks for the idea, I didn’t even know about that command. Anyway–it is mysteriously all working now, I manually rebooted the Pi and when it came back up, FA began reporting that it was receiving the updates, although it doesn’t credit all the stuff I sent the previous 24 hours. It reports working MLAT too! I again tried a remote upgrade, and this time that works, and status is showing. Who knows, all is good for now… :slight_smile: