Debian Bookworm kills piaware.service minutes after starting

[butterfly2]

Hi Eric

any update to the new bookworm repository?

Reading package lists... Done
E: The repository 'http://flightaware.com/adsb/piaware/files/packages bookworm Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.


Ign:6 http://www.flightaware.com/adsb/piaware/files/packages bookworm InRelease
Err:7 http://www.flightaware.com/adsb/piaware/files/packages bookworm Release
  404  Not Found [IP: 2606:4700:4400::6812:27c9 80]


pi@flightrecorder:/etc/apt/sources.list.d$ cat flightaware-apt-repository.list
# This file is automatically generated by the flightaware-apt-repository package
# to point to the correct FlightAware repository for the currently installed Debian OS.
deb http://flightaware.com/adsb/piaware/files/packages bookworm piaware

There is connectivity

pi@flightrecorder:/etc/apt/sources.list.d$ telnet 2606:4700:4400::6812:27c9 80
Trying 2606:4700:4400::6812:27c9...
Connected to 2606:4700:4400::6812:27c9.
Escape character is '^]'.

There doesn’t seems to be a release file?

[obj]

@butterfly2

any update to the new bookworm repository?

We have not released bookworm packages for piaware yet.

probably will happen this week, but not guaranteed.

[butterfly2]

Thanks! Few other flight tracking sites are neither ready yet so I moved back to the old SDcard.

Will there be 64bit support in the future?

[obj]

Yes, planning to release armhf + arm64 packages for bullseye and bookworm.

[abcd567]

@butterfly2

Few other flight tracking sites are neither ready yet

(1) First step is is to wait till the Raspberry Pi OS Bookworm gets fixed.
It has a USB bug, which causes dump1090-fa and rtl_test to fail to detect / use the dongle.

(2) After fixing the USB bug, I could install dump1090-fa and piaware, as well as Flightradar24, Planefinder, and Radarbox24 feeders because the Raspberry Pi OS is multi architecture (arm64/aarch64 AND armhf)

Click on Screenshot to See Larger Size

 

[butterfly2]

@abcd567 your such a value for this community, many thanks for sharing your knowledge. I’ll fire up the pi 3b+ (where ill move the SD card tot the pi4 after install) and start testing with the commands you shared.

What I did was moving my bullseye 32bits install to a bookworm 64bits install. I’m using an airspy and 2 RTL-SDR dongles for VHF. Indeed the airspy worked fine but the rlt_test had major issues with communicating to the RTL-SDR dongle. And as I dont want to get gaps on my graphs1090 I did not run it for hours. At least my local TAR1090 showed airplanes via the airspy.

Is there any bypass for the USB problems? We might need to wait for the USB issue is solved, is there any tracking available? Are you able to ping this thread when its released?

Due to the USB load of the Airspy combined with 2 RTL-SDR’s i need to increase the usbfs_memory

pi@flightrecorder:~ $ cat usb_buffer.sh
#!/bin/sh
PCM_ID="/sys/module/usbcore/parameters/usbfs_memory_mb"
BUFSIZE="0"

# Adjust usbfs memory
if [ -f $PCM_ID ]; then
        echo $BUFSIZE > $PCM_ID
fi

If I do understand well, I need to add the foreign architectures to get the packages installed well. What is your vision about some excotic sites which does not really have an active package development. I’m thinking about removing them when I move to the new install:

Opensky: last update 2018
adsbhub bash script
radarvirtuel.com executable

[butterfly2]

Well booted up and tested some things, found some other post of you.

Why Not Use 64-bit OS on RPi Model 3 and 4?

Why not switch to 64-bit OS on RPi 3 & 4? The 64-bit is future of computing. Raspberry Pi has started 64-bit capable processor armv8l since RPi model 3. They have made available 64-bit version (beta) of Raspberry Pi OS since May 2020. DietPi and Ubuntu have also followed the suite and have released 64-bit versions for RPi. I strongly recommend to use a SPARE microSD card to write the 64-bit image, and preserve existing microSD card with 32-bit OS and feeders as backup. This way if something go…

Let me handle them step by step looking for tips and providing you a fresh view on new installs today.

