Readsb update error

JRG1956 · September 12, 2022, 7:33am

@wiedehopf, I got the following error after running the readsb update script yesterday:

sudo bash -c "$(wget -O - https://github.com/wiedehopf/adsb-scripts/raw/master/readsb-install.sh)"

All done! Webinterface available at http://192.168.124.104/tar1090
--------------
--------------
-- Logs begin at Thu 2019-02-14 21:11:58 AEDT, end at Sun 2022-09-11 13:06:36 AEST. --
Aug 11 09:55:18 raspi4-2 systemd[1]: Started readsb ADS-B receiver.
Aug 11 09:55:18 raspi4-2 readsb[503]: Thu Aug 11 09:55:18 2022 AEST  readsb starting up.
Aug 11 09:55:18 raspi4-2 readsb[503]: readsb version: wiedehopf git: b1f77e7 (committed: Sun Jul 3 06:46:11 2022 0200)
Aug 11 09:55:18 raspi4-2 readsb[503]: Using lat:  -38.29xx, lon:  144.39xx
Aug 11 09:55:18 raspi4-2 readsb[503]: 30002: Raw TCP output port            30005: Beast TCP output port
Aug 11 09:55:18 raspi4-2 readsb[503]: 30003: SBS TCP output ALL port        30004: Beast TCP input port
Aug 11 09:55:18 raspi4-2 readsb[503]: 30104: Beast TCP input port
Aug 12 06:40:55 raspi4-2 readsb[503]: Beast TCP output: Couldn't flush data for 1.00s (Insufficient bandwidth?): disconnecting: 192.168.124.197 port 33738 (fd 24, SendQ 3812)
Sep 11 13:06:26 raspi4-2 readsb[503]: Sun Sep 11 13:06:26 2022 AEST  Caught SIGTERM, shutting down...
Sep 11 13:06:26 raspi4-2 systemd[1]: Stopping readsb ADS-B receiver...
Sep 11 13:06:26 raspi4-2 readsb[503]: Sun Sep 11 13:06:26 2022 AEST  Normal exit.
Sep 11 13:06:26 raspi4-2 systemd[1]: readsb.service: Succeeded.
Sep 11 13:06:26 raspi4-2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 11 13:06:26 raspi4-2 systemd[1]: Started readsb ADS-B receiver.
Sep 11 13:06:26 raspi4-2 readsb[11399]: Sun Sep 11 13:06:26 2022 AEST  readsb starting up.
Sep 11 13:06:26 raspi4-2 readsb[11399]: readsb version: wiedehopf git: d809bd8 (committed: Wed Sep 7 13:47:41 2022 0200)
Sep 11 13:06:26 raspi4-2 readsb[11399]: Using lat:  -38.29xx, lon:  144.39xx
Sep 11 13:06:26 raspi4-2 readsb[11399]: 30002: Raw TCP output port
Sep 11 13:06:26 raspi4-2 readsb[11399]: 30005: Beast TCP output port
Sep 11 13:06:26 raspi4-2 readsb[11399]: 30003: SBS TCP output ALL port
Sep 11 13:06:26 raspi4-2 readsb[11399]: 30004: Beast TCP input port
Sep 11 13:06:26 raspi4-2 readsb[11399]: 30104: Beast TCP input port
Sep 11 13:06:26 raspi4-2 systemd[1]: readsb.service: Main process exited, code=killed, status=7/BUS
Sep 11 13:06:26 raspi4-2 systemd[1]: readsb.service: Failed with result 'signal'.
--------------
--------------
ERROR: readsb service didn't start.
       common issues: SDR not plugged in.
       the webinterface will show an error until readsb is running!
       If you can't fix the issue:
            Open a github issue or contact wiedehopf on the adsbexchange discord and post the above 30 lines of log!

This was on a 4GB Raspi4B running a fully updated version of RasPi OS Buster (32 bit applications on a 64 bit kernel) and the latest airspy_adsb fed from an Airspy Mini.

Rebooting, running the readsb update script again and power cycling the RasPi all failed to clear the problem.

