Preserve the evidence first
Do not repeatedly force-stop the server while it is initializing or downloading Workshop content. Copy the current console file and logs.zip, note the last action, and back up the server save before editing a database or removing content mods.
- Reproduce one failed start and keep the complete log from that attempt.
- Read upward from the termination line until you reach the first exception, missing item, memory message, port error, or named file.
- If a Workshop item or mod is named, confirm its download, dependencies, Mod ID, and server/client load order.
- If the log reports memory exhaustion, reduce the mod set or increase appropriate server memory; do not treat it as a file-corruption problem.
- If a port is unavailable, stop the other process or correct the server port configuration.
- If a particular database or map file is named, back up the server and investigate only that file.
Match one of these branches
- Missing Workshop item or map dependency: repair the download and required-item chain before restarting.
- Mod exception during world creation: test a new world with that mod group disabled.
- Out of memory: adjust memory and reduce load; deleting a save does not address the signature.
- Port already in use: identify the conflicting server process or configuration.
- Named database or world file: treat it as a targeted corruption case and preserve a backup before any change.
Sources
The Indie Stone support: modded multiplayer termination — Official support case showing signature-based diagnosis.
Steam support: dedicated server termination — Support discussion of a server termination case.
Build 42 server terminated discussion — Community report with staff guidance; apply only to matching logs.