I am having trouble with piaware 8.2 after the update it gets killed for some reason.
Dump1090 works fine and I have a nice map with planes locally, but I am unable to feed to FlightAware for some reason.
Systemctl Staus output is below and I am on arm64 Debian Bookworm
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; preset: enabled)
Active: active (running) since Tue 2023-01-03 18:05:29 GMT; 2s ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 1029 (piaware)
Tasks: 2 (limit: 1046)
Memory: 5.7M
CPU: 933ms
CGroup: /system.slice/piaware.service
└─1029 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
Jan 03 18:05:29 ADSB-Receiver systemd[1]: Started FlightAware ADS-B uploader.
Jan 03 18:05:29 ADSB-Receiver piaware[1029]: creating pidfile /run/piaware/piaware.pid
Jan 03 18:05:29 ADSB-Receiver piaware[1029]: ****************************************************
Jan 03 18:05:29 ADSB-Receiver piaware[1029]: piaware version 8.2 is running, process ID 1029
Jan 03 18:05:29 ADSB-Receiver piaware[1029]: your system info is: Linux ADSB-Receiver 6.0.0-6-arm64 #1 SMP Debian 6.0.12-1 (2022-12-09) aarch64 GNU/Linux
Jan 03 18:05:29 ADSB-Receiver piaware[1029]: GPS: Connected to gpsd 3.22 at localhost/2947
Jan 03 18:05:30 ADSB-Receiver piaware[1029]: gpsd reported location: 50.0000, 0.00000, 24m (WGS84)
Jan 03 18:05:31 ADSB-Receiver piaware[1029]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jan 03 18:05:31 ADSB-Receiver piaware[1029]: Connection with adept server at piaware.flightaware.com/1200 established
Anybody else got this wierd issue?
This also affects piaware 7.2 as well, because it was the reason why I upgrade to 8.2 as I thought it might fix the problem.
I installed Debian12 (Bookworm)Testing on my VM using Alpha-1 netinstaller (debian-bookworm-DI-alpha1-amd64-netinst.iso), and installed dump1090-fa 8.2 and piaware 8.2.
Results were identical to yours.
Yesterday I removed the Debian 12 Bookworm Testing OS. Downloaded new copy of Alpha-1 netinstaller iso, then installed it again using new copy of Alpha-1 netinstaller. Next I installed dump1090-fa 8.2 and piaware 8.2. Got the exact same failure again.
Finally uninstalled Debian12 Bookworm Testing from VM
I have checked with Journalctl and this is on constant repeat
Jan 03 19:18:42 ADSB-Receiver systemd[1]: Started FlightAware ADS-B uploader.
Jan 03 19:18:42 ADSB-Receiver systemd[1]: piaware.service: Consumed 1.082s CPU time.
Jan 03 19:18:42 ADSB-Receiver systemd[1]: Stopped FlightAware ADS-B uploader.
Jan 03 19:18:42 ADSB-Receiver systemd[1]: piaware.service: Scheduled restart job, restart counter is at 171.
Jan 03 19:18:11 ADSB-Receiver systemd[1]: piaware.service: Consumed 1.082s CPU time.
Jan 03 19:18:11 ADSB-Receiver systemd[1]: piaware.service: Failed with result 'signal'.
Jan 03 19:18:11 ADSB-Receiver systemd[1]: piaware.service: Main process exited, code=killed, status=6/ABRT
Jan 03 19:18:11 ADSB-Receiver piaware[1866]: SpellFix: programming error
Jan 03 19:18:11 ADSB-Receiver piaware[1866]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Jan 03 19:18:11 ADSB-Receiver piaware[1866]: Connection with adept server at piaware.flightaware.com/1200 established
Jan 03 19:18:10 ADSB-Receiver piaware[1866]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jan 03 19:18:10 ADSB-Receiver piaware[1866]: gpsd reported location: 50.00000, 0.00000, 10m (WGS84)
Jan 03 19:18:09 ADSB-Receiver piaware[1866]: GPS: Connected to gpsd 3.22 at localhost/2947
Jan 03 19:18:09 ADSB-Receiver piaware[1866]: your system info is: Linux ADSB-Receiver 6.0.0-6-arm64 #1 SMP Debian 6.0.12-1 (2022-12-09) aarch64 GNU/Linux
Jan 03 19:18:09 ADSB-Receiver piaware[1866]: piaware version 8.2 is running, process ID 1866
Jan 03 19:18:09 ADSB-Receiver piaware[1866]: ****************************************************
Jan 03 19:18:09 ADSB-Receiver piaware[1866]: creating pidfile /run/piaware/piaware.pid
Does piaware has a log file which I could look into?
Unfortunately I have deleted the Bookworm from my VM on Windows, so I cannot post journalctl output, but I remember to get similar constant repeats when ran journalctl -u piaware , and following Error messages
piaware.service: Main process exited, code=killed, status=6/ABRT SpellFix: programming error
I dont know what is cause of this failure.
Flightaware staff @obj and @eric1tran may shed some light.
Currently I am using Debian11.6 (Bullseye) AMD64, with Piaware v8.2, without any issue, to feed one of my stations.
When Bookworm SID’s issue will be solved by Flightaware, I will switch to it
By the way, to build the piaware and dump1090-fa packages from Flightaware’s source code, I use the automated install script, which I have written and posted on Github. It makes life easy for repeatitive job.
Well, we can work around this specific issue, but the breakage is upstream so we’re limited in how much can be fixed.
It’d be appreciated if someone running bookworm and seeing the issue can submit a Debian bug report against the itcl debian package (the breakage is in itcl 3.4.4). Here is a bug report against the original itcl itself: Itcl - the [incr Tcl] extension: View Ticket
Thank you for filing a new Bug report with Debian.
You can follow progress on this Bug here: 1027932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027932.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Debian Tcl/Tk Packagers <pkg-tcltk-devel@lists.alioth.debian.org>
If you wish to submit further information on this problem, please
send it to 1027932@bugs.debian.org.
Please do not send mail to owner@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
--
1027932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027932
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
As a interim workaround for all those who are on Debian Bookworm,
add “bullseye main” to /etc/apt/sources.list and then install itcl3 3.4.3 with “sudo apt install itcl3=3.4.3-3.1” now mark itcl3 as hold with “sudo apt-mark hold itcl3” to prevent apt from upgrading itcl3.
Piaware is now worinkg again, but without MLAT as the workaround breaks the fa-mlat-client.
Good news, Debian has fixed the SpellFix error in itcl 3.4.4-2
Source: itcl3
Source-Version: 3.4.4-2
Done: Sergei Golovan
We believe that the bug you reported is fixed in the latest version of
itcl3, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1027932@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sergei Golovan (supplier of updated itcl3 package)
Changes:
itcl3 (3.4.4-2) unstable; urgency=medium
.
* Revert the change which ports Itcl 3 to Tcl 8.7 because it breaks
abbreviations in namespaces like [info exist var]
(closes: #1027932, #1027857).
Can I manually update cx_Freeze to 6.13 before building piaware?
I have seen in sensible-build.sh (line 154-156) that the script downloads cx_Freeze 6.8.3, but which file path to target?
Maybe this could fix the MLAT issue?
But when you look in the folder package-bullseye there is a subfolder freeze-mlat-client and I don’t know there this comes from.
As I tried to manually extend sensible-build.sh with an entry for bookworm it wouldn’t download importlib, zipp and cf_Freeze at all.
So I downloaded the latest versions manually and the build failed as zipp-0.5.0 is hardcoded somethere and also a patch seems to be applied to importlib_metadata-4.3.1 and zipp-0.5.0, renaming the folders to match expected old versions does not work either.
Also downloading the old versions of zipp and importlib_metadata and just updating cx_Freeze does not compile either, even with renaming cx_Freeze to match 6.8.3, it does not compile.