I resolved the problem by swapping the SD card with one that had the latest 64 bit version of Bullseye installed plus readsb, tar1090 and nginx. (I had been meaning to do this for a while, but the RasPi is mounted on the aerial pole so changing the card involves ladders and screwdrivers to remove it from its weatherproof enclosure.)

I don’t need a fix now, but am posting this in case it isn’t something that was unique to my setup, and anyone else runs into the same problem.

wiedehopf · September 12, 2022, 8:27am

https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb#debugging-memory-issues

Could you try this please? (just added it)
(should give more info, the current log only shows SIGBUS … hard to guess the issue)

JRG1956 · September 12, 2022, 9:13am

The 4GB Raspi 4B with the new Bullseye SD card is back up on the sand dune attached to the antenna pole, so I can’t easily test the setup that had the error.

I ran the commands on that RasPi anyway. They worked without error.

I have the old SD card running Buster, etc. in a spare 1GB Raspi 4B (I still need to transfer the graphs1090 history across), so I ran the same command on it as well:

All done! Webinterface available at http://192.168.124.197/tar1090
--------------
--------------
Sep 12 06:59:19 raspi4-2 readsb[5553]: Using lat:  -38.2962, lon:  144.3911
Sep 12 06:59:19 raspi4-2 readsb[5553]: 30002: Raw TCP output port
Sep 12 06:59:19 raspi4-2 readsb[5553]: 30005: Beast TCP output port
Sep 12 06:59:19 raspi4-2 readsb[5553]: 30003: SBS TCP output ALL port
Sep 12 06:59:19 raspi4-2 readsb[5553]: 30004: Beast TCP input port
Sep 12 06:59:19 raspi4-2 readsb[5553]: 30104: Beast TCP input port
Sep 12 06:59:19 raspi4-2 systemd[1]: readsb.service: Main process exited, code=killed, status=7/BUS
Sep 12 06:59:19 raspi4-2 systemd[1]: readsb.service: Failed with result 'signal'.
Sep 12 06:59:23 raspi4-2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 12 06:59:23 raspi4-2 systemd[1]: Started readsb ADS-B receiver.
Sep 12 06:59:23 raspi4-2 readsb[5626]: Mon Sep 12 06:59:23 2022 AEST  readsb starting up.
Sep 12 06:59:23 raspi4-2 readsb[5626]: readsb version: wiedehopf git: d809bd8 (committed: Wed Sep 7 13:47:41 2022 0200)
Sep 12 06:59:23 raspi4-2 readsb[5626]: Using lat:  -38.2962, lon:  144.3911
Sep 12 06:59:23 raspi4-2 readsb[5626]: 30002: Raw TCP output port
Sep 12 06:59:23 raspi4-2 readsb[5626]: 30005: Beast TCP output port
Sep 12 06:59:23 raspi4-2 readsb[5626]: 30003: SBS TCP output ALL port
Sep 12 06:59:23 raspi4-2 readsb[5626]: 30004: Beast TCP input port
Sep 12 06:59:23 raspi4-2 readsb[5626]: 30104: Beast TCP input port
Sep 12 06:59:23 raspi4-2 readsb[5626]: AddressSanitizer:DEADLYSIGNAL
Sep 12 06:59:23 raspi4-2 readsb[5626]: =================================================================
Sep 12 06:59:23 raspi4-2 readsb[5626]: ==5626==ERROR: AddressSanitizer: BUS on unknown address 0xf4b0dd01 (pc 0xf76fc30c bp 0x00000001 sp 0xf12fd5c0 T5)
Sep 12 06:59:24 raspi4-2 readsb[5626]:     #0 0xf76fc30b  (/usr/lib/arm-linux-gnueabihf/libzstd.so.1+0x1d30b)
Sep 12 06:59:24 raspi4-2 readsb[5626]: AddressSanitizer can not provide additional info.
Sep 12 06:59:24 raspi4-2 readsb[5626]: SUMMARY: AddressSanitizer: BUS (/usr/lib/arm-linux-gnueabihf/libzstd.so.1+0x1d30b)
Sep 12 06:59:24 raspi4-2 readsb[5626]: Thread T5 created by T0 here:
Sep 12 06:59:24 raspi4-2 readsb[5626]:     #0 0x4a127 in __interceptor_pthread_create (/usr/bin/readsb+0x4a127)
Sep 12 06:59:24 raspi4-2 readsb[5626]:     #1 0x1b7cdb in threadCreate /usr/local/share/adsb-wiki/readsb-install/git/util.c:262
Sep 12 06:59:24 raspi4-2 readsb[5626]: ==5626==ABORTING
Sep 12 06:59:24 raspi4-2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
Sep 12 06:59:24 raspi4-2 systemd[1]: readsb.service: Failed with result 'exit-code'.
--------------
--------------
ERROR: readsb service didn't start.
       common issues: SDR not plugged in.
       the webinterface will show an error until readsb is running!
       If you can't fix the issue:
            Open a github issue or contact wiedehopf on the adsbexchange discord and post the above 30 lines of log!

