How to start, stop, restart or kill a server on Schokr
Learn the difference between start, stop, restart and kill on Schokr, when to use each one and what to do if a server will not stop.
Updated · 2 min read
You control your server's power from its console page. Start boots it, Stop shuts it down cleanly, Restart does both, and Kill forces it off immediately.
The four power actions
| Action | What it does | When to use it |
|---|---|---|
| Start | Runs the startup command | Server is offline |
| Stop | Asks the server to shut down cleanly | Normal shutdowns, before editing important files |
| Restart | Stops, then starts again | Applying config changes, new plugins or new code |
| Kill | Ends the process immediately | Only when Stop does not work |
Stop vs kill
Stop sends the server its normal shutdown command (for example stop on Minecraft) so it can save the world, close files and disconnect players properly. This can take a few seconds or longer on big worlds.
Kill ends the process instantly, like pulling the power cable. Anything not yet saved is lost, and files that were being written can be corrupted. Use kill only when a server is frozen and Stop has done nothing for a minute or two.
Restart after changes
Most software only reads its config at startup. Restart after:
- Editing config files such as
server.propertiesorconfig.yml - Adding or removing plugins and mods
- Uploading new code for a bot or app
- Changing Startup variables or the startup command
- Changing memory, CPU or disk in the Resources section
Automatic restarts
You do not need to restart by hand every day. Use a schedule to restart on a timer, optionally warning players first. See schedules and automatic restarts.
Do servers stop on their own?
Schokr servers do not sleep when idle. They keep running until you stop them, they crash or they are killed for running out of memory. If your server keeps turning off:
- Check the console for a crash or error.
- If the process was killed for exceeding memory, see out of memory errors.
- For bots, a code error that ends the process stops the server too. Add error handling so one failed command does not crash the whole bot.
The server will not stop
- Wait a minute. Large Minecraft worlds can take a while to save.
- Check the console. A plugin might be blocking shutdown.
- If nothing changes, use Kill.
- Before the next start, check for corrupted files if the server was in the middle of saving.
The server will not start
See server stuck starting or won't start.
Permissions
In a team, power actions are a separate permission. You can let someone view the console without letting them stop or restart the server. See team roles and permissions.