Direct answer

If shutdown hangs at “Saving world”, do not repeatedly force-kill Java. Collect the last console lines and storage state, then diagnose disk pressure, stalled chunk writes and plugin shutdown hooks.

What it means

The log line describes a phase, not necessarily the exact blocking component. A plugin could still be saving its database, a world may be writing large chunk data, or storage may have stalled.

If you are a player

  1. Avoid repeatedly joining while the server is shutting down. Notify the administrator of the last active actions, such as world backups or large WorldEdit jobs.

If you run the server

  1. Keep a copy of recent logs and backups. Check free space and inode exhaustion on Linux using df -h and df -i. Inspect host-panel disk alerts and I/O wait if available.
  2. If the process is still alive but stalled, use the host’s supported thread-dump facility (jcmd <pid> Thread.print when a compatible JDK/tooling is available). Do not post logs with credentials publicly.
  3. Look for the most recent plugin database or world-save messages. Reproduce only on a backup test instance and disable suspect plugins in a controlled order.
  4. A forced termination may lose unsaved chunk or plugin data. Use it only as a last-resort recovery action after preserving the available evidence and backup.
How to verify the fix

Two normal shutdowns finish cleanly, the server restarts without save/region errors, and a small test world change persists.

References

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000