Crash detection
Stratum notices crashes, finds the cause in the console and starts the server again, unless a restart cannot help.
Stratum → Servers → Crash detection. When it is on, the panel checks every server every 30 seconds and every server gets a Crashes page.
How a crash is found
The panel remembers every start and stop that goes through it, also from schedules. A server that goes offline without anyone stopping it has crashed. A normal shutdown in the console (for example stop typed in the game) is not counted.
The last console lines are saved with the crash, and the cause is read from them: out of memory, wrong Java version, EULA not accepted, port in use, missing mods or plugins, a broken world and more.
What happens next
| Situation | Action |
|---|---|
| Normal crash | Restarted after a short wait. The wait doubles with every further crash. |
| Cause a restart cannot fix | Not restarted. The owner gets the cause and the steps to fix it. |
| Too many crashes in a row | Crash loop: restarts pause until someone starts the server. |
| Auto-restart off | Only recorded and reported. |
Which causes count as "a restart cannot fix this" is your choice. By default: EULA, wrong Java, missing server jar, missing mods, file permissions, missing Node.js or Python modules.
Settings
Prop
Type
Per server
Admins can force auto-restart on or off for single servers: on the admin server page under Package & Splits, or in the Per server list on the crash page. The owner cannot change it then.
Freeze detection
A server can run and still be stuck. With freeze detection on, Stratum asks the game (the same query as Player statistics). After several failed answers in a row it restarts the server. The first minutes after a start are skipped, so big modpacks can load.
The Crashes page
Owners see every crash with its cause, the fix, what was done, how long the server was down and the console before the crash. A waiting restart can be cancelled. When memory was the cause and Upgrades are on, the page links to them.
Notifications
- Email to the owner when the server needs help: crash loops, causes a restart cannot fix, failed restarts. Optionally after every restart too.
- Discord: pick a channel for Server crashes under Discord alerts.
Suggestions
Keep the default "do not restart" causes. A server without an accepted EULA would otherwise start and stop in a loop. Wings can restart crashed servers by itself too; Stratum sees that and records it as "restarted by the node".