Minecraft server crashes - [Server Watchdog/FATAL]: A single server tick...

Issue

Minecraft server crashes when computer is resuming from sleep mode.

Minecraft Logs:

[05:11:26] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 23352870ms behind, skipping 467057 tick(s)
[05:11:35] [Server Watchdog/FATAL]: A single server tick took 23361.66 seconds (should be max 0.05)
[05:11:38] [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown.
[05:11:39] [Server Watchdog/ERROR]: This crash report has been saved to: C:\DATA\minecraft_server\.\crash-reports\crash-2014-11-24_05.11.39-server.txt
[05:11:39] [Server Shutdown Thread/INFO]: Stopping server

Resolution

As above logs show, the server is killed bServer Watchdog component of Minecraft server. When computer resumes from sleep, PC time and Minecraft internal time don't match (since Minecraft process is not running while PC is in sleep mode). Minecraft server then adjusts it's internal clock to match PC time (as we can see in logs: Running 23352870ms behind, skipping 467057 tick(s)). This would be all well and good; however, when this happens Minecraft Server Watchdog assumes that something went horribly wrong and kills the server!

To avoid this, edit server.properties file by changing line:

max-tick-time=60000

to

max-tick-time=-1

Setting the value to -1 basically disables the "watchdog" component so regardless of what is the difference between PC  time and internal Minecraft time, server will simply adjust its own time and continue to run.

Windows 8.1 Pro 64bit
Minecraft Server 1.8

Comments  

ME604
# ME604 2015-07-04 20:47
Thank you so much this saved my life

Newsletter

Subscribe to receive occasional updates on new posts.
Your email will not be used for any other purpose and you can unsubscribe at any time.
Please wait