[SPIGOT-4656] Watchdog Timeout Crash/Shutdown Created: 07/Mar/19 Updated: 08/Mar/19 Resolved: 08/Mar/19 |
|
Status: | Resolved |
Project: | Spigot |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | Priority: | Major |
Reporter: | Luke | Assignee: | Unassigned |
Resolution: | Invalid | Votes: | 0 |
Labels: | 1.13.2, Crash, Spigot, watchdog | ||
Environment: |
Dual Xeon x5690 3.47Ghz 128GB DDR3 Ram Server allocated 10G of that. Windows Server 2008 R2 Enterprise OS Java V8 update 191 Build 1.8.0_191-b12 Spigot 1.13.2 version: CraftBukkit version git-Spigot-3cb9dcb-7 7ca7ca (MC: 1.13.2) (Implementing API version 1.13.2-R0.1-SNAPSHOT) (Fresh download/compile with Git bash) |
Version: | CraftBukkit version git-Spigot-3cb9dcb-7 7ca7ca (MC: 1.13.2) (Implementing API version 1.13.2-R0.1-SNAPSHOT) |
Plugin: | None |
Guidelines Read: | Yes |
Description |
Server watchdog timeout as soon as started. Offline mode in latest.log because this is part of a Bungee network Server latest.log https://pastebin.com/grKjurtd Last 3 lines of log cut off are just worlds End and Nether saving and the server starting over in a loop Installed plugins: None Originally tested with plugins but removed them all to do trial and error testing, Didn't even get to install one plugin before it had issues. |
Comments |
Comment by md_5 [ 08/Mar/19 ] |
The logs did state: [22:13:40] [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 |
Comment by Luke [ 08/Mar/19 ] |
I have just found out about the "optimization" thing required to be done to worlds moving from 1.12.2 to 1.13+ Sadly nowhere was this mentioned in the server logs that I had to do this, no errors or anything. |
Comment by Luke [ 07/Mar/19 ] |
Updated Java to build V8 Update 201 Build 1.8.0_201-b09 Issue still persists. |