Cuberite service unable to start

Troubleshooting
1

Hi All

Following the most recent update to DietPi I installed Cuberite, the service refuses to start with an error code of 1. Upon tying to start the service/executable myself I get the following error:

./Cuberite: /lib/arm-linux-gnueabihf/libc.so.6 version `GLIBC_2.28’ not found (required by ./Cuberite)

I’ve confirmed it’s there but likely a wrong version. Anyone else seeing this problem as well?

2

Hi,

many thanks for your report. Pls can you post following output

dpkg -l libc6
ls -l /lib/arm-linux-gnueabihf | grep libc
3

dietpi@DietPi-EXP:/mnt/dietpi_userdata/cubrite$ dpkg -l libc6
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description ================================================================================================
ii libc6:armhf 2.24-11+deb9u4 armhf GNU C Library: Shared libraries

…

ls -l /lib/arm-linux-gnueabihf | grep libc
-rwxr-xr-x 1 root root 1234700 Feb 6 2019 libc-2.24.so
lrwxrwxrwx 1 root root 18 Jul 6 2016 libcap-ng.so.0 → libcap-ng.so.0.0.0
-rw-r–r-- 1 root root 17988 Jul 6 2016 libcap-ng.so.0.0.0
lrwxrwxrwx 1 root root 14 May 24 2016 libcap.so.2 → libcap.so.2.25
-rw-r–r-- 1 root root 17916 May 24 2016 libcap.so.2.25
-rw-r–r-- 1 root root 181868 Feb 6 2019 libcidn-2.24.so
lrwxrwxrwx 1 root root 15 Feb 6 2019 libcidn.so.1 → libcidn-2.24.so
lrwxrwxrwx 1 root root 17 Sep 26 2019 libcom_err.so.2 → libcom_err.so.2.1
-rw-r–r-- 1 root root 9568 Sep 26 2019 libcom_err.so.2.1
-rw-r–r-- 1 root root 30276 Feb 6 2019 libcrypt-2.24.so
lrwxrwxrwx 1 root root 22 May 9 2017 libcryptsetup.so.4 → libcryptsetup.so.4.7.0
-rw-r–r-- 1 root root 143648 May 9 2017 libcryptsetup.so.4.7.0
lrwxrwxrwx 1 root root 16 Feb 6 2019 libcrypt.so.1 → libcrypt-2.24.so
lrwxrwxrwx 1 root root 12 Feb 6 2019 libc.so.6 → libc-2.24.so

…
● cuberite.service - Cuberite Server (DietPi)
Loaded: loaded (/etc/systemd/system/cuberite.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-05-14 02:59:31 BST; 3min 9s ago
Process: 1175 ExecStart=/mnt/dietpi_userdata/cubrite/Cuberite --service (code=exited, status=1/FAILURE)

May 14 02:59:31 DietPi-EXP systemd[1]: Starting Cuberite Server (DietPi)…
May 14 02:59:31 DietPi-EXP systemd[1]: cuberite.service: Control process exited, code=exited status=1
May 14 02:59:31 DietPi-EXP systemd[1]: Failed to start Cuberite Server (DietPi).
May 14 02:59:31 DietPi-EXP systemd[1]: cuberite.service: Unit entered failed state.
May 14 02:59:31 DietPi-EXP systemd[1]: cuberite.service: Failed with result ‘exit-code’.
…
dietpi@DietPi-EXP:/mnt/dietpi_userdata/cubrite$ ./Cuberite
./Cuberite: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28’ not found (required by ./Cuberite)

4

looks like you have installed version GLIBC 2.24 but Cuberite is expecting GLIBC 2.28

ii libc6:armhf 2.24-11+deb9u4 armhf GNU C Library: Shared libraries
lrwxrwxrwx 1 root root 12 Feb 6 2019 libc.so.6 -> libc-2.24.so

pls can you try running

apt update
apt upgrade

Afterwads you can check if version changed to GLIBC 2.28

5

Joulinar schafferm
Same here, I installed after updating to latest Dietpi 6.30.0, it doesn’t start with status=1/FAILURE

Mine appears to be v2.24 also. I ran apt-update and apt-upgrade and it still shows v2.24 and still fails. At first and second glance, response is identical before and after to:
dpkg -l libc6
ls -l /lib/arm-linux-gnueabihf | grep libc

6

Are you running Debian Stretch? As far as I can see libc6 is on 2.24 running Stretch and 2.28 running Buster.

Package libc6
jessie (oldoldstable) (libs): 2.19-18+deb8u10: amd64 armel armhf i386
stretch (oldstable) (libs): 2.24-11+deb9u4: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
buster (stable) (libs): 2.28-10: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
bullseye (testing) (libs): 2.30-7: amd64 arm64 armel armhf i386 mips64el mipsel ppc64el s390x
7

Hi

You are correct, I’m on stretch - Tried Dist-upgrade but that didn’t get me to buster… time to reflash unless anyone has any other ideas?

8

It is generally not recommended to do distro (Debian) major version upgrades. In most cases it works well, perhaps some manual config adjustments required but nothing urgent. But in rare cases issues CAN be much larger. For this reason no distro would ever automate this upgrade, nor support it, neither we de.

If you want to take the risk, you can have a look to: https://dietpi.com/forum/t/qbittorrent-version-shipping-with-dietpi/2326/9

9

I’ve been putting off the Buster upgrade. Is Bullseye close (XU4)?

10

I don’t expect official release of Debian Bullseye before mid of 2021. Means no DietPi support until official release was done. Therefore the Debian version of choice should be Buster.