Minecraft Server keeps closing on its own

I have a 8GB Ram 4 Cores plan and i am hosting a minecraft server, but after a few minutes into starting the server the stop command automatically gets put into the console on its own and the server stops, The system is enough to run the server though, any ideas?

13 Replies

Are you starting the Minecraft process with Tmux or Screen?

This keeps the Minecraft console open even when you logout of the terminal.

Even when the terminal's open, the stop command goes through on its own and closes the server, then it reopens and then closes and loops like that even without my own intervention

If the the Minecraft console is stopping and starting automatically that’s strange…

How do you have things configured?

I moved my already pre-configured and made server to linode machines, i never had any problems like these before, it only started right after i launched the server in linode

We still need more details in order to help.

Tell me what files you need to check ill send its details gladly

You have to provide details on what you’re running: OS version, Minecraft version, configuration file, etc.

We don’t know how you setup your previous server, so we can’t answer/troubleshoot based on “It doesn’t work” responses.

OS : Ubuntu 20.04.03 LTS

Minecraft Version : 1.16.5 Tuinity (Paper-Fork)

by configuration file i dont know what you meant by it because theres hundreds of them in a server so i'll give the OS Configuration

VM: Paravirtualization

Boot settings : GRUB 2 Default Kernel no memory limit

512 MB Swap Image

All boot helpers enabled

There's only one config file that actually matters in this context, and that's the server.properties file.

Minecraft server properties

Wed Sep 22 17:56:37 UTC 2021

enable-jmx-monitoring=false
rcon.port=25575
level-seed=
enable-command-block=true
gamemode=survival
enable-query=false
generator-settings=
level-name=world
motd=A Minecraft Server
query.port=25565
pvp=true
generate-structures=true
difficulty=hard
network-compression-threshold=256
max-tick-time=60000
max-players=75
use-native-transport=true
enable-status=true
online-mode=false
allow-flight=false
broadcast-rcon-to-ops=true
view-distance=8
max-build-height=256
server-ip=
allow-nether=true
server-port=25565
sync-chunk-writes=true
enable-rcon=false
op-permission-level=4
prevent-proxy-connections=false
resource-pack=
entity-broadcast-range-percentage=100
player-idle-timeout=0
rcon.password=
force-gamemode=false
debug=false
rate-limit=0
hardcore=false
white-list=false
broadcast-console-to-ops=true
spawn-npcs=true
spawn-animals=true
snooper-enabled=true
function-permission-level=2
level-type=default
text-filtering-config=
spawn-monsters=true
enforce-whitelist=false
spawn-protection=16
resource-pack-sha1=
max-world-size=29999984

Unfortunately I'm not familiar with 1.16.5 Tuinity (Paper-Fork) since I run Minecraft from Mojang.

Tuinity just optimizes the vanilla game and adds support for plugins and whatnot, server.properties file is still the game as if you get it from mojang, though im thinking ubuntu is somehow causing this, i just moved the serverfiles to linode and thats when the problem has started initially, there is no crashes just the "stop" command itself is being run automatically after some time the server has started which if it was caused by corrupt files or normal errors or crashes etc. it wouldn't run the stop command it would just simply crash…

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct