Stuck/100% CPU getting version_manifest.json on RaspberryPi

[cconde]

Describe the problem

Raspberry Pi4 4GB keeps at the same point for more than two hours.

I've tested changing to TYPE:PAPER unsuccessfully.

I can ping launchermeta.mojang.com

I've been supervising network with Portainer stats for the container but doesn't seem to download anything. Just CPU between 300% and 400%. Volume /data only gets the eula.txt.

I'm not sure what to test more, any help?

Container definition

docker run -d -v minecraft_data:/data:z -p 25565:25565 -e EULA="true" -e ONLINE_MODE="false" -e MEMORY=750m -e DEBUG="true" --name minecraft itzg/minecraft-server

Container logs

+ export HOME=/data,�
+ HOME=/data,
++ id -u,
++ id -g,
++ ls -lnd /data,
+ log 'Running as uid=1000 gid=1000 with /data as '\''drwxrwxr-x 2 1000 1000 4096 Feb 20  2022 /data'\''',
+ local oldState,
++ shopt -po xtrace,
+ oldState='set -o xtrace',
+ shopt -u -o xtrace,
[init] 1970-03-01 15:58:51+00:00 Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 2 1000 1000 4096 Feb 20  2022 /data',
+ '[' '!' -e /data/eula.txt ']',
+ isTrue false,
+ local oldState,
++ shopt -po xtrace,
+ oldState='set -o xtrace',
+ shopt -u -o xtrace,
+ return 1,
+ isTrue false,
+ local oldState,
++ shopt -po xtrace,
+ oldState='set -o xtrace',
+ shopt -u -o xtrace,
+ return 1,
+ [[ -n '' ]],
+ [[ -n '' ]],
+ fixJavaPath,�
+ which java,
+ export VERSIONS_JSON=https://launchermeta.mojang.com/mc/game/version_manifest.json,
+ VERSIONS_JSON=https://launchermeta.mojang.com/mc/game/version_manifest.json,
+ case "X$VERSION" in,
++ get --json-path '$.latest.release' https://launchermeta.mojang.com/mc/game/version_manifest.json,
++ flags=(),
++ local flags,
++ isTrue false,
++ local oldState,
+++ shopt -po xtrace,
++ oldState='set -o xtrace',
++ shopt -u -o xtrace,
++ return 1,
++ mc-image-helper get --json-path '$.latest.release' https://launchermeta.mojang.com/mc/game/version_manifest.json

And nothing else for two hours

[itzg]

To test this a different way, try:

docker run -it --rm --entrypoint curl itzg/minecraft-server -v https://launchermeta.mojang.com/mc/game/version_manifest.json

[itzg]

@valentinfrlch can you try the curl test above in addition to the -e DEBUG_GET=true?

[valentinfrlch]

When running

docker run -it -e DEBUG_GET=true -e EULA=TRUE -e TYPE=PAPER --name minecraft -p 25565:25565 --entrypoint curl itzg/minecraft-server -v https://launchermeta.mojang.com/mc/game/version_manifest.json

I get:

* Closing connection 0
curl: (28) Timeout was reached

[itzg]

The log you posted for -e DEBUG_GET=true seems like the unrelated one at #1418 (comment)

[itzg]

As for

curl: (28) Timeout was reached

That sounds like it could be a DNS issue on that particular docker installation.

[valentinfrlch]

I found a solution (yet to test it myself) in another thread: #755 (comment)

[valentinfrlch]

Great news, it's working. Here's how (link in original solution no longer works):

Get signing keys to verify the new packages

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 04EE7237B7D453EC 648ACFD622F3D138

Add the Buster backport repository to apt sources.list

echo 'deb http://httpredir.debian.org/debian buster-backports main contrib non-free' | sudo tee -a /etc/apt/sources.list.d/debian-backports.list

Update and upgrade libseccomp2

sudo apt update
sudo apt install libseccomp2 -t buster-backports

[itzg]

Great find!

[valentinfrlch]

Thanks for all your help! I think we can now close this issue.