-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Crash]: Frequent server crashes due to "Ticking entity" issue #1551
Comments
Were you or any players on your server fighting a Wither Skeleton when the server crashed? |
Oh actually about an hour after sending out this ISSUE I found the cause and banned the generation of the Wither Skeleton and have never crashed due to this issue again. |
Same issue here on 0.2.56 Keeps crashing on logging in, had to move my character with NBT editor to 0,128,0 in order to fix it. As far as I remember they all where normal skeletons.
|
Another Server crash, Now in the Other Ancient Pyramid. Exact same entity.
|
In the Crash logs it indeed shows the Wither Skeleton as being ticking
|
Also normal Skeleton is impacted. Maybe it has something to do with my damage reflects?
|
The following assumes you were fighting a Skeleton or Wither Skeleton when the server crashed. |
Hey @James103 I have found the issue for me was the Thorn Pendant Necklace from Artifacts that cause the issue. ID: artifacts:thorn_pendant |
Do you get a similar crash if you enchant your armor with Thorns then let (Wither) Skeletons attack you and die from that Thorns effect? |
Caused by thorns killing skeleton-based mobs, see #1153 |
Possible Fixes
Yes
Modpack Version
0.2.54
What happened?
Advance note: I installed other mods, two about adding more planes and a drop cleanup mod, which I don't think will have an impact on the AI convenience.
My server has been up for four days now, and since yesterday, the server has started crashing frequently because of this error, and looking at the logs I think it's a problem with the monster AI, but I can't pinpoint the exact reason why.
It even crashed four times in a row in the early hours of this morning
This is the log error:
net.minecraft.ReportedException: Ticking entity
at net.minecraft.server.MinecraftServer.m_5703_(MinecraftServer.java:897) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.dedicated.DedicatedServer.m_5703_(DedicatedServer.java:283) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.MinecraftServer.m_5705_(MinecraftServer.java:814) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.MinecraftServer.m_130011_(MinecraftServer.java:661) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.MinecraftServer.m_206580_(MinecraftServer.java:251) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at java.lang.Thread.run(Thread.java:840) ~[?:?]
Caused by: java.util.ConcurrentModificationException
at java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:756) ~[?:?]
at java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:778) ~[?:?]
at net.minecraft.world.entity.ai.goal.GoalSelector.m_186081_(GoalSelector.java:118) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.world.entity.Mob.m_6140_(Mob.java:753) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.world.entity.LivingEntity.m_8107_(LivingEntity.java:2548) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.world.entity.Mob.m_8107_(Mob.java:536) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.world.entity.monster.Monster.m_8107_(Monster.java:42) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.world.entity.monster.AbstractSkeleton.m_8107_(AbstractSkeleton.java:116) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.world.entity.LivingEntity.m_8119_(LivingEntity.java:2298) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.world.entity.Mob.m_8119_(Mob.java:337) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.level.ServerLevel.observable$track(ServerLevel.java:7169) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.level.ServerLevel.redirect$bib000$observable$onTickNonPassenger(ServerLevel.java:7185) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.level.ServerLevel.m_8647_(ServerLevel.java:693) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.world.level.Level.m_46653_(Level.java:479) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.level.ServerLevel.m_184063_(ServerLevel.java:343) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.world.level.entity.EntityTickList.m_156910_(EntityTickList.java:54) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.level.ServerLevel.m_8793_(ServerLevel.java:323) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
at net.minecraft.server.MinecraftServer.m_5703_(MinecraftServer.java:893) ~[server-1.20.1-20230612.114412-srg.jar%23911!/:?]
... 5 more
The following four error reports are basically very similar, all because of a single error and then the server immediately crashed:
crash-2024-03-29_01.19.07-server.txt
crash-2024-03-29_01.26.25-server.txt
crash-2024-03-29_07.19.29-server.txt
crash-2024-03-29_07.44.13-server.txt
log--2024-03-29_01.19.07.log
log-2024-03-29_01.26.25-server.log
log-2024-03-29_07.19.29-server.log
log-2024-03-29_07.44.13-server.log
Crash Log
https://gist.github.com/KNaiFen/72e6252a897e48c04e7c11cf6516711a
Latest.Log
https://gist.github.com/KNaiFen/d3e244072590addf3c6730660034ab0a
The text was updated successfully, but these errors were encountered: