PaperMC / PaperMC/Paper

Minecraft server crashes and fills my logs

Open
#12,003 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: needs triage version: 1.21.4
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Stack trace

https://mclo.gs/dqO62Wz

Plugin and Datapack List

AdvancedTeleport, BetterChairs, BetterMessages, MiniMOTD, PingDisplay, Plan, ProtocolLib, SeeMore, ViaBackwards, ViaVersion

Actions to reproduce (if known)

No response

Paper version

This server is running Paper version 1.21.4-121-main@88bbead (2025-01-22T20:05:15Z) (Implementing API version 1.21.4-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.4-118-73f7736 (MC: 1.21.4)

Other

I use https://github.com/itzg/docker-minecraft-server and here is my docker compose file:

services:
  mc:
    image: itzg/minecraft-server
    container_name: paper
    labels:
      - traefik.enable=true
      - traefik.http.routers.http-analytics.entryPoints=http
      - traefik.http.routers.http-analytics.rule=Host(`analytics.gregtech.eu`)
      - traefik.http.middlewares.https_redirect.redirectscheme.scheme=https
      - traefik.http.middlewares.https_redirect.redirectscheme.permanent=true
      - traefik.http.routers.http-analytics.middlewares=https_redirect
      - traefik.http.routers.https-analytics.entryPoints=https
      - traefik.http.routers.https-analytics.rule=Host(`analytics.gregtech.eu`)
      - traefik.http.routers.https-analytics.service=analytics
      - traefik.http.routers.https-analytics.tls=true
      - traefik.http.services.analytics.loadbalancer.server.port=8804
      - traefik.http.routers.https-analytics.tls.certResolver=le-ssl
    environment:
      EULA: "true"
      TYPE: PAPER
      VIEW_DISTANCE: 32
      SIMULATION_DISTANCE: 32
      MEMORY: 7000M
      USE_AIKAR_FLAGS: true
    ports:
      - "25565:25565"
      - "45999:45999"
    volumes:
      - ./data:/data
    restart: always
volumes:
  mc-paper: {}
networks:
  default:
    name: traefik_access
    external: true

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 inspecting the linked stack trace and compare it with the listed Paper version, plugins, datapacks, and Docker Compose setup. Reproduce the crash with the reported configuration or isolate the triggering component; done means the cause is identified and the server no longer crashes or fills the logs.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, java
Domain
backend, game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.