Closed candidgamera closed 8 months ago
candidgamera
commented
11 months ago Update : I manually edited the refined storage network dat file to put both RS networks in redstone-control mode. This allowed the server to load with both networks turned off and I was able to log in.
codegavran
commented
11 months ago Getting the same error on a standard ATM9 server running RS 1.12.4
Once you were able to get in, what did you do to prevent the crash from reoccurring @candidgamera ?
candidgamera
commented
11 months ago Getting the same error on a standard ATM9 server running RS 1.12.4
Once you were able to get in, what did you do to prevent the crash from reoccurring @candidgamera ?
@codegavran - Having had inspected the various RS dat files, I knew that it was unlikely to be my own network causing the crash - I just didn't have anything heinous in storage. I took the precaution of removing any creative exporters I had on my network, to guarantee I didn't have any creative exporter/importer race conditions going on, and re-enabled mine. Once that happened safely, I turned my attention to the other RS network on the server - my friend had been storing a ton of equipment drops from his mob farm onto an infinite drive in his RS system. I had him remove the drive and make sure nothing else was being imported before we re-enabled his.
I still don't have a concrete sense of what /exactly/ the issue was, but removing the thousands of equipment objects with NBT data from his system seems to have kept the issue from recurring for us.
Darkere
commented
11 months ago increasing max-tick-time in server.properties should be the first step. 1 minute seems long but on startup that easily happens. Add a 0 at the end.
Describe the bug
Yesterday around 1PM, my hosted ATM8 server began a crash loop. One player was logged in and used a teleport commend from FTB Essentials - this spiked the tick time about sixty seconds, according the first crash log - and then when the server came back up, it crashed again. The tick time was still above sixty seconds, but for the second and all subsequent crashes, the crash report points to Refined Storage.
I shut down the server, downloaded a copy of the world, inspected the refined storage dat files with NBT Explorer - one player besides myself has an RS system, and had half a billion redstone stored - I edited the dat file to reduce the stored redstone quantities in the hopes that it was just some mass-production feedback going on, but no luck.
I can get the server not to crash if I edit the server properties file to remove the max tick time limit, but cannot get logged in - connection timeout - even if I do so.
We're running 1.0.23, and I had intended to update us to 1.0.28 today, in fact, but this has obviously ground that effort to a halt.
We're running on Shockbyte, and one confounding factor is that I had the server configured to be a Forge 1.19.2 server with auto-updates, and at some point in the last few weeks, Shockbyte's processes did upgrade the Forge version to 43.3.5, instead of 43.2.14. I don't think that's relevant to the crash, but mention it for completeness.
Crash log visible here : https://mclo.gs/fB3K8i6
Please help me get this back online for myself and my friends. Thank you in advance!
How can we reproduce this bug or crash?
Since it is a crash on boot, I do not have concrete steps to reproduce the issue. I'm unclear as to what is causing the tick lag specifically beyond what the crash report gives me.
What Minecraft version is this happening on?
Minecraft 1.18.2
What Forge version is this happening on?
43.3.5
What Refined Storage version is this happening on?
1.11.6
Relevant log output