BDS-17490Server crash on 1.19.20.02
I have a docker version of minecraft bedrock for MCPE so my kids can play minecraft. Recently it has started crashing each day. I am unable to find a cause of the crash.
I have enabled emit-server-telemetry=true now also, unsure if this helps for future crashes, but this is whats logged so far when the server crashes for everyone.
I can pull more logs if needed and if and when it crashes again. This is just a snippet of what appears to be relevant.
-P
[2022-08-10 20:34:04:928 INFO] Player disconnected: Patsywewe, xuid: 2535449382420588
terminate called without an active exception
[2022-08-10 20:50:35:831 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.19.20.02
OS: Linux
Server start: 2022-08-10 02:02:56 EDT
Dmp timestamp: 2022-08-10 20:50:35 EDT
Upload Date: 2022-08-10 20:50:35 EDT
Session ID: 30760d12-3214-4c65-b20c-ae291d5ab0cc
Commit hash: 1aa76c5813541fe1bbb16c4e3a0af2b29474dc34
Build id: 10811062
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
Crash
[2022-08-10 20:50:35:832 INFO] at raise (UnknownFile:?)
at abort (UnknownFile:?)
at clone (UnknownFile:?)
NO LOG FILE! - Failed to up file descriptor limit Operation not permitted
NO LOG FILE! - setting up server logging...
[2022-08-10 22:40:19:665 INFO] Starting Server
[2022-08-10 22:40:19:665 INFO] Version 1.19.20.02
[2022-08-10 22:40:19:665 INFO] Session ID fc9f1c15-1b53-4997-9c15-f89b409dc584
[2022-08-10 22:40:19:667 INFO] Level Name: Bedrock level
[2022-08-10 22:40:19:670 INFO] Game mode: 0 Survival
[2022-08-10 22:40:19:670 INFO] Difficulty: 2 NORMAL
[2022-08-10 22:40:23:964 INFO] opening worlds/Bedrock level/db
[2022-08-10 22:40:28:015 INFO] IPv4 supported, port: 19132
[2022-08-10 22:40:28:015 INFO] IPv6 not supported
[2022-08-10 22:40:29:746 INFO] Server started.
[2022-08-10 22:40:29:770 INFO] IPv4 supported, port: 50231
[2022-08-10 22:40:29:770 INFO] IPv6 not supported
[2022-08-10 22:40:29:797 INFO] ================ TELEMETRY MESSAGE ===================
[2022-08-10 22:40:29:797 INFO] Server Telemetry is currently not enabled.
[2022-08-10 22:40:29:797 INFO] Enabling this telemetry helps us improve the game.
[2022-08-10 22:40:29:797 INFO]
[2022-08-10 22:40:29:797 INFO] To enable this feature, add the line 'emit-server-telemetry=true'
[2022-08-10 22:40:29:797 INFO] to the server.properties file in the handheld/src-server directory
[2022-08-10 22:40:29:797 INFO] ======================================================
[2022-08-10 22:41:02:908 INFO] Player connected: Parzival3724, xuid: 2535456280667077
[2022-08-10 22:41:33:871 INFO] Player disconnected: Parzival3724, xuid: 2535456280667077
[2022-08-10 22:42:50:253 INFO] Player connected: Patsywewe, xuid: 2535449382420588
terminate called without an active exception
[2022-08-10 22:43:45:321 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.19.20.02
OS: Linux
Server start: 2022-08-10 22:40:18 EDT
Dmp timestamp: 2022-08-10 22:43:45 EDT
Upload Date: 2022-08-10 22:43:45 EDT
Session ID: fc9f1c15-1b53-4997-9c15-f89b409dc584
Commit hash: 1aa76c5813541fe1bbb16c4e3a0af2b29474dc34
Build id: 10811062
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
Crash
[2022-08-10 22:43:45:322 INFO] at raise (UnknownFile:?)
at abort (UnknownFile:?)
at clone (UnknownFile:?)
NO LOG FILE! - Failed to up file descriptor limit Operation not permitted
NO LOG FILE! - setting up server logging...
[2022-08-10 22:52:58:819 INFO] Starting Server
[2022-08-10 22:52:58:819 INFO] Version 1.19.20.02
[2022-08-10 22:52:58:819 INFO] Session ID 8503616c-1d23-41bd-b5b0-36b43f5e041c
[2022-08-10 22:52:58:821 INFO] Level Name: Bedrock level
[2022-08-10 22:52:58:830 INFO] Game mode: 0 Survival
[2022-08-10 22:52:58:830 INFO] Difficulty: 2 NORMAL
[2022-08-10 22:53:01:565 INFO] opening worlds/Bedrock level/db
[2022-08-10 22:53:05:144 INFO] IPv4 supported, port: 19132
[2022-08-10 22:53:05:144 INFO] IPv6 not supported
[2022-08-10 22:53:06:817 INFO] Server started.
[2022-08-10 22:53:06:840 INFO] IPv4 supported, port: 40746
[2022-08-10 22:53:06:840 INFO] IPv6 not supported
Linked Issues
Comments9
History5
Resolution: Unresolved → Awaiting Response
Resolution: Awaiting Response → Unresolved
Added duplicates link: BDS-17527Multiple server crashes due to memory leak when loading chunksFixed
Resolution: Unresolved → Duplicate
Added Security Level: Minecraft - Private
I have the same issue, except I get "exited with code 255"
Hi
Are you using any resource/behavior packs?
This ticket will automatically reopen when you reply.
Hi @Maciej,
Actually everything is vanilla with no modifications and custom skins or packs are actually disallowed on this server so connecting clients cannot make use of 3rd party stuff either. Also xbox login is enforced so that clients who connect must have a microsoft account in addition. However two changes were made to accomodate my kids requests, coordinates are shown and also "keep inventory" is on as they complain if they lose everything when they die. Other than those 2 settings everything should be default.
P
I have managed to get some information regarding this crash as well as find how to recreate it. One of the kids friends who plays with them went to the end and dug down to very low on the map (y 1?) and then built a straight line out for a long time (120-130 blocks) using the end blocks (unsure of terminology here). They then placed blocks on this line of blocks and can mine them but the mined blocks do not enter their inventory - however if you then try to walk back along this long bridge (after mining?) after a short walk the server crashes. If you then go back into the end after restarting the server the blocks have regenerated as if you never mined them which makes me think they found some way to duplicate blocks but it also seems to crash the server when performing these steps. Unsure if they perform a different sequence of steps or something similar but either way this can be done and it crashes the server every single time, and there is no way to get rid of the bridge they have constructed which means any player can connect, go to the end and crash the server now.
P
BDS has been incredibly unstable for me as well. Running on Linux in this situation.
At the moment the situation I am in is any kid in the neighbourhood can cause a denial of service attack against my server by going to the end and mining a block, requiring manual intervention to fix. The kids squabble a lot so this is surprisingly common. Kind of a major issue imo.
Any update on this?
P
Thank you for your report!
We're tracking this issue in
BDS-17527, so this ticket is being resolved and linked as a duplicate.If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
That linked ticket is not publicly viewable so I cannot see it or any information on it.