Debugging a hanging shutdown on a modded server
I'm running a modded server with 200-ish mods and one of them is causing /stop to fail to exit to terminal as I presume some random mod's thread is hanging, using ctrl+c to exit doesn't cause any issues after the shutdown process is complete so it's not a corruption concern, but it does break any shell script logic for auto-restarting the server since the process is still active after running /stop. I was wondering if there's any way to determine what components of the server are still running to cause this, or maybe a kubejs event that can force quit the server ~2 minutes after running /stop?
11 Replies
Thanks for asking your question!
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
Make sure to mark solved when issue is solved!!!
/close
!close
!solved
!answered
Requested by cncz#0
Can you send logs please?
shutdown starts at line 7508
We have uploaded your file to a paste service for better readability
Paste services are more mobile friendly and easier to read than just posting a file
MPU566C.log
Requested by cncz#0
Issue with the Framework mod.
I’ve looked into their GitHub issues and another person is having the same issue. No response from the dev
only way to fix would be remove the mod / its dependents
makes sense
didn't work😢
also removed another mod called MIMI which had a github issue pending for the problem
logs after removing?
same log
*except framework
wonder if a shell script can read stdout for "All dimensions are saved" and force close it
boom
We have uploaded your file to a paste service for better readability
Paste services are more mobile friendly and easier to read than just posting a file
rtpEYp4.sh
Requested by cncz#0
chatgpt sucks at scripting so I had to edit the heck out of it but I got it