Arch Linux User Repository

To get an overview of the available options provided by the management script, be sure to have a look at the help page or read the according section on the ArchWiki article [1].

You can quit the console without shutting down the server by press ctrl+a d (first ctrl+a and after releasing the buttons press d; ctrl+b also works). This will detach your input from the server console. The attaching and detaching is done with tmux (previously GNU screen) since it lets you view and type into the console, send single commands to it and keep it alive without a connected user. Take a look at the the command overview at the ArchWiki [2] to get a feel for its power. (@carmelo12341)

[1] https://wiki.archlinux.org/title/Minecraft#Setup [2] https://wiki.archlinux.org/title/Tmux

Hi, @edh, yes starting the server manually led me to the error, but that issue is resolved.

I think I am misunderstanding the dependencies on this package because java-runtime-headless>=16 has a list of possible packages to satisfy the dependency. However jre8-openjdk-headless is listed but does not work with the latest version of Minecraft (which is what I was using). I don't know how the large list with possible dependency candidates above is composed, perhaps this is out of your control.

@InFerNo

Yes, sorry, the log file would not have been conclusive. However, starting the server by hand would have told you as much. Or in other words, I don't think one can call this an error in the package.

Btw. the java dependency has long been java-runtime-headless>=16.

@edh, the logfile gets written by Minecraft, but if Minecraft can't start then it doesn't write anything to the logfile(s). It was the first thing I checked.

The package dependencies need to be updated, because versions lower than 16 will no longer work. At the very least they should be checked.

@InFerNo

The log file of your server could have probably told you so from the beginning.

Both ctrl+a and ctrl+b work so not much should have changed for the user. I updated the comment though to point to tmux and not screen.

edit: I fixed it by installing the latest openjdk (jre-openjdk-headless) version and setting it as the default: sudo archlinux-java set java-16-openjdk

The version that no longer works is jre8-openjdk-headless.

@edh, unfortunately running these commands made no change. The output was:

[user@host minecraft-server-old]$ sudo -u minecraft screen -S minecraft -rx
[sudo] password for user: 
There is no screen to be attached matching minecraft.

The same for idle_server_minecraft. BTW you should update the pinned comment too.

edit: I believe the issue is related to Java:

Exception in thread "main" java.lang.UnsupportedClassVersionError: net/minecraft/server/Main has been compiled by a more recent version of the Java Runtime (class file version 60.0), this version of the Java Runtime only recognizes class file versions up to 52.0

Version 60 = Java 16

@InFerNo

Very good point! I forgot to include the install file in the PKGBUILD :(

The message should have been:

The management script switched from GNU screen to tmux.
Manual intervention is needed to close the previous GNU screen sessions:
Use `sudo -u minecraft screen -S minecraft -rx` to attach to the minecraft session and stop it.
Do the same for the `idle_server_minecraft` session if one is running.

@edh

edit: here is my output, I see no instructions:

https://pastebin.com/LegNUqrH

@InFerNo The management script switched from GNU screen to tmux in the meantime. Did you follow the instructions that were printed after the upgrade?

I keep getting minecraftd[133901]: The corresponding tmux session for minecraft was already dead. How can I fix this? I upgraded from 1.16.5.

If you would like to use minecraftd console without entering your password to both enter and exit the console you need to add a line to your /etc/sudoers file.

<user> ALL=(minecraft) NOPASSWD: ALL

You should understand the potential security issues here. This will allow <user> to run any command on your system as the minecraft user. If the user only has permission on the file system for files related to the minecraft server this is probably fine.