1 warning found. Every finding below comes from what was actually in the pasted files. Treat the fixes as suggestions: they cover the common causes, and this case may need more digging.
FabricMinecraft 26.2
What this error means, and every way to fix it →
The tick loop fell 6047ms behind, 120 ticks in one go
A tick took far longer than the 50ms it is allowed, so the server ran behind real time and skipped ahead to catch up (once in this log). Players see rubber-banding, delayed block breaks and mobs that stutter. One burst after a restart, a world upgrade or a chunk pre-generation run is normal. A steady stream is lag with a cause: profile it with spark (/spark profiler start --timeout 120 in the console) rather than guessing. The usual culprits are view-distance and simulation-distance set too high, entity or item build-ups, chunks generating live as players explore, and garbage collection pauses when the heap is too small.
Hosting with the headroom to keep up →Why this happens: Diagnosing server lag →jump to line 16219 sensitive values (addresses, passwords and the like) were stripped before this page was stored.
As received, after redaction.
Need more help or want to discuss your issue further? Join our Discord and bring the link to this page.
Join our DiscordRun a community? Add the Roastd bot and anyone can roast a crash log in your support channel.
Add the Roastd botGot a server of your own that deserves a second opinion?
Roast your own serverRoastd is a free tool built by Hostd. This diagnosis stays put. The log it was read from is deleted on a timer.