Any news on an offical PiAware version of Bookworm yet?
So found this thread as I was busy trying to move my setup to Bookworm
Thankfully I have 2 Raspberry Pis and did a clean install to a new one of Bookworm
My new Setup is:
Raspberry Pi 4 Model B Rev 1.1 with v12 Bookworm latest version installed
I came looking for some help in copying across my setup to the new environment (much like you can do with PiHole and Teleporter that will back up all the settings
My Old setup currently working and feeding data is on Buster
I discovered that Raspberry Pi Connect is not available on my install and there is no ‘elegant’ upgrade path to go from Buster to latest 64-bit Bookworm
It appears that Flightaware will not work on Buster - is that true and if so I will just pause this process.
However I still want to upgrade and would want to move my settings - is that possible and if so can anyone guide me on the steps and process to do this?
Thanks
it works fine on buster. thats what I am on at the moment.
you should be able to use flightaware on bookworm though but no piaware image available as yet…
the instructions here say you can install flightaware on bookworm however.
Thanks @conligwx does that mean that the details in this thread regarding the USB challenges do not apply. I have to look up what receiver I bought and plugged in to confirm make/model etc
FA works fine on Bookworm with a package installation of the FA software.
I have multiple setups running that way.
Just install the OS first using the raspberry Pi imager and then proceed with the installation steps listed in the linked page above.
Normally you would encounter no problems.
I only had problems when I used Bookworm Noble. That image isn’t available through the Raspberry Pi imager so that problem won’t come your way when you use the Raspberry Pi software.
3 Likes
I do believe that somebody active in the forum even provided a nominal bash script for the few steps you describe (post-imaging as you describe), where one could plug in the UUID for one’s site.
2 Likes
After writing image, inserting microSD card in Pi, and powering up Pi, do following:
OPTION-1:
You can manually run following command one by one in the same order given below
OR
OPTION-2:
You can creat & run a script file as follows:
(2.1) Creare a blank file by following command
sudo nano install-flightaware.sh
(2.2) In the new blanlk file created by above command, copy-paste the commands listed below, and save file.
(2.3) Run the file by following command
sudo bash install-flightaware.sh
Manual commands / Code for script
wget https://www.flightaware.com/adsb/piaware/files/packages/pool/piaware/f/flightaware-apt-repository/flightaware-apt-repository_1.2_all.deb
sudo dpkg -i flightaware-apt-repository_1.2_all.deb
sudo apt update
sudo apt install dump1090-fa
sudo apt install piaware
sudo apt install piaware-web
sudo piaware-config feeder-id xxxxxxxxxxxx
## Replace xxxxxxxxxxxxx by your actual unique identifier / uuid / feeder-id
## Uncomment following commands if you live in USA and want to install 978 mhz uat receiver.
# sudo apt install dump978-fa
# sudo piaware-config uat-receiver-type sdr
# sudo sed -i 's/^RECEIVER_SERIAL=.*/RECEIVER_SERIAL=00001090/' /etc/default/dump1090-fa
# sudo sed -i 's/driver=rtlsdr[^ ]* /driver=rtlsdr,serial=00000978 /' /etc/default/dump978-fa
sudo reboot
3 Likes
Thanks for the info. much appreciated
So in my attempt to create a Bookworm-64 new install. I looked at the /adsbfi site locally and it appeared to be working with data on the right and planes displayed
And it showed connected/working
Left it overnight only to receive a notification of
PiAware Receiver Site XXXXXX Data Outage
So I followed the script above in case I had missed anything in my install
Now I don’t see anything on the adsbfi page suggesting I have nothing working
I am very lost at this point and unsure of what to follow to troubleshoot
This page was not very helpful with the FAQs
Would greatly appreciate some troubleshooting steps to get this working so I can move to Bookworm-64
Thanks
To debug your issue, more information is needed. As a first step, please post outputs of following two commands:
sudo journalctl -u piaware -n 15 |tee
sudo journalctl -u dump1090-fa -n 10 |tee
Piaware:
Oct 16 12:51:30 raspberrypi2 sudo[29977]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 16 12:51:30 raspberrypi2 sudo[29977]: pam_unix(sudo:session): session closed for user root
Oct 16 12:51:30 raspberrypi2 piaware[1590]: no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
Oct 16 12:51:43 raspberrypi2 sudo[30024]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Oct 16 12:51:43 raspberrypi2 sudo[30024]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 16 12:51:43 raspberrypi2 sudo[30024]: pam_unix(sudo:session): session closed for user root
Oct 16 12:51:43 raspberrypi2 piaware[1590]: no ADS-B data program seen listening on port 30978 for 250 seconds, next check in 60s
Oct 16 12:52:14 raspberrypi2 sudo[30103]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Oct 16 12:52:14 raspberrypi2 sudo[30103]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 16 12:52:14 raspberrypi2 sudo[30103]: pam_unix(sudo:session): session closed for user root
Oct 16 12:52:14 raspberrypi2 piaware[1590]: no ADS-B data program is serving on port 30005, not starting multilateration client yet
Oct 16 12:52:30 raspberrypi2 sudo[30135]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Oct 16 12:52:30 raspberrypi2 sudo[30135]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 16 12:52:31 raspberrypi2 sudo[30135]: pam_unix(sudo:session): session closed for user root
Oct 16 12:52:31 raspberrypi2 piaware[1590]: no ADS-B data program seen listening on port 30005 for 71 seconds, next check in 60s
dump1090
Oct 16 12:52:51 raspberrypi2 systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Oct 16 12:53:21 raspberrypi2 systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 327.
Oct 16 12:53:21 raspberrypi2 systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 12:53:21 raspberrypi2 systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 12:53:21 raspberrypi2 dump1090-fa[30284]: Wed Oct 16 12:53:21 2024 EDT dump1090-fa 9.0 starting up.
Oct 16 12:53:21 raspberrypi2 dump1090-fa[30284]: rtlsdr: no device matching ‘00001090’ found.
Oct 16 12:53:21 raspberrypi2 dump1090-fa[30284]: rtlsdr: found 1 device(s):
Oct 16 12:53:21 raspberrypi2 dump1090-fa[30284]: 0: Realtek, RTL2832U, SN: 1090
Oct 16 12:53:21 raspberrypi2 systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Oct 16 12:53:21 raspberrypi2 systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
And the piaware status report for good measure
PiAware master process (piaware) is running with pid 1611.
PiAware ADS-B client (faup1090) is running with pid 1861.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is running with pid 2510.
Local ADS-B receiver (dump1090) is not running.
Local ADS-B UAT receiver (dump978) is not running.
readsb (pid 768) is listening for ES connections on port 30005.
no program appears to be listening for UAT connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
got ‘couldn’t open socket: connection refused’
dump978 is NOT producing data on localhost:30978.
dump1090 is producing data on localhost:30005.
Your feeder ID is MYFEEDERID (configured at /etc/piaware.conf:9)
Probably should not publicize your feeder ID.
1 Like
Don’t run dump1090-fa and readsb.
Use one of those.
If you’re fine using readsb, just rerun the readsb install script it’ll remove dump1090-fa.
Probably you just have 2 sites (2 feeder ids).
This is not an issue but one of them will show offline.
https://www.flightaware.com/adsb/stats/user/nickvt#stats-222095
Reason for failure
The dump1090-fa failed to start because of serial number mismatch.
Dongle serial number = 1090
Serial number set in file /etc/fefault/dump1090-fa = 00001090
REMEDY:
(1) Open file by following command
sudo nano /etc/default/dump1090-fa
(2) Scroll down till you see following
(3) Remove 0000 from 00001090 so that it becomes 1090, like below:
(4) Save (Ctrl+O) and close (Ctrl+x) the file
(5) Restart dump1090-fa
sudo systemctl restart dump1090-fa
(6) Wait for 5 minutes then check status of dump1090-fa and piaware
sudo systemctl status dump1090-fa
sudo systemctl status piaware
1 Like
Thanks @abcd567
Slightly confused with conflicting advice from @wiedehopf who said uninstall dump1090 which I did too quickly and then had to rerun the install script
Then added the receiver serial and restarted
dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2024-10-16 14:17:51 EDT; 23s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 4768 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, status=1/FAILURE)
Main PID: 4768 (code=exited, status=1/FAILURE)
CPU: 52ms
AND
piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-10-16 14:06:41 EDT; 6min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 1605 (piaware)
Tasks: 4 (limit: 3909)
CPU: 12.122s
CGroup: /system.slice/piaware.service
├─1605 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─1864 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 39.085 --lon -77.150
└─2731 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,lo>
Oct 16 14:12:46 raspberrypi2 sudo[3823]: pam_unix(sudo:session): session closed for user root
Oct 16 14:12:46 raspberrypi2 piaware[1605]: attempting to start dump978-fa using 'systemctl --no-block restart dump978-fa.service < /dev/nul>
Oct 16 14:12:46 raspberrypi2 sudo[3828]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/systemctl --no-block restart dump978-fa.service
Oct 16 14:12:46 raspberrypi2 sudo[3828]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 16 14:12:46 raspberrypi2 sudo[3828]: pam_unix(sudo:session): session closed for user root
Oct 16 14:12:46 raspberrypi2 piaware[1605]: dump978 start appears to have been successful
Oct 16 14:12:56 raspberrypi2 sudo[3871]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Oct 16 14:12:56 raspberrypi2 sudo[3871]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 16 14:12:56 raspberrypi2 sudo[3871]: pam_unix(sudo:session): session closed for user root
Oct 16 14:12:56 raspberrypi2 piaware[1605]: no ADS-B data program seen listening on port 30978 for 10 seconds, next check in 60s
Hopefully no info I should not be posting in those two logs
Not conflicting at all.
You had both installed, removing either is what is certainly necessary.
Additionally the serial was misconfigured for dump1090-fa.
Did you install dump978-fa?
You only have one SDR, remove that.
And for good measure I rebooted just in case
piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-10-16 14:21:50 EDT; 4min 5s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 1608 (piaware)
Tasks: 4 (limit: 3909)
CPU: 8.238s
CGroup: /system.slice/piaware.service
├─1608 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─1861 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 39.085 --lon -77.150
└─2529 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loc>
Oct 16 14:23:54 raspberrypi2 sudo[2847]: pam_unix(sudo:session): session closed for user root
Oct 16 14:23:54 raspberrypi2 piaware[1608]: no ADS-B data program seen listening on port 30978 for 123 seconds, next check in 60s
Oct 16 14:24:54 raspberrypi2 sudo[3081]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Oct 16 14:24:54 raspberrypi2 sudo[3081]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 16 14:24:54 raspberrypi2 sudo[3081]: pam_unix(sudo:session): session closed for user root
Oct 16 14:24:54 raspberrypi2 piaware[1608]: no ADS-B data program seen listening on port 30978 for 183 seconds, next check in 60s
Oct 16 14:25:54 raspberrypi2 sudo[3262]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Oct 16 14:25:54 raspberrypi2 sudo[3262]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 16 14:25:54 raspberrypi2 sudo[3262]: pam_unix(sudo:session): session closed for user root
Oct 16 14:25:54 raspberrypi2 piaware[1608]: no ADS-B data program seen listening on port 30978 for 243 seconds, next check in 60s
dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2024-10-16 14:28:03 EDT; 5s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 3665 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, status=1/FAILURE)
Main PID: 3665 (code=exited, status=1/FAILURE)
CPU: 77ms
Is it time to start again with a new install and try and get this right?
So if you’re gonna go with dump1090-fa, do the following:
sudo systemctl disable --now readsb
sudo apt remove dump978-fa -y
sudo systemctl restart dump1090-fa
After that show the log for dump1090-fa:
sudo journalctl -u dump1090-fa -n100
Sticking with dump1090 and following the removal of readsb etc
Oct 16 14:38:38 raspberrypi2 systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 14:38:38 raspberrypi2 systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 14:38:38 raspberrypi2 dump1090-fa[5531]: Wed Oct 16 14:38:38 2024 EDT dump1090-fa 9.0 starting up.
Oct 16 14:38:38 raspberrypi2 dump1090-fa[5531]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 1090)
Oct 16 14:38:38 raspberrypi2 dump1090-fa[5531]: usb_claim_interface error -6
Oct 16 14:38:38 raspberrypi2 dump1090-fa[5531]: rtlsdr: error opening the RTLSDR device: Device or resource busy
Oct 16 14:38:38 raspberrypi2 systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Oct 16 14:38:38 raspberrypi2 systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Oct 16 14:39:09 raspberrypi2 systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 34.
Oct 16 14:39:09 raspberrypi2 systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 14:39:09 raspberrypi2 systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 14:39:09 raspberrypi2 dump1090-fa[5644]: Wed Oct 16 14:39:09 2024 EDT dump1090-fa 9.0 starting up.
Oct 16 14:39:09 raspberrypi2 dump1090-fa[5644]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 1090)
Oct 16 14:39:09 raspberrypi2 dump1090-fa[5644]: usb_claim_interface error -6
Oct 16 14:39:09 raspberrypi2 dump1090-fa[5644]: rtlsdr: error opening the RTLSDR device: Device or resource busy
Oct 16 14:39:09 raspberrypi2 systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Oct 16 14:39:09 raspberrypi2 systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Oct 16 14:39:39 raspberrypi2 systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 35.
Oct 16 14:39:39 raspberrypi2 systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 14:39:39 raspberrypi2 systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 14:39:39 raspberrypi2 dump1090-fa[5730]: Wed Oct 16 14:39:39 2024 EDT dump1090-fa 9.0 starting up.
Oct 16 14:39:39 raspberrypi2 dump1090-fa[5730]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 1090)
Oct 16 14:39:39 raspberrypi2 dump1090-fa[5730]: usb_claim_interface error -6
Oct 16 14:39:39 raspberrypi2 dump1090-fa[5730]: rtlsdr: error opening the RTLSDR device: Device or resource busy
Oct 16 14:39:39 raspberrypi2 systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Oct 16 14:39:39 raspberrypi2 systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Oct 16 14:40:09 raspberrypi2 systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 36.
Oct 16 14:40:09 raspberrypi2 systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 14:40:09 raspberrypi2 systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
Oct 16 14:40:09 raspberrypi2 dump1090-fa[5814]: Wed Oct 16 14:40:09 2024 EDT dump1090-fa 9.0 starting up.
Oct 16 14:40:09 raspberrypi2 dump1090-fa[5814]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 1090)
Oct 16 14:40:09 raspberrypi2 dump1090-fa[5814]: usb_claim_interface error -6
Oct 16 14:40:09 raspberrypi2 dump1090-fa[5814]: rtlsdr: error opening the RTLSDR device: Device or resource busy
Oct 16 14:40:09 raspberrypi2 systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Oct 16 14:40:09 raspberrypi2 systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Oct 16 14:40:39 raspberrypi2 systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 37.
Oct 16 14:40:39 raspberrypi2 systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).