apt-cache policy piaware | grep Installed
apt-cache policy fr24feed | grep Installed
Installed: 1.0.41-0
apt-cache policy mlat-client | grep Installed
apt-cache policy rbfeeder | grep Installed
apt-cache policy pfclient | grep Installed
Installed: 5.0.161

MLAT-CLIENT

pi@flightrecorder:~ $ sudo apt install mlat-client
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package mlat-client

There seems no mlat-client for bookworm availably your site doesn’t show an bookworm version?

RBFEEDER

Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.SI2MYNfRd5/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 1D043681
gpg: key D4F914061D043681: "AirNav Systems <jceara@airnavsystems.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
Don't know how to install for a distribution named




case "$VERS" in
    stretch)
        echo 'deb https://apt.rb24.com/ stretch main' > /etc/apt/sources.list.d/rb24.list
        ;;

     buster)
        echo 'deb https://apt.rb24.com/ buster main' > /etc/apt/sources.list.d/rb24.list
        ;;

     bullseye)
        echo 'deb https://apt.rb24.com/ bullseye main' > /etc/apt/sources.list.d/rb24.list
        ;;

     *)
        echo "Don't know how to install for a distribution named $DIST" >&2
        exit 1
esac

As it seems the script logic could not handle the bookworm output gathered, should I change the script to match bookworm and install bullseye?

     bookworm)
        echo 'deb https://apt.rb24.com/ bullseye main' > /etc/apt/sources.list.d/rb24.list
        ;;

And yes that change worked fine:

pi@flightrecorder:~ $ apt-cache policy rbfeeder | grep Installed
  Installed: 1:1.0.8+deb11.1

PIWARE

Ign:6 http://www.flightaware.com/adsb/piaware/files/packages bookworm InRelease
Err:7 http://www.flightaware.com/adsb/piaware/files/packages bookworm Release
  404  Not Found [IP: 2606:4700:4400::6812:27c9 80]
Reading package lists... Done

As stated earlier in this topic, package will be released soon

apt-cache policy piaware | grep Installed
apt-cache policy mlat-client | grep Installed
apt-cache policy fr24feed | grep Installed
  Installed: 1.0.41-0
apt-cache policy pfclient | grep Installed
  Installed: 5.0.161
apt-cache policy rbfeeder | grep Installed
  Installed: 1:1.0.8+deb11.1

[abcd567]

@butterfly2

Please see following thread for hack to fix USB bug in current release of RaspberryPi OS Bookworm (10-10-2023)

Raspberry Pi OS Bookworm released

 

[abcd567]

@butterfly2

RBFEEDER

Don't know how to install for a distribution named

wget http://apt.rb24.com/inst_rbfeeder.sh

sudo nano inst_rbfeeder.sh  

Scroll down till you see line which starts with VERS=lsb_release

 

Just below this line, add VERS=bullseye
CAUTION: Do NOT leave any blank space on either side of = sign.

 

Save file, and issue following command

sudo bash inst_rbfeeder.sh   

The above command will start and complete installation of Radarbox24 feeder on Bookworm

 

@butterfly2

MLAT-CLIENT

pi@flightrecorder:~ $ sudo apt install mlat-client
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package mlat-client

For RadarBox24 feeder, build mlat-client from source code, dev branch ver 0.2.13, which is compatible to Bookworm

sudo apt update  
sudo apt install -y git curl build-essential debhelper 
sudo apt install -y python3 python3-dev dh-python 

git clone https://github.com/mutability/mlat-client   

cd mlat-client  

git fetch --all
git reset --hard origin/dev  

sudo dpkg-buildpackage -b -uc   

## After mlat client  package is built

cd .. /

sudo dpkg -i mlat-client_*.deb  

 

[abcd567]

@butterfly2

PIWARE

Ign:6 http://www.flightaware.com/adsb/piaware/files/packages bookworm InRelease
Err:7 http://www.flightaware.com/adsb/piaware/files/packages bookworm Release
  404  Not Found [IP: 2606:4700:4400::6812:27c9 80]
Reading package lists... Done

As stated earlier in this topic, package will be released soon