Don’t know if this is of any use.

wiedehopf · September 12, 2022, 9:17am

Limited.
Might be related to your 64 / 32 bit mix.
I can’t reproduce it on bullseye 32 and 64 bit.
But i don’t run any mix any more.

cat /etc/os-release
dpkg --print-architecture
sudo apt search libzstd1

Wait … now i’m confused, one of them is working?
The one that initially didn’t work?

But that does make me think of something.
I should backup the old binary if it exists and copy it back if it doesn’t work.

JRG1956 · September 12, 2022, 9:30am

Yes - the pi that originally had the problem, that is now working with a new SD card with Bullseye:

jrg@raspi4-3:~ $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
jrg@raspi4-3:~ $ dpkg --print-architecture
arm64
jrg@raspi4-3:~ $ sudo apt search libzstd1
Sorting... Done
Full Text Search... Done
libzstd1/stable,now 1.4.8+dfsg-2.1 arm64 [installed]
  fast lossless compression algorithm

My spare Raspi with the SD card and Buster OS that had the error, still has an error - note it does not have a receiver attached:

jrg@raspi4-2:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
jrg@raspi4-2:~ $ dpkg --print-architecture
armhf
jrg@raspi4-2:~ $ sudo apt search libzstd1
[sudo] password for jrg: 
Sorting... Done
Full Text Search... Done
libzstd1/oldstable,now 1.3.8+dfsg-3+rpi1+deb10u2 armhf [installed]
  fast lossless compression algorithm

wiedehopf · September 12, 2022, 10:46am

Yeah the receiver part doesn’t matter really.

The issue is that the error is with a library and it’s pretty unspecific.
Not sure how to debug that … i believe it normally works fine on jessie / buster.
I suppose you could try reinstalling libzstd1

sudo apt install --reinstall libzstd1

abcd567 · September 12, 2022, 5:39pm

Default architectures of Raspberry Pi OS (formerly Raspbian)

32-bit Raspberry Pi OS

$ dpkg --print-architecture 
armhf

$ dpkg --print-foreign-architectures 

$

64-bit Raspberry Pi OS is multi-arch by default

$ dpkg --print-architecture 
arm64

$ dpkg --print-foreign-architectures 
armhf

$

JRG1956 · September 12, 2022, 10:43pm

I reinstalled libzstd1 and ran the debug commands again. Got the same error:

