Possible bug - Dedicated server does not exit on "stop" / Server hang on "stop"
DLCIncluded opened this issue · 5 comments
Modpack
Direwolf20 1.18
Modpack version
1.3.1
Mod versions tested with:
1.0.5, 1.0.7, 1.0.9
Log Files
https://pastebin.com/m2tXqASG
Describe the bug
Linux dedicated server doesn't end the java process when stopped. It sits at the ">" minecraft console after saving, and leaves java running.
Using a server manager, IE AMP by CubeCoders, scheduled reboots cause the same behavior, sending a stop command, and it hangs and is never able to start the server as it gets stuck waiting for the server to properly exit.
Steps to reproduce
Launch dedicated server.
Wait for it to load up fully.
Issue a stop command in the minecraft console.
OR
run server with AMP, schedule a reboot or /stop command every 4 hours, on that time the server appears to save, backup, and then hang after doing so getting stuck on the line "Finished unloading ender chest data"
Removing the mod ftbbackups2 all together, the server restarts / stops as expected.
Expected behaviour
Console should close and java should exit upon stop, after save.
Additional information
Using ctrl+c or ending the process manually after all the save messages seems to have no ill effect. I left the server at the saved and stopped, but not exited state for a few hours and it never exited.
This is the thread on the FTB team's github issue tracker for the same issue: FTBTeam/FTB-Modpack-Issues#847 where they suggested the issue being with an older version of ftbbackups2
I am not sure if this is a direct issue or a conflict, any assistance would be appreciated, thank you for the work you guys do!
Can confirm I have the same issue with FTBbackups 2 v1.0.9 on both Windows 10 servers, and a rented server on Linux. Only my log's final line before the server idles instead of shutting down is: the backups scheduler shutdown log.
Having this same challenge running a dedicated server on a custom modpack using AMP Server Manager on Linux. Every time I shut down the server the lines show the below output. Then the server hangs and I have to kill it to actually have it shutdown.