Run following script on Bookworm. It will install piaware ver 9.0~dev on Bookworm.

sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu-debian-amd64/master/install-piaware.sh)"

 

[butterfly2]

Thanks in the end it failed, just to let you know how your script runs.

Successfully installed MlatClient-0.2.13
make -C dump978 faup978 VERSION=9.0~dev
make[2]: Entering directory '/home/pi/piaware_builder/package-bookworm/dump978'
g++ -g -O2 -ffile-prefix-map=/home/pi/piaware_builder/package-bookworm=. -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall -Wno-psabi -Werror -O2 -g -Ilibs -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"9.0~dev\"  -c -o faup978_main.o faup978_main.cc
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [<builtin>: faup978_main.o] Error 1
make[2]: Leaving directory '/home/pi/piaware_builder/package-bookworm/dump978'
make[1]: *** [debian/rules:73: build_dump978] Error 2
make[1]: Leaving directory '/home/pi/piaware_builder/package-bookworm'
make: *** [debian/rules:116: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
[ERROR] Error in line 121 when executing: dpkg-buildpackage -b --no-sign
[ERROR] Error in line 26 when executing: sudo bash -c "$(wget -O - https://github.com/abcd567a/temp/raw/main/install-piaware-debian-12.sh)"

[abcd567]

@butterfly2

g++ -g -O2 -ffile-prefix-map=/home/pi/piaware_builder/package-bookworm=. -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall -Wno-psabi -Werror -O2 -g -Ilibs -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"9.0~dev\"  -c -o faup978_main.o faup978_main.cc
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [<builtin>: faup978_main.o] Error 1
make[2]: Leaving directory '/home/pi/piaware_builder/package-bookworm/dump978'
make[1]: *** [debian/rules:73: build_dump978] Error 2
make[1]: Leaving directory '/home/pi/piaware_builder/package-bookworm'
make: *** [debian/rules:116: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

@obj

Yesterday I have successfully built piaware ver 9.0~dev using Flightaware source-code, and it was OK.

After seeing @butterfly2’s post, I just now tried to build it again, and it failed exactly like it failed with @butterfly2 .

Checked source-code at Flightaware Repository.
Found some changes have been made in the dev branch of Github/Flightaware/Piaware_builder about 3 hrs ago, which seem to cause this failure.

 

Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion 2 sensible-build.sh

@@ -86,7 +86,7 @@ shallow_clone https://github.com/flightaware/tcllauncher.git v1.10 $OUTDIR/tclla

shallow_clone https://github.com/flightaware/dump1090.git dev $OUTDIR/dump1090

shallow_clone https://github.com/mutability/mlat-client.git dev $OUTDIR/mlat-client

shallow_clone https://github.com/mutability/mlat-client.git v0.2.13 $OUTDIR/mlat-client

shallow_clone https://github.com/flightaware/dump978.git dev $OUTDIR/dump978

 

[obj]

@butterfly2

g++: fatal error: Killed signal terminated program cc1plus

You ran out of memory. Build on a machine with more memory, or add swap.

[abcd567]

@obj

Build on a machine with more memory, or add swap

@butterfly2
Please see following post for method to add swap.
If the total memory (RAM + builtin swapfile (if any) + your added swap file) is 2.5 GB or larger, then piaware, dump1090-fa and dump978-fa pckages will built without any memory issue.

After building and installing the packages (piaware, dump1090-fa, dump978-fa), you can delete the swap file you have added to free up space on microSD card.

 

Trouble with PiAware 8.2 on Ubuntu 20.04 Installed on Odroid N2

I found an easy method of solving memory shortage on my OrangePiPC, running Armbian Bullseye. It has 1 GB RAM and 0.5 GB swap, i.e. total 1.5 GB which proved insufficient to build dump978-fa from source-code. As my microSD card has enough free space, I decided to create a 1 GB swap file, making total memory 2.5 GB (1 GB RAM + 0.5 GB original swap + 1 GB swap file created by me). With this arrtangement I could build dump978-fa. ORIGINAL MEMORY Click on screenshot to see larger size [image] …

[abcd567]

@obj

Up till October 21, 2023, I have several times built piaware ver 9.0~dev successfully on RPi OS Bookworm and Armbian OS Bookworm.

Today I tried again to build piaware 9.0~dev on RPi Model 4 with 4GB RAM, and it failed with following error:

make[1]: *** [debian/rules:92: install_mlat-client] Error 1
make[1]: Leaving directory '/home/pi/piaware_builder/package-bookworm'
make: *** [debian/rules:116: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

 

Click on Screenshot to see larger Size

 

 

[obj]

@abcd567

Today I tried again to build piaware 9.0~dev on RPi Model 4 with 4GB RAM, and it failed with following error:

Well, OK, but you said you had the same error. That’s not the same error, and you haven’t given enough context to diagnose the problem.

Our CI environment builds the current dev branch OK on both bookworm armhf and bookworm arm64.

edit: if you still have problems building please create a github issue with full logs.

[butterfly2]

Thanks @obj and @abcd567 as shared im building on a 3B+ because i don’t want the graph1090 stats to get filled with gaps. The Pi 4 has 8G and the 3b+ 1G if I recall well.

Will try to add swap and also noticed that there was some high CPU process running which consumes resources.

Thanks for the help!

[abcd567]

@obj

edit: if you still have problems building please create a github issue with full logs.

Finally found the problem! My install had some sort of corruption.

Last night, after seeing your post, I tried several times, but always build process aborted with same error message. Got fed up and went to sleep.

Today morning re-imaged RPi4 4GB ram, with 64-bit Raspberry Pi OS Lite Bookworm (2023-10-10).

Then to solve USB / Dongle detection issue, upgraded kernel to 6.1.58-v8+ by command sudo rpi-update.

After this ran the install scripts from my Github page, and all went well and could built & install:

• piaware 9.0~dev
• dump1090-fa 9.0~dev
• dump978-fa 9.0~dev
• piaware-web
  

https://www.flightaware.com/adsb/stats/user/abcd567#stats-76000

 

Click on Screenshot to see larger Size

 

[kmm0000]

Works for me on a Pi 5 without updating the firmware.

kmm0000 ADS-B Feeder Statistics - FlightAware

[abcd567]

@abcd567

Today I tried again to build piaware 9.0~dev on RPi Model 4 with 4GB RAM, and it failed with following error:

make[1]: *** [debian/rules:92: install_mlat-client] Error 1
make[1]: Leaving directory '/home/pi/piaware_builder/package-bookworm'
make: *** [debian/rules:116: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

@obj

Well, OK, but you said you had the same error. That’s not the same error, and you haven’t given enough context to diagnose the problem.

Last night I ended up in same error, but this time I could find what exactly caused above failure. It was failure of package building process to install following package:

./wheels/MlatClient-0.2.13-cp311-cp311-linux_aarch64.whl

The reason for failure was that I have built and installed mlat-client_0.2.13_arm64.deb for Radarbox24 feeder., and piaware build process detected it and failed to install its own mlat-client

The message given by dpkg-buildpackage -b command ` is given below:

/home/pi/piaware_builder/package-bookworm/debian/venv/bin/python -m pip install --no-index --no-deps --require-virtualenv /home/pi/piaware_builder/package-bookworm/wheels/MlatClient-*.whl
Processing ./wheels/MlatClient-0.2.13-cp311-cp311-linux_aarch64.whl
MlatClient is already installed with the same version as the provided wheel. Use --force-reinstall to force an installation of the wheel.

I solved this problem by following method:

sudo dpkg --purge mlat-client 

cd /home/pi/piaware_builder/package-bookworm

sudo dpkg-buildpackage -b

After uninstalling stand-alone mlat-client_0.2.13, the piaware package was built successfully.

After building piaware package, I reinstalled stand alone mlat-client for Radarbox24 feeder

sudo dpkg -i mlat-client_0.2.13_arm64.deb  

I have also noted that mlat-clients installed under virtual enviroments by adsbexchange and adsbfi do not cause this issue. It is only the stand-alone /usr/bin/mlat-client which caused this failure.
 
Click on Screenshot to See Larger Size