[SPIGOT-6306] Watchdog thread cannot be disabled Created: 05/Jan/21  Updated: 18/Mar/21  Resolved: 11/Jan/21

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

Type: Bug Priority: Minor
Reporter: H. K. Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: crash
Environment:

docker container image: itzg/minecraft-server
running on a debian/linux
8Core 16GB ram cloud server
no plugins / minimal changed configuration.

docker compose:
{{version: '3.6'
services:
minecraft:
container_name: vanilla
image: itzg/minecraft-server
ports:

  • "25565:25565"

environment:
EULA: "TRUE"
TYPE: "SPIGOT"

USE_AIKAR_FLAGS: "true"
ENABLE_AUTOPAUSE: "FALSE"
AUTOPAUSE_TIMEOUT_EST: "7200"
AUTOPAUSE_TIMEOUT_KN: "240"
TZ: "Europe/Berlin"
MEMORY: "4G"

volumes:

  • "~/mc/data:/data"}}

Attachments: File latest.log     Text File server.properties     File spigot.yml    
Version: latest (cannot run /version)
Guidelines Read: Yes

 Description   

The Server is running in a docker container useing the base configuration. The tick timeout has been changed to -1 to disable the watchdog for use with the AUTOPAUSE feature of the docker image. the feature is disabled in the docker compose for testing, but since the crash remained it is not related to this.
Sadly the log file is not of any help to me, I cant figure out what the issue is.

The server should have enough power for a basic vanilla server, as i was running All-The-Mods-6 on it without any issues.

(#####) has been added to the server.properties file to obfuscate the name of the server... Was only Alphabetical name.

 Comments   
Comment by Philip Papp [ 18/Mar/21 ]

Hi, any information for what version this fix was rolled into?

Comment by H. K. [ 05/Jan/21 ]

This bug seems to be related to tick_timeout not supporting the Minecraft Servers max_tick_time option of -1 for no timeout.
This should maybe be added, as it can be a usefull feature if the server Watchdog shall not kill the server if paused.
This would also be usefull if useing a Debugger on the server for debugging plugins, as this would also trigger the Watchdog to shutdown the server.

EDIT: this issue not only occures if set to negativ or 0, to high of a value results in the same error. Have not figured out what the max value is.

Generated at Thu Sep 04 22:38:20 UTC 2025 using Jira 10.3.9#10030009-sha1:eff8913ed2270ee44ab422c3609af4c4f36536d0.