PaperMC / PaperMC/Paper

Paper Console shutdown before all logs are written to it

Open
#13,837 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: low status: accepted version: 26.1.2
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

I would expect the console to print all the logs before shutting down.

Observed/Actual behavior

The console shutdown before all logs are printed to it.

Note: Do not confuse this with the .log file; The .log file is written to normally, it's just not printed in the terminal;

Steps/models to reproduce
  1. Start the server (I used the flags "@ECHO OFF

java -jar server.jar --nogui

PAUSE", I don't know if it's relevant to the cause of the issue)

  1. Log in to the server

  2. Type "stop" in the console

Okay, you will see that the logs in the terminal stop at:

[18:03:48 INFO]: [ChunkHolderManager] Waiting 60s for chunk I/O to halt for world 'minecraft:the_nether'
[18:03:48 INFO]: [ChunkHolderManager] Halted I/O scheduler for world 'minecraft:the_nether'

The following lines do not appear in the console (although they appear in the .log file):

[18:04:38] [Server thread/INFO]: [ChunkHolderManager] Saving all chunkholders for world 'minecraft:the_end'
[18:04:38] [Server thread/INFO]: [ChunkHolderManager] Saved 0 block chunks, 0 entity chunks, 0 poi chunks in world 'minecraft:the_end' in 0.00s
[18:04:38] [Server thread/INFO]: [ChunkHolderManager] Waiting 60s for chunk I/O to halt for world 'minecraft:the_end'
[18:04:38] [Server thread/INFO]: [ChunkHolderManager] Halted I/O scheduler for world 'minecraft:the_end'
[18:04:38] [Server thread/INFO]: ThreadedAnvilChunkStorage (world): All chunks are saved
[18:04:38] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM-1): All chunks are saved
[18:04:38] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM1): All chunks are saved
[18:04:38] [Server thread/INFO]: ThreadedAnvilChunkStorage: All dimensions are saved
[18:04:38] [Server thread/INFO]: Waiting for all RegionFile I/O tasks to complete...
[18:04:38] [Server thread/INFO]: All RegionFile I/O tasks to complete
[18:04:38] [Server thread/INFO]: [MoonriseCommon] Awaiting termination of worker pool for up to 60s...
[18:04:38] [Server thread/INFO]: [MoonriseCommon] Awaiting termination of I/O pool for up to 60s...
Plugin and Datapack List

None

Paper version

version
[18:11:01 INFO]: Checking version, please wait...
[18:11:01 INFO]: This server is running Paper version 26.1.2-51-main@5d62ec0 (2026-04-27T16:54:06Z) (Implementing API version 26.1.2.build.51-beta)
You are running the latest version

Other

Sometimes the console prints two more or two fewer lines than the ones I sent above.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing shutdown with the shown java -jar server.jar --nogui command, then compare terminal output with the .log file. The issue is done when stopping the server prints all shutdown log lines consistently, including the final chunk and I/O messages.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.