[SPIGOT-5872] Server stoped responding and errored. Unkown cause Created: 28/Jun/20  Updated: 28/Jun/20  Resolved: 28/Jun/20

Status: Resolved
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Tamani Wolf Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: 1.16.1, Spigot, Unknown, crash, error, responding, stopped
Environment:
  • Updated from 1.15.2 to \/
  • Spigot 1.16.1 (git-Spigot-758abbe-2b00831 (MC: 1.16.1))
  • OpenJDK 11.0.7 2020-04-14

Attachments: Text File latest.log    
Version: 1.16.1
Guidelines Read: Yes

 Description   

The Server stopped responding ~30 Min after the last log writing.

I don't know what error it is, but don't look like a plugin has caused it.

Start of the log:

[06:59:33] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 513467ms or 10269 ticks behind
[06:59:33] [Spigot Watchdog Thread/ERROR]: ------------------------------
[06:59:33] [Spigot Watchdog Thread/ERROR]: The server has stopped responding! This is (probably) not a Spigot bug.
[06:59:33] [Spigot Watchdog Thread/ERROR]: If you see a plugin in the Server thread dump below, then please report it to that author
[06:59:33] [Spigot Watchdog Thread/ERROR]: 	 *Especially* if it looks like HTTP or MySQL operations are occurring
[06:59:33] [Spigot Watchdog Thread/ERROR]: If you see a world save or edit, then it means you did far more than your server can handle at once
[06:59:33] [Spigot Watchdog Thread/ERROR]: 	 If this is the case, consider increasing timeout-time in spigot.yml but note that this will replace the crash with LARGE lag spikes
[06:59:33] [Spigot Watchdog Thread/ERROR]: If you are unsure or still think this is a Spigot bug, please report to https://www.spigotmc.org/
[06:59:33] [Spigot Watchdog Thread/ERROR]: Be sure to include ALL relevant console errors and Minecraft crash reports
[06:59:33] [Spigot Watchdog Thread/ERROR]: Spigot version: git-Spigot-758abbe-2b00831 (MC: 1.16.1)
[06:59:33] [Spigot Watchdog Thread/ERROR]: ------------------------------
[06:59:33] [Spigot Watchdog Thread/ERROR]: Server thread dump (Look for plugins here before reporting to Spigot!):
[06:59:34] [Spigot Watchdog Thread/ERROR]: ------------------------------
[06:59:34] [Spigot Watchdog Thread/ERROR]: Current Thread: Server thread
[06:59:34] [Spigot Watchdog Thread/ERROR]: 	PID: 22 | Suspended: false | Native: false | State: RUNNABLE
[06:59:34] [Spigot Watchdog Thread/ERROR]: 	Stack:
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//com.google.common.collect.Iterators$3.hasNext(Iterators.java:169)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//com.google.common.collect.Iterators.addAll(Iterators.java:366)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//com.google.common.collect.Lists.newArrayList(Lists.java:165)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//com.google.common.collect.Lists.newArrayList(Lists.java:150)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//net.minecraft.server.v1_16_R1.ChunkProviderServer.tickChunks(ChunkProviderServer.java:375)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//net.minecraft.server.v1_16_R1.ChunkProviderServer.tick(ChunkProviderServer.java:346)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//net.minecraft.server.v1_16_R1.WorldServer.doTick(WorldServer.java:329)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//net.minecraft.server.v1_16_R1.MinecraftServer.b(MinecraftServer.java:1104)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//net.minecraft.server.v1_16_R1.DedicatedServer.b(DedicatedServer.java:354)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//net.minecraft.server.v1_16_R1.MinecraftServer.a(MinecraftServer.java:1007)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//net.minecraft.server.v1_16_R1.MinecraftServer.v(MinecraftServer.java:846)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//net.minecraft.server.v1_16_R1.MinecraftServer.lambda$0(MinecraftServer.java:164)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		app//net.minecraft.server.v1_16_R1.MinecraftServer$$Lambda$2984/0x0000000800893040.run(Unknown Source)
[06:59:34] [Spigot Watchdog Thread/ERROR]: 		java.base@11.0.7/java.lang.Thread.run(Thread.java:834)
[06:59:34] [Spigot Watchdog Thread/ERROR]: ------------------------------
[06:59:34] [Spigot Watchdog Thread/ERROR]: Entire Thread Dump:
[07:05:08] [Spigot Watchdog Thread/ERROR]: ------------------------------
[07:05:36] [Spigot Watchdog Thread/ERROR]: Current Thread: Reference Handler
[07:05:36] [Spigot Watchdog Thread/ERROR]: 	PID: 2 | Suspended: false | Native: false | State: RUNNABLE
[07:05:36] [Spigot Watchdog Thread/ERROR]: 	Stack:
[07:05:36] [Spigot Watchdog Thread/ERROR]: 		java.base@11.0.7/java.lang.ref.Reference.waitForReferencePendingList(Native Method)
[07:05:36] [Spigot Watchdog Thread/ERROR]: 		java.base@11.0.7/java.lang.ref.Reference.processPendingReferences(Reference.java:241)
[07:05:36] [Spigot Watchdog Thread/ERROR]: 		java.base@11.0.7/java.lang.ref.Reference$ReferenceHandler.run(Reference.java:213)
[07:05:36] [Spigot Watchdog Thread/ERROR]: ------------------------------
[07:05:36] [Spigot Watchdog Thread/ERROR]: Current Thread: Finalizer
[07:05:36] [Spigot Watchdog Thread/ERROR]: 	PID: 3 | Suspended: false | Native: false | State: WAITING
[07:05:36] [Spigot Watchdog Thread/ERROR]: 	Stack:
[07:05:36] [Spigot Watchdog Thread/ERROR]: 		java.base@11.0.7/java.lang.Object.wait(Native Method)
[07:05:36] [Spigot Watchdog Thread/ERROR]: 		java.base@11.0.7/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:155)
[07:05:36] [Spigot Watchdog Thread/ERROR]: 		java.base@11.0.7/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:176)
[07:05:36] [Spigot Watchdog Thread/ERROR]: 		java.base@11.0.7/java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:170)
[07:05:36] [Spigot Watchdog Thread/ERROR]: ------------------------------
... (more in the log file)


 Comments   
Comment by xtomyserrax [ 28/Jun/20 ]

Hey, you are using the first version released by spigot. After that version, spigot released more than 60 ones. Please try updating your server before reporting a bug. Idk if that crash was fixed but probably it was

Generated at Tue Apr 08 03:01:09 UTC 2025 using Jira 10.3.3#10030003-sha1:d220e3fefc8dfc6d47f522d3b9a20c1455e12b7b.