Posted December 14, 20222 yr Hello if someone have a hint to find where the problem come from. thanks The crash report file : https://mclo.gs/r4kIkrd
December 14, 20222 yr You have something taking too long on the server thread. When the 60 second timeout happened it was doing something with applied energistics. Quote ava.lang.Error: ServerHangWatchdog detected that a single server tick took 60.00 seconds (should be max 0.05) 8at java.util.IdentityHashMap.get(IdentityHashMap.java:341) ~[?:?] {re:mixin} 9at appeng.me.storage.CompositeStorage.isPreferredStorageFor(CompositeStorage.java:38) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 10at appeng.me.storage.DelegatingMEInventory.isPreferredStorageFor(DelegatingMEInventory.java:36) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 11at appeng.me.storage.MEInventoryHandler.isPreferredStorageFor(MEInventoryHandler.java:136) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 12at appeng.me.storage.NetworkStorage.insert(NetworkStorage.java:128) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 13at appeng.helpers.iface.PatternProviderReturnInventory.injectIntoNetwork(PatternProviderReturnInventory.java:75) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 14at appeng.helpers.iface.PatternProviderLogic.doWork(PatternProviderLogic.java:373) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 15at appeng.helpers.iface.PatternProviderLogic$Ticker.tickingRequest(PatternProviderLogic.java:502) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 16at appeng.me.service.TickManagerService.unsafeTickingRequest(TickManagerService.java:358) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 17at appeng.me.service.TickManagerService.tickQueue(TickManagerService.java:121) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 18at appeng.me.service.TickManagerService.tickLevelQueue(TickManagerService.java:93) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 19at appeng.me.service.TickManagerService.onLevelEndTick(TickManagerService.java:78) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 20at appeng.me.Grid.onLevelEndTick(Grid.java:262) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 21at appeng.hooks.ticking.TickHandler.onServerLevelTickEnd(TickHandler.java:282) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 22at appeng.hooks.ticking.TickHandler.onLevelTick(TickHandler.java:248) ~[appliedenergistics2-forge-12.8.6.jar%23125!/:12.8.6] {re:classloading} 23at appeng.hooks.ticking.TickHandler$$Lambda$24988/0x00000008038dac50.accept(Unknown Source) ~[?:?] {} Boilerplate: If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one. If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install Large files should be posted to a file sharing site like https://gist.github.com You should also read the support forum sticky post.
December 14, 20222 yr Since it looks like you have the spark mod installed did you try looking at its analysis of what is using time on the server thread? Boilerplate: If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one. If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install Large files should be posted to a file sharing site like https://gist.github.com You should also read the support forum sticky post.
December 14, 20222 yr Author 9 minutes ago, warjort said: Since it looks like you have the spark mod installed did you try looking at its analysis of what is using time on the server thread? To be honest, I don't know how to use spark, the server doesn't have to be up in order to analyse with spark ? Because the server keep crashing just after loading : https://mclo.gs/Lvsil8G
December 14, 20222 yr Author 7 hours ago, warjort said: Since it looks like you have the spark mod installed did you try looking at its analysis of what is using time on the server thread? Did you have a solution because I tried to launch the spark profiler when the server is up but it crash 3 seconds after so the report is never upload
December 14, 20222 yr You originally reported the 60 second timeout on the server thread crash. If it crashes after 3 seconds you have some other error. But you don't post a link to the logs/debug.log to show what that is. Boilerplate: If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one. If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install Large files should be posted to a file sharing site like https://gist.github.com You should also read the support forum sticky post.
December 14, 20222 yr Author 10 minutes ago, warjort said: You originally reported the 60 second timeout on the server thread crash. If it crashes after 3 seconds you have some other error. But you don't post a link to the logs/debug.log to show what that is. This is my debug.log : https://mclo.gs/Lvsil8G
December 14, 20222 yr Quote [14Dec2022 01:32:20.559] [Server thread/INFO] [net.minecraftforge.common.AdvancementLoadFix/]: Using new advancement loading for net.minecraft.server.PlayerAdvancements@231f873 -- 55 second gap -- [14Dec2022 01:33:15.839] [Server Watchdog/ERROR] [net.minecraft.server.dedicated.ServerWatchdog/FATAL]: A single server tick took 60.00 seconds (should be max 0.05) That is the server tick timeout error. It can't be a crash after 3 seconds. Boilerplate: If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one. If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install Large files should be posted to a file sharing site like https://gist.github.com You should also read the support forum sticky post.
December 14, 20222 yr Author 2 minutes ago, warjort said: That is the server tick timeout error. It can't be a crash after 3 seconds. Yes but what I want to said is that I can't run the command spark profiler -stop after the line you mentioned because the server is not crashed but is totally bugged due to that
December 14, 20222 yr I don't know then. All the information we have is that you have something taking too long on the server thread. And the one crash report you posted showed it was doing something in applied energistics. Without new information, I suggest you contact the authors of that mod. Boilerplate: If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one. If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install Large files should be posted to a file sharing site like https://gist.github.com You should also read the support forum sticky post.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.