mojira.dev
MC-139758

Stopping the server doesn't work

Hi. I have a VPS where i play all the minecraft versions and this is the first snapshot dont wont to stop, when i type stop in the console. Thank you.


From MC-142040:

The bug

Server won't close with enabled GS4 listener on stop command.
What I expected to happen was...:
Server stops and exit after "stop" command on console
What actually happened was...:
Server hangs and won't exit after:

[19:41:33] [Server thread/INFO]: Saving chunks for level 'world'/minecraft:overworld
[19:41:33] [Server thread/INFO]: ThreadedAnvilChunkStorage (world): All chunks are saved
[19:41:33] [Server thread/INFO]: Saving chunks for level 'world'/minecraft:the_end
[19:41:33] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM1): All chunks are saved
[19:41:33] [Server thread/INFO]: Saving chunks for level 'world'/minecraft:the_nether
[19:41:33] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM-1): All chunks are saved

How to reproduce

  1. Enable query port in server.properties.

    enable-query=true
  2. Start server

    [19:46:58] [Server thread/INFO]: Done (8.822s)! For help, type "help"
    [19:46:58] [Server thread/INFO]: Starting GS4 status listener
    [19:46:59] [Query Listener #1/INFO]: Query running on 0.0.0.0:25565
  3. Enter stop command

    [19:47:06] [Server thread/INFO]: Stopping the server
    [19:47:06] [Server thread/INFO]: Stopping server
    [19:47:06] [Server thread/INFO]: Saving players
    [19:47:06] [Server thread/INFO]: Saving worlds
    [19:47:06] [Server thread/INFO]: Saving chunks for level 'world'/minecraft:overworld
    [19:47:07] [Server thread/INFO]: ThreadedAnvilChunkStorage (world): All chunks are saved
    [19:47:07] [Server thread/INFO]: Saving chunks for level 'world'/minecraft:the_nether
    [19:47:07] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM-1): All chunks are saved
    [19:47:07] [Server thread/INFO]: Saving chunks for level 'world'/minecraft:the_end
    [19:47:07] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM1): All chunks are saved

    → Server hangs and won't exit (java proccess is still alive).

Linked issues

Attachments

Comments

migrated

Please attach the crash report ([minecraft|http://hopper.minecraft.net/help/finding-minecraft-data-folder]/crash-reports/crash-<DATE>-client.txt), otherwise we can not diagnose this issue.
For technical support please use the Mojang Support Center.

-- I am a bot. This action was performed automagically!

migrated

I cant do that cose is a VPS not single player and get stack and i need to reboot. I add a photo. Thankyou.

 

migrated

Running 18w47a on my dedicated server box i encounter the exact same issue on a brand new generated world using this snapshot, when i try and restart the server the log shows nothing unusual but it refuses to restart and then i need to manually kill the PID of the process in order for the server to restart.

Attached is a screenshot of the entire log

Johnibur

Same issue: when typing stop, the console was stuck on "all chunks are saved" and I had to manually kill it.

migrated

The same problem with 18w47b.

Johnibur

Also happening with the gui.

Johnibur

Also to mention: the server stops, but the (g)ui continues to display and freeze untill you kill it.

migrated

Can verify. It does this with 18w47b, but not the most recent release. Kill doesn't work, have to do kill -9 to fully kill.

Debian Version:

4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64

 

Java Version:

 

openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-2~deb9u1-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)

 

migrated

Confirming kill -9 is required on CentOS. 18w47b java server.

migrated

Still exists in 18w48a

migrated

For some reason, I didn't face this issue on 18w48a

tested on upgraded/new worlds.

after fallback to w18w47a/b - still can't stop the server.

OS: win7

Java:
java version "1.8.0_191"
Java(TM) SE Runtime Environment (build 1.8.0_191-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)

 

migrated

Yes this issue is no longer present on a Windows system, its still very much present on a *nix system

migrated

Seems to exit fine for me on 18w48a

Johnibur

This is not an issue anymore with 18w48b. Exists fine on a Linux system.

migrated

Dosent exit fine for me.

Server uses MineOS for Console Management

Server Specs:

Ubuntu 18.04.1 LTS
Intel® Core i7-6700
64 GB RAM
2 x 500 GB 6Gb/s SSDs

migrated

Latest exits fine for me. Just takes around 5-10s (presumably due to it needing to save the world?).

migrated

Still broken for me on 18w49a

migrated

Still broken for me in 18w50a

migrated

Minecraft is not tracking the extra java processes it spawns under Linux. The stop command only seems to stop the primary game thread, the rest keep running.

migrated

Still not working in 19w02

migrated

19w03 is also affected

migrated

Still in 19w03b

migrated

also in 19w03c

 

migrated

This error also occurs when rcon is enabled.

enable-rcon=true

 

migrated

19w04a affected

 

migrated

19w04b affected

migrated

boq

Confirmed

Minecraft 18w47a, Minecraft 18w47b, Minecraft 18w48a, Minecraft 18w49a, Minecraft 18w50a, Minecraft 19w02a, Minecraft 19w03a, Minecraft 19w03b, Minecraft 19w03c, Minecraft 19w04b

Minecraft 19w05a

Retrieved