Arch Linux User Repository

Unfortunately, upstream does not really have proper releases but instead points to build-versions of the software. Note, I will not push every new build of the package to the AUR but I will update the package upon new minecraft releases, e.g. for 1.14.4 to 1.14.5.

Hi ! Sorry to bother ;

When trying to start a server (papermc start), the following message appears.

Starting server... done

(and nothing else)

However, when trying to papermc status or papermc console, they both indicate that no server is actually running.

I can manually run the jar in /srv/papermc so it's not a problem there.

Thank you in advance for your time.

Wow! Thank you for the quick response haha. Yep, that's exactly the issue. Thank you so much, I've opened the issue here.

@x00010 Do you use the idle-server daemon to suspend the server if no user is active?

If so then this is most probably a bug in the management server. In this case I would ask you to file an issue at github to more easily track the issue.

I've noticed a strange behavior with this package, sometimes when the server is starting up it seems to attempt to run a command, particularly list, which causes the following error:

[21:28:08 INFO]: Reloading ResourceManager: Default, bukkit, afk display v1.1.0.zip, armor statues v2.8.1.zip, chunk loaders v1.0.1.zip, custom nether portals v2.3.2.zip, fast leaf decay v2.0.3.zip, multiplayer sleep v2.4.3.zip, player head drops v1.1.0.zip, unlock all recipes v2.0.0.zip                                                                                                                                        

    list                                                                                                                                                                                                               

    [21:28:16 INFO]: Loaded 7 recipes                                                                                                                                                                                  

    [21:28:23 INFO]: Starting minecraft server version 1.17.1                                                                                                                                                          

    [21:28:23 INFO]: Loading properties                                                                                                                                                                                

    [21:28:23 INFO]: This server is running Paper version git-Paper-243 (MC: 1.17.1) (Implementing API version 1.17.1-R0.1-SNAPSHOT) (Git: 20903fc)                                                                    

    > lis[21:28:24 ERROR]: Caught previously unhandled exception :                                                                                                                                                     

    java.lang.NullPointerException: Cannot invoke "org.bukkit.command.CommandSender.hasPermission(String)" because the return value of "net.minecraft.commands.CommandListenerWrapper.getBukkitSender()" is null       

        at net.minecraft.commands.CommandDispatcher.lambda$new$0(CommandDispatcher.java:210) ~[patched_1.17.1.jar:git-Paper-243]
        at com.mojang.brigadier.tree.CommandNode.canUse(CommandNode.java:78) ~[patched_1.17.1.jar:git-Paper-243]
        at com.mojang.brigadier.CommandDispatcher.parseNodes(CommandDispatcher.java:358) ~[patched_1.17.1.jar:git-Paper-243]
        at com.mojang.brigadier.CommandDispatcher.parse(CommandDispatcher.java:348) ~[patched_1.17.1.jar:git-Paper-243]
        at io.papermc.paper.console.BrigadierCommandHighlighter.highlight(BrigadierCommandHighlighter.java:28) ~[patched_1.17.1.jar:git-Paper-243]
        at org.jline.reader.impl.LineReaderImpl.getHighlightedBuffer(LineReaderImpl.java:3818) ~[patched_1.17.1.jar:git-Paper-243]
        at org.jline.reader.impl.LineReaderImpl.getDisplayedBufferWithPrompts(LineReaderImpl.java:3800) ~[patched_1.17.1.jar:git-Paper-243]
        at org.jline.reader.impl.LineReaderImpl.redisplay(LineReaderImpl.java:3700) ~[patched_1.17.1.jar:git-Paper-243]
        at org.jline.reader.impl.LineReaderImpl.doCleanup(LineReaderImpl.java:2427) ~[patched_1.17.1.jar:git-Paper-243]
        at org.jline.reader.impl.LineReaderImpl.cleanup(LineReaderImpl.java:2419) ~[patched_1.17.1.jar:git-Paper-243]
        at org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:648) ~[patched_1.17.1.jar:git-Paper-243]
        at org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:418) ~[patched_1.17.1.jar:git-Paper-243]
        at net.minecrell.terminalconsole.SimpleTerminalConsole.readCommands(SimpleTerminalConsole.java:158) ~[patched_1.17.1.jar:git-Paper-243]
        at net.minecrell.terminalconsole.SimpleTerminalConsole.start(SimpleTerminalConsole.java:141) ~[patched_1.17.1.jar:git-Paper-243]
        at net.minecraft.server.dedicated.DedicatedServer$1.run(DedicatedServer.java:113) ~[patched_1.17.1.jar:git-Paper-243]

I am then only able to shutdown the server by pressing ctrl+a and typing :kill-session. This behavior is extremely strange and I'm not too sure what's causing it, maybe the papermc script? Server was started via

papermc start

papermc console

Thanks for the comments @electronicboy and @Zalgo . I updated to v2 of the API.

Hey,

Sorry, you emailed me a while ago and basically, I ended up losing it and got distracted;

https://papermc.io/api/docs/ - The documentation for the API exists here, it makes it easy to pull jars off our services and is easily queriable, commonly people just use jq in order to parse the API given that it's just a json endpoint, makes it easy to work out latest version, latest build, within a script; Would mean that scripts can easily be created which don't tie to the MC version, and can permit people to update builds

The v1 API has been deprecated for coming up to a year and is scheduled to be sunset near the end of November, marking a year of it's deprecation

The version of the API this PKGBUILD uses to download builds will stop working on Sept 25 of this year due to it being deprecated, just a heads up

@sflor hmm, tmux exiting immediately does not necessarily mean the server can not. Starting tmux plainly is different to starting tmux with a command. In my understanding of the issue, there should be no need for a default-command. Having said that, tmux should of course work normally, i.e. start without exiting.

I am a little confused what you mean by having configured zsh as default shell. Surely you didn't set the zsh as shell for papermc, right?

Finally, to reiterate once again: Please try to reproduce the error in a clean chroot!

Sorry if my comment came off as rude, I just didn't have much time to do more testing yesterday.

The issue is that tmux run as papermc user exits immediately. It doesn't matter what arguments I provide or don't.

[papermc@midori sf]$ tmux
[exited]

I fixed this by creating /etc/tmux.conf with the following content:

set-option -g default-shell "/bin/bash"
set-option -g default-command "bash -l"

Maybe it's related to me having zsh as default?

@sflor The line is supposed to start the server in the background, i.e. it is not supposed to return anything. If you strip the -d from the argument it will run in the foreground (see man tmux).

Please be more verbose in your description of the error. A 1-bit binary statement (failing/not failing) contains very little information:

• How exactly is it failing?
  • Do you mean that the return value is non-zero?
  • What happens if you modify the command as outlined in my previous comment?
  • Did you attempt to perform the steps from the command individually, i.e. switch user -> spawn tmux -> run papermc?
• Did you check for the EULA/papermc logs (if any)?
• Did you check again in a clean chroot?