Sep 12 19:44:54 raspi4-2 readsb[12577]: AddressSanitizer:DEADLYSIGNAL
Sep 12 19:44:54 raspi4-2 readsb[12577]: =================================================================
Sep 12 19:44:54 raspi4-2 readsb[12577]: ==12577==ERROR: AddressSanitizer: BUS on unknown address 0xf4c0a101 (pc 0xf781930c bp 0x00000001 sp 0xf0ffe5c0 T5)
Sep 12 19:44:54 raspi4-2 readsb[12577]:     #0 0xf781930b  (/usr/lib/arm-linux-gnueabihf/libzstd.so.1+0x1d30b)
Sep 12 19:44:54 raspi4-2 readsb[12577]: AddressSanitizer can not provide additional info.
Sep 12 19:44:54 raspi4-2 readsb[12577]: SUMMARY: AddressSanitizer: BUS (/usr/lib/arm-linux-gnueabihf/libzstd.so.1+0x1d30b)
Sep 12 19:44:54 raspi4-2 readsb[12577]: Thread T5 created by T0 here:
Sep 12 19:44:54 raspi4-2 readsb[12577]:     #0 0x4a577 in pthread_create (/usr/bin/readsb+0x4a577)
Sep 12 19:44:54 raspi4-2 readsb[12577]:     #1 0x1be4db in threadCreate /usr/local/share/adsb-wiki/readsb-install/git/util.c:262
Sep 12 19:44:54 raspi4-2 readsb[12577]: ==12577==ABORTING
Sep 12 19:44:54 raspi4-2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
Sep 12 19:44:54 raspi4-2 systemd[1]: readsb.service: Failed with result 'exit-code'.

As nobody else has reported an issue, it is probably safe to assume that my setup was an edge case and it is not worth pursuing.

Thanks for looking at it.

JRG1956 · September 13, 2022, 12:57am

@abcd567 my OS with the problem is “non standard” it runs the buster 64 bit kernel, but all the packages are 32 bit:

jrg@raspi4-2:~ $ uname -a
Linux raspi4-2 5.10.103-v8+ #1529 SMP PREEMPT Tue Mar 8 12:26:46 GMT 2022 aarch64 GNU/Linux

To enable this you need to run rbi-update. You can then swap from 32 bit to 64 bit by editing the /boot/config.txt line and rebooting:

change arm_64bit=0 to arm_64bit=1 (or vice versa)

In theory running the 64 bit kernel gave slightly better performance…

Anyway, it is not an issue now as I have moved to 64 bit bullseye, which as you point out should run 32 bit (armhf) packages as a foreign architecture by default.

However, I discovered that installing feeders on 64bit bullseye isn’t as simple as that:

As you know, Piaware will not install - I had to install the 64bit beta from your GitHub repository
https://github.com/abcd567a/rpi/blob/master/README.md

Can I add my thank to all the others who benefit from your contributions to this and other forums.

Plane Finder will not install - I got the error. armhf depends on libc6 (>= 2.13-28)

I managed to fix this by running apt --fix-broken install

ADSB Exchange feeder installation had no problems - the only issue was that I needed to do bit of digging to work out how to transfer my feeder ID to the new install.

Postscript - The above helped me identify the readsb update error. See post to @wiedehopf below.

JRG1956 · September 13, 2022, 1:02am

@wiedehopf the problem appears to have been caused by running the 64 bit buster kernel.

I set arm_64bit=0 in /boot/config.txt and rebooted.

readsb was running normally after the reboot.

I ran the debug commands again - there were no errors.

abcd567 · September 13, 2022, 2:04am

CLICK ON IMAGE TO SEE LARGER SIZE

wiedehopf · September 13, 2022, 2:56am

Thanks for checking.

I’d try and fix the issue, but it’s not with readsb itself but rather a library.
And i gotta admit i’m not too familiar with the library stuff, it gets pretty complicated quickly.

Ok after some google: https://github.com/borgbackup/borg/issues/4891

This reads very very much the same.
Ok … now in case it’s an issue of the memory passed to the library i’ve made a small change.
Can you try again?
No need to run the debug thing … it’s not telling much.

JRG1956 · September 13, 2022, 3:08am

My problem with pfclient was that one of the armhf libraries was missing from my bullseye installation:

2022-09-12 12:55:40 (1.31 MB/s) - ‘pfclient_5.0.161_armhf.deb’ saved [1566910/1566910]

jrg@raspi4-3:~ $ sudo dpkg -i pfclient_5.0.161_armhf.deb
Selecting previously unselected package pfclient:armhf.
(Reading database ... 41210 files and directories currently installed.)
Preparing to unpack pfclient_5.0.161_armhf.deb ...
Unpacking pfclient:armhf (5.0.161) ...
dpkg: dependency problems prevent configuration of pfclient:armhf:
 pfclient:armhf depends on libc6 (>= 2.13-28).

