itzg / itzg/docker-minecraft-bedrock-server
Minecraft server crashing
- Dominant language
- Shell
- Stars
- 1.9k
- Forks
- 302
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 2
Description
My minecraft server has crashed and stopped working. i have tried setting up new server but got same issue:
Host: Kubernetes
All configurations are done via config
```
EULA: "TRUE" # Must accept EULA to use this minecraft server
GAMEMODE: "survival" # Options: survival, creative, adventure
DIFFICULTY: "easy" # Options: peaceful, easy, normal, hard
DEFAULT_PLAYER_PERMISSION_LEVEL: "member" # Options: visitor, member, operator
LEVEL_NAME: "Bedrock level"
#LEVEL_SEED: "33480944"
SERVER_NAME: "Minecraft Server"
SERVER_PORT: "19132"
SERVER_PORT_V6: "19133"
#LEVEL_TYPE: "DEFAULT" # Options: FLAT, LEGACY, DEFAULT
ALLOW_CHEATS: "true" # Options: true, false
MAX_PLAYERS: "10"
PLAYER_IDLE_TIMEOUT: "30"
TEXTUREPACK_REQUIRED: "true" # Options: true, false
#
## Changing these will have a security impact
ONLINE_MODE: "true" # Options: true, false (removes Xbox Live account requirements)
WHITE_LIST: "false" # If enabled, need to provide a whitelist.json by your own means.
#
## Changing these will have a performance impact
#VIEW_DISTANCE: "10"
#TICK_DISTANCE: "4"
#MAX_THREADS: "8"
UID: "1002"
PID: "1002"
GID: "1002"
PACKAGE_BACKUP_KEEP: "2"
```
strange observation in logs on
```
[2021-12-24 21:48:54:111 INFO] IPv4 supported, port: 0
[2021-12-24 21:48:54:111 INFO] IPv6 supported, port: 0
```
Full log
```
time="2021-12-24T21:48:53Z" level=debug msg="Using /data to match uid and gid"
time="2021-12-24T21:48:53Z" level=debug msg="Resolved 1002 from environment variable UID"
time="2021-12-24T21:48:53Z" level=debug msg="Resolved 1002 from environment variable GID"
time="2021-12-24T21:48:53Z" level=debug msg="stdin is detached, so forwarding is disabled"
Looking up latest version...
Starting Bedrock server...
NO LOG FILE! - [] setting up server logging...
[2021-12-24 21:48:53:624 INFO] Starting Server
[2021-12-24 21:48:53:624 INFO] Version 1.18.2.03
[2021-12-24 21:48:53:624 INFO] Session ID a8ae1eef-d728-4e1a-a995-914413947ffb
[2021-12-24 21:48:53:625 INFO] Level Name: Bedrock level
[2021-12-24 21:48:53:625 INFO] Game mode: 0 Survival
[2021-12-24 21:48:53:625 INFO] Difficulty: 1 EASY
[2021-12-24 21:48:53:654 INFO] opening worlds/Bedrock level/db
[2021-12-24 21:48:54:111 INFO] IPv4 supported, port: 0
[2021-12-24 21:48:54:111 INFO] IPv6 supported, port: 0
[2021-12-24 21:48:54:134 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.18.2.03
OS: Linux
Server start: 2021-12-24 21:48:53 UTC
Dmp timestamp: 2021-12-24 21:48:54 UTC
Upload Date: 2021-12-24 21:48:54 UTC
Session ID: a8ae1eef-d728-4e1a-a995-914413947ffb
Commit hash: 74c6ce6eb10dfe6b481aa14578b375b50a5d2028
Build id: 7966228
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
Crash
[2021-12-24 21:48:54:134 INFO]
Failed to open curl lib from binary, use libcurl.so instead
```
Contributor guide
Research direction
Start with the supplied Kubernetes configuration and the full Bedrock startup log, especially the reported port 0 values and crash details. Reproduce the startup using the same configuration and collect the container and Kubernetes logs; done means identifying a reproducible cause and documenting the required configuration or confirming an upstream failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100