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

It looks like the 1.14.2-1 PKGBUILD update did not change the JAR url or SHAsum. Based on the 1.14.2 blogpost it seems like the URL should have changed (808be....) https://www.minecraft.net/en-us/article/minecraft-java-edition-1-14-2

@abrenner Thanks a bunch! That should not have happened! Fixed.

Bug Report:

In commit fc300f4fd62a a switch was made from using "which" to "command" to determine if binaries exists on a system (tar, netcat, etc.).

The issue is that a space needs to be between the -v and name of the binary:

command -vtar is not correct

command -v tar is correct

Please add a space.

thanks, /adam

@fryfrog Fair point given that Java is in the process of changing their versions more frequently.

I'm running this w/ java-11-openjdk (jre-openjdk and jre-openjdk-headless packages), could the java-runtime-headless dep be set to >= instead of =?

@buzo Technically the resulting package has changed and bumping the pkgrel would have been justified. However, as the change in the script addressed an issue which will affect probably no one who uses the package, I refrained from doing so.

edh: It would have been a good idea to increase pkgrel with your change yesterday.

@Grelek Minecraft server logs are important though! Previously a similar error which has since been fixed was due to the server already running and the screen session therefore failing to start properly. Those kind of anomalies can be investigated if the server logs are present. Furthermore my very first request was not about the server logs at all and you disregarded that completely.

Pinning down the problem with merely the information which you provided until now is simply impossible as I can not reproduce your error! The systemd service should simply execute the script using the minecraft user as seen here and until now has not caused any problems itself AFAIK. Regarding the script, I can merely tell you that the error originated from somewhere around here.

If you do not want to investigate the problem in a reproducible way yourself (e.g. using a clean chroot), then I am afraid you have to provide more details.

@edh Minecraft logs aren't relevant here, the server isn't even getting started. And the only info I have is the I posted here before. For some reason the systemd unit file does not work, although I can start the server just fine manually with the commands, even when I log in as the minecraft user.

@Grelek I can not reproduce your described effect in a clean chroot. Please explain your problem in more detail: E.g. are there any other screen sessions running (pgrep -af SCREEN), what does the minecraft log tell you, ...