dpkg: error processing package pfclient:armhf (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pfclient:armhf

sudo apt --fix-broken install was needed to complete the install and configuration of pfclient

jrg@raspi4-3:~ $ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  gcc-10-base:armhf krb5-locales libc6:armhf libcom-err2:armhf libcrypt1:armhf libgcc-s1:armhf libgssapi-krb5-2:armhf libidn2-0:armhf libk5crypto3:armhf libkeyutils1:armhf libkrb5-3:armhf
  libkrb5support0:armhf libnsl2:armhf libnss-nis:armhf libnss-nisplus:armhf libssl1.1:armhf libtirpc3:armhf libunistring2:armhf
Suggested packages:
  glibc-doc:armhf locales:armhf krb5-doc:armhf krb5-user:armhf
The following NEW packages will be installed:
  gcc-10-base:armhf krb5-locales libc6:armhf libcom-err2:armhf libcrypt1:armhf libgcc-s1:armhf libgssapi-krb5-2:armhf libidn2-0:armhf libk5crypto3:armhf libkeyutils1:armhf libkrb5-3:armhf
  libkrb5support0:armhf libnsl2:armhf libnss-nis:armhf libnss-nisplus:armhf libssl1.1:armhf libtirpc3:armhf libunistring2:armhf
0 upgraded, 18 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 5,350 kB of archives.
After this operation, 17.0 MB of additional disk space will be used.
Do you want to continue? [Y/n] y

I couldn’t find any references to this problem in relation to pfclient, but ran across the apt --fix-broken install command while searching for a solution and gave it a try on spec.

abcd567 · September 13, 2022, 3:13am

CLICK ON SCREENSHOTS TO SEE LARGER SIZE
CLICK AGAIN TO SEE FULL SIZE

Graphs installed only 10 minutes ago, Just started populating.

JRG1956 · September 13, 2022, 3:22am

Swapped back to arm_64bit=1 and rebooted, and then ran the updater again:

sudo bash -c "$(wget -O - https://github.com/wiedehopf/adsb-scripts/raw/master/readsb-install.sh)"

The error is still there:

Sep 13 13:13:04 raspi4-2 readsb[2696]: 30002: Raw TCP output port
Sep 13 13:13:04 raspi4-2 readsb[2696]: 30005: Beast TCP output port
Sep 13 13:13:04 raspi4-2 readsb[2696]: 30003: SBS TCP output ALL port
Sep 13 13:13:04 raspi4-2 readsb[2696]: AddressSanitizer:DEADLYSIGNAL
Sep 13 13:13:04 raspi4-2 readsb[2696]: =================================================================
Sep 13 13:13:04 raspi4-2 readsb[2696]: ==2696==ERROR: AddressSanitizer: BUS on unknown address 0xf500dd01 (pc 0xf7bc630c bp 0x00000001 sp 0xf19fd5c0 T5)
Sep 13 13:13:04 raspi4-2 readsb[2696]: 30004: Beast TCP input port
Sep 13 13:13:04 raspi4-2 readsb[2696]: 30104: Beast TCP input port
Sep 13 13:13:05 raspi4-2 readsb[2696]:     #0 0xf7bc630b  (/usr/lib/arm-linux-gnueabihf/libzstd.so.1+0x1d30b)
Sep 13 13:13:05 raspi4-2 readsb[2696]: AddressSanitizer can not provide additional info.
Sep 13 13:13:05 raspi4-2 readsb[2696]: SUMMARY: AddressSanitizer: BUS (/usr/lib/arm-linux-gnueabihf/libzstd.so.1+0x1d30b)
Sep 13 13:13:05 raspi4-2 readsb[2696]: Thread T5 created by T0 here:
Sep 13 13:13:05 raspi4-2 readsb[2696]:     #0 0x4a577 in __interceptor_pthread_create (/usr/bin/readsb+0x4a577)
Sep 13 13:13:05 raspi4-2 readsb[2696]:     #1 0x1be4db in threadCreate /usr/local/share/adsb-wiki/readsb-install/git/util.c:262
Sep 13 13:13:05 raspi4-2 readsb[2696]: ==2696==ABORTING
Sep 13 13:13:05 raspi4-2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
Sep 13 13:13:05 raspi4-2 systemd[1]: readsb.service: Failed with result 'exit-code'.
Sep 13 13:13:31 raspi4-2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 13 13:13:31 raspi4-2 systemd[1]: Started readsb ADS-B receiver.
Sep 13 13:13:31 raspi4-2 readsb[3791]: /usr/bin/readsb --net-only --lat -38.29620 --lon 144.39108 --max-range 360 --write-json-every 1 --net --net-heartbeat 60 --net-ro-size 1250 --net-ro-interval 0.05 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 2 --write-json /run/readsb --quiet
Sep 13 13:13:31 raspi4-2 readsb[3791]: Tue Sep 13 13:13:31 2022 AEST  readsb starting up.
Sep 13 13:13:31 raspi4-2 readsb[3791]: readsb version: wiedehopf git: e16d0d5 (committed: Tue Sep 13 04:52:37 2022 0200)
Sep 13 13:13:31 raspi4-2 readsb[3791]: Using lat:  -38.2962, lon:  144.3911
Sep 13 13:13:31 raspi4-2 readsb[3791]: 30002: Raw TCP output port
Sep 13 13:13:31 raspi4-2 readsb[3791]: 30005: Beast TCP output port
Sep 13 13:13:31 raspi4-2 readsb[3791]: 30003: SBS TCP output ALL port
Sep 13 13:13:31 raspi4-2 readsb[3791]: 30004: Beast TCP input port
Sep 13 13:13:31 raspi4-2 readsb[3791]: 30104: Beast TCP input port
Sep 13 13:13:31 raspi4-2 systemd[1]: readsb.service: Main process exited, code=killed, status=7/BUS
Sep 13 13:13:31 raspi4-2 systemd[1]: readsb.service: Failed with result 'signal'.
--------------
--------------
ERROR: readsb service didn't start.
       common issues: SDR not plugged in.
       the webinterface will show an error until readsb is running!
       If you can't fix the issue:
            Open a github issue or contact wiedehopf on the adsbexchange discord and post the above 30 lines of log!

wiedehopf · September 13, 2022, 3:24am

Just out of curiosity: one last time.

Anyhow i’ll probably file this under “library compiled for unaligned access but 64 bit kernel won’t allow that”.
Besides not using the library, not much i can do.
Thanks for checking all the stuff.

JRG1956 · September 13, 2022, 3:34am

Ran the updater again - same result. Should the commit number have changed from last time?

Sep 13 13:29:08 raspi4-2 readsb[16986]: 30002: Raw TCP output port
Sep 13 13:29:08 raspi4-2 readsb[16986]: 30005: Beast TCP output port
Sep 13 13:29:08 raspi4-2 readsb[16986]: 30003: SBS TCP output ALL port
Sep 13 13:29:08 raspi4-2 systemd[1]: readsb.service: Main process exited, code=killed, status=7/BUS
Sep 13 13:29:08 raspi4-2 systemd[1]: readsb.service: Failed with result 'signal'.
Sep 13 13:29:39 raspi4-2 systemd[1]: readsb.service: Service RestartSec=30s expired, scheduling restart.
Sep 13 13:29:39 raspi4-2 systemd[1]: readsb.service: Scheduled restart job, restart counter is at 34.
Sep 13 13:29:39 raspi4-2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 13 13:29:39 raspi4-2 systemd[1]: Started readsb ADS-B receiver.
Sep 13 13:29:39 raspi4-2 readsb[17284]: /usr/bin/readsb --net-only --lat -38.29620 --lon 144.39108 --max-range 360 --write-json-every 1 --net --net-heartbeat 60 --net-ro-size 1250 --net-ro-interval 0.05 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 2 --write-json /run/readsb --quiet
Sep 13 13:29:39 raspi4-2 readsb[17284]: Tue Sep 13 13:29:39 2022 AEST  readsb starting up.
Sep 13 13:29:39 raspi4-2 readsb[17284]: readsb version: wiedehopf git: e16d0d5 (committed: Tue Sep 13 04:52:37 2022 0200)
Sep 13 13:29:39 raspi4-2 readsb[17284]: Using lat:  -38.2962, lon:  144.3911
Sep 13 13:29:39 raspi4-2 readsb[17284]: 30002: Raw TCP output port
Sep 13 13:29:39 raspi4-2 readsb[17284]: 30005: Beast TCP output port
Sep 13 13:29:39 raspi4-2 readsb[17284]: 30003: SBS TCP output ALL port
Sep 13 13:29:39 raspi4-2 readsb[17284]: 30004: Beast TCP input port
Sep 13 13:29:39 raspi4-2 readsb[17284]: 30104: Beast TCP input port
Sep 13 13:29:39 raspi4-2 systemd[1]: readsb.service: Main process exited, code=killed, status=7/BUS
Sep 13 13:29:39 raspi4-2 systemd[1]: readsb.service: Failed with result 'signal'.
Sep 13 13:30:03 raspi4-2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 13 13:30:03 raspi4-2 systemd[1]: Started readsb ADS-B receiver.
Sep 13 13:30:03 raspi4-2 readsb[17978]: /usr/bin/readsb --net-only --lat -38.29620 --lon 144.39108 --max-range 360 --write-json-every 1 --net --net-heartbeat 60 --net-ro-size 1250 --net-ro-interval 0.05 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 2 --write-json /run/readsb --quiet
Sep 13 13:30:03 raspi4-2 readsb[17978]: Tue Sep 13 13:30:03 2022 AEST  readsb starting up.
Sep 13 13:30:03 raspi4-2 readsb[17978]: readsb version: wiedehopf git: e16d0d5 (committed: Tue Sep 13 04:52:37 2022 0200)
Sep 13 13:30:03 raspi4-2 readsb[17978]: Using lat:  -38.2962, lon:  144.3911
Sep 13 13:30:03 raspi4-2 readsb[17978]: 30002: Raw TCP output port
Sep 13 13:30:03 raspi4-2 readsb[17978]: 30005: Beast TCP output port
Sep 13 13:30:03 raspi4-2 systemd[1]: readsb.service: Main process exited, code=killed, status=7/BUS
Sep 13 13:30:03 raspi4-2 systemd[1]: readsb.service: Failed with result 'signal'.
--------------
--------------
ERROR: readsb service didn't start.
       common issues: SDR not plugged in.
       the webinterface will show an error until readsb is running!
       If you can't fix the issue:
            Open a github issue or contact wiedehopf on the adsbexchange discord and post the above 30 lines of log!

wiedehopf · September 13, 2022, 3:41am

JRG1956:

Should the commit number have changed from last time?

Sep 13 13:29:08 raspi4-2 readsb[16986]: 30002: Raw TCP output port
Sep 13 13:29:08 raspi4-2 readsb[16986]: 30005: Beast TCP output port
Sep 13 13:29:08 raspi4-2 readsb[16986]: 30003: SBS TCP output ALL port
Sep 13 13:29:08 raspi4-2 systemd[1]: readsb.service: Main process exited, code=killed, status=7/BUS
Sep 13 13:29:08 raspi4-2 systemd[1]: readsb.service: Failed with result 'signal'.
Sep 13 13:29:39 raspi4-2 systemd[1]: readsb.service: Service RestartSec=30s expired, scheduling restart.
Sep 13 13:29:39 raspi4-2 systemd[1]: readsb.service: Scheduled restart job, restart counter is at 34.
Sep 13 13:29:39 raspi4-2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 13 13:29:39 raspi4-2 systemd[1]: Started readsb ADS-B receiver.
Sep 13 13:29:39 raspi4-2 readsb[17284]: /usr/bin/readsb --net-only --lat -38.29620 --lon 144.39108 --max-range 360 --write-json-every 1 --net --net-heartbeat 60 --net-ro-size 1250 --net-ro-interval 0.05 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 2 --write-json /run/readsb --quiet
Sep 13 13:29:39 raspi4-2 readsb[17284]: Tue Sep 13 13:29:39 2022 AEST  readsb starting up.
Sep 13 13:29:39 raspi4-2 readsb[17284]: readsb version: wiedehopf git: e16d0d5 (committed: Tue Sep 13 04:52:37 2022 0200)
Sep 13 13:29:39 raspi4-2 readsb[17284]: Using lat:  -38.2962, lon:  144.3911
Sep 13 13:29:39 raspi4-2 readsb[17284]: 30002: Raw TCP output port

Nah, compile parameter.

But yeah i didn’t think it would help, issue is inside the library i have no influence on it.
That library just won’t run with a 64bit kernel. The way it’s been compiled is incompatible.

obj · September 13, 2022, 4:10am

(From digging through related comments in github:)

The point here is that the default gcc-8 compiler pretends that the system can handle unaligned accesses (which the 64bit kernel cannot)

womp womp. that seems kinda terrible.

Then again:

This is a minor hotfix for v1.4.7, where an internal buffer unalignment bug was detected by @bmwiedemann .
The issue is of no consequence for x64 and arm64 targets, but could become a problem for cpus relying on strict alignment, such as mips or older arm designs.

github.com/facebook/zstd

1.4.7 dictionary tests fail on i586 and s390x

opened 07:03AM - 17 Dec 20 UTC

closed 02:00AM - 18 Dec 20 UTC

bmwiedemann

bug

**Describe the bug** dictionary tests fail on i586 and s390x **To Reproduce*…* Steps to reproduce the behavior: 1. on openSUSE or Debian do 2. osc checkout Archiving/zstd && cd $_ 2. osc build --vm-type=kvm -j1 --clean openSUSE_Factory i586 **Expected behavior** tests should pass the same way they did in 1.4.5 **Screenshots and charts** build log: ``` ===> dictionary tests - test with raw dict (content only) - Create first dictionary ! Warning : data size of samples too small for target dictionary size ! Samples should be about 100x larger than target dictionary size Loading /home/abuild/rpmbuild/BUILD/zstd-1.4.7/tests/../programs/zstdcli.c... ^M^M ^MTrying 5 different sets of parameters WARNING: The maximum dictionary size 112640 is too large compared to the source size 688542! size(source)/size(dictionary) = 6.112766, but it should be >= 10! This may lead to a subpar dictionary! We recommend training on sources at least 10x, and preferably 100x the size of the dictionary! HUF_writeCTable error Failed to select dictionary HUF_writeCTable error Failed to select dictionary HUF_writeCTable error Failed to select dictionary HUF_writeCTable error Failed to select dictionary HUF_writeCTable error Failed to select dictionary ^Mdictionary training failed : Error (generic) make: *** [Makefile:330: test-zstd] Error 1 ``` **Desktop:** - OS: openSUSE-Tumbleweed - Version 20201215 - Compiler gcc10 - Flags `-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects` - Build system: Makefile **Additional context** [How openSUSE builds](https://github.com/bmwiedemann/openSUSE/blob/master/packages/z/zstd/zstd.spec#L93) Current build logs can be found at https://build.opensuse.org/package/live_build_log/Archiving/zstd/openSUSE_Factory/i586

debian ships 1.4.7: Debian -- Details of package libzstd-dev in bullseye

abcd567 · September 13, 2022, 4:25am

Topic		Replies	Views
Did I do something stupid ADS-B Flight Tracking	29	829	June 8, 2022
Airspy - Readsb Combo error messages ADS-B Flight Tracking	4	455	March 24, 2023
PiAware Beast-Format Results Error ADS-B Flight Tracking	8	3955	March 4, 2016
New Error since update to 4.0 ADS-B Flight Tracking	4	501	November 17, 2021
Dump 1090 Errors ADS-B Flight Tracking	12	2418	July 2, 2020

Readsb update error

Default architectures of Raspberry Pi OS (formerly Raspbian)

Related Topics