After testing it 10 times, it seems like the world isn't saved. Only once did it save players, but other than that, it doesn't have the same output as the stop command, so i'm led to assume it doesn't save.
This means that running a minecraft server as a daemon is harder without some workarounds such as using GNU screen or tmux.
Environment
Linux
openjdk version "11.0.8" 2020-07-14
Linked issues
relates to 2
Attachments
Comments 4
Here you go, as you can see, when SIGTERM is received, the log ends, but it doesn't say anything about saving chunks, saving player data, or anything like that.
Can confirm.
Affects 21w05b.
Only performed a quick test. Placed a few blocks then sent sigterm with:
kill -15 <pid>Log makes no mention of saving world, players, etc. However when I restarted the server, I was in the correct location and the blocks I had placed where there. Running /stop then closed the server with mention of saving.
It would be great to have this fixed. My kids get a time limit to play minecraft each day and it would be nice if the tool I wrote that monitors and enforces the limits would have the ability to ask it to shutdown cleanly. SIGTERM is the designated proper Linux way of saying “Please clean your room and shutdown gracefully”
Please provide the full server log.