Server not shutting down issue returning.
In testing the latest nightly build, I've encountered the same server refusing to shut down issue that was fixed with commit 82e0cfe0. Aside from quickly starting up and shutting down the server, I've always been testing pre-generation every time I've launched the server, and even when it only ran for 30 minutes and didn't come near maximum usage for any component I still encountered the issue. Not saying it is the cause but that is at least a constant in my testing.
This issue wasn't present using commit bc475373, and I do not recall if it was an issue using commit 8f7823a4, but it is definitely an issue using commit 521bcdcc as I am currently.
Here is the spark profile that was running on the server for server specs and a modlist: https://spark.lucko.me/wpFw28ipz4
spark
spark is a performance profiler for Minecraft clients, servers, and proxies.
41 Replies
I too have this issue.
Unable to reproduce with the latest nightly build.
I'm not able to reproduce in the development environment, but I have been having the issue on a live server I have - I might try investigate when I get home.
There's a 30 minute expiry for spark profiles IIRC
Was unable to reproduce, at least with the same frequency, after updating to the newest build
Will be running longer testing
Can you send a log from when you were able to reproduce the issue - the spark link expired? I think it's not Distant Horizons, or perhaps it's some kind of interaction between mods.
I believe this should be the log from the one I posted to start the thread
Actually that isn't the one I posted, but it should be the same issue
And I can still access the spark profile from the link so I've attached more info from that as well as a simple modlist from my mods folder
I haven't got around to debugging it, but removing c2me (neoforge version) seems to have resolved it for me.
I am having same problem [14:00:22] [Server thread/INFO]: Closed DhWorld of type [SERVER_ONLY].
[14:00:22] [Server thread/INFO]: Closing all [0] database connections...
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
@shaurya @KaiSiege @Jaxpo are any of you able to test with less mods until you know which combination of mods is causing the issue?
I’ve fully reset everything, moved to the latest build and have not encountered the issue since
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
How many mods did you have?
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
Oh, that's probably the smallest modlist I've seen reproducing the issue so far. Can you send the log?
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
Hmm, but you say it's fixed itself.
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
Yea
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
I am feeling a bit more confident that this is caused by DH, as it seems to be happening in quite a few different environments and it seems like DH is the only thing in common.
I will try to find some time to debug as I'm reproducing the issue locally again.
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
To be clear I'm not a DH dev, and any fix I make for this bug will probably have to wait until after the next release until it's merged into DH.
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
I think it's fairly safe to close it - however I would err on the side of still giving it a minute before doing so.
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
I know alredy what causes it
Its either only DH
or C2me with DH
cause, this only happens after we do /dh pregen
It happens without c2me for me. It also happens without using pregen.
Sometimes
It never happend after i generated a very large radius
So i guess, it happens only when the world generator at least generate a single lod
And since i alredy generated a very large radius
it don't happen anymore
until anyone goes tooo far
Yes I think that's probably the important thing to look into.
Confirm that it only happens after significant writing has been made to the DB.
What would be interesting to see, is if I remove FullDataV1 and SQLite entirely from my datastore branch, if the problem persists or not.
Unknown User•4d ago
Message Not Public
Sign In & Join Server To View
yup
i said that alredy here
Unknown User•3d ago
Message Not Public
Sign In & Join Server To View
I have been unable to reproduce DH preventing the server from shutting down.
If anyone can find a consistent way of reproducing the problem with just DH, let me know.
are you running reterraforged by chance?
Will see, For me it was when i sued DH with c2me and did dh pregen 128 after that triend to close
Unknown User•2d ago
Message Not Public
Sign In & Join Server To View