Hello techie enthusiasts.
I have been uploading to Fr24, Planefinder and Flightaware for a few weeks, trouble free and very satisfactory. Then, while trying to enable some features, I messed up my settings while editing config files, and after trying to sort things out via console commands (I am a total linux dud) I decided the best thing to do, would be to remove dump1090-fa and piaware and purge the files and directories involved.
Then when I reinstalled the packages, FR24 and Planefinder worked fine, uploading and recognising my data, but my flightaware page shows no uploading (or at least not recognised as my uploading).
I made sure that my unique identifier (share code) was available to piaware, and used commands to test piaware status. The status enquiry shows that my feeder is connected and uploading to flightaware and that it knows my unique identifier, but still no recognition on my ADSB feeder page. Red boxes and no acknowledgement. The piaware status enquiry gives this response:
pi@pi24-bookworm:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 17245.
PiAware ADS-B client (faup1090) is running with pid 17262.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-fa) is running with pid 667.
dump1090-fa (pid 667) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.
dump1090 is producing data on localhost:30005.
Your feeder ID is b8027f41-b12e-48de-aa79 [ I edited this ID code for security] (from /var/cache/piaware/feeder_id)
pi@pi24-bookworm:
Does anyone have a clue how I can mend this broken setup?
It looks to me as if somehow the problem may not be on my system, but on the flightaware site.
Thanks in advance for any suggestions you can make.
Tony
