[BDS-10666] Server bedrock crash during the game Created: 17/Dec/20 Updated: 22/Feb/21 Resolved: 10/Feb/21 |
|
| Status: | Resolved |
| Project: | Bedrock Dedicated Server |
| Affects Version/s: | 1.16.201 Hotfix |
| Fix Version/s: | 1.16.201.03 Hotfix |
| Type: | Bug | ||
| Reporter: | Radoslaw P. | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 30 |
| Labels: | None | ||
| Environment: |
Ubuntu 20.04.1 LTS |
||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Confirmation Status: | Community Consensus | ||||||||||||||||||||||||||||||||||||
| Description |
|
Version: 1.16.201.2 Crash |
| Comments |
| Comment by Ali Ershad-Manesh [ 22/Feb/21 ] |
|
Hey Joe, this is a closed source program. I doubt they are willing to discuss the issues and mistakes with their code. |
| Comment by Joe Colafrancesco [ 22/Feb/21 ] |
|
I pulled down a new server into my Docker environment, copied over the world files and can confirm that all looks good. No more crash that once was very consistent. Not that everyone cares but I'm an IT geek - any way know what the issue was and what the fix was? Always love seeing some insight into the code and the fix for a bug! |
| Comment by Ruli Manurung [ 12/Feb/21 ] |
|
Same here – upgraded the BDS 2 days ago and things seem to be running OK so far. Thanks for the fix! |
| Comment by Joost Bruining [ 12/Feb/21 ] |
|
Testing here, looking good so far - chalk up one more 'seems fixed'. Thanks for addressing this! We had a rather large no-go zone in our world that we are glad to return to. |
| Comment by Frederic [ 10/Feb/21 ] |
|
I tested my own use case that used to crash, and it also seems fixed. I will move into the cautiously optimistic camp also. |
| Comment by Stephen [ 10/Feb/21 ] |
|
After doing a quick test, the issue seems resolved. Will require further testing before I am convinced. Cautiously optimistic.. |
| Comment by [Mojang] Mega_Spud (Jay Wells) [ 10/Feb/21 ] |
|
We believe this issue is fixed in the server fix that went out yesterday - Bedrock Dedicated Server software 1.16.201.03, available at https://www.minecraft.net/en-us/download/server/bedrock/ |
| Comment by ace earvin arellano [ 10/Feb/21 ] |
|
hey guys they just released a new version of the server, they said that the issues are fixed including this bug with the village |
| Comment by Simon Carpentier [ 09/Feb/21 ] |
|
Had this crash as well on Linux server. I have a village chunk with 20+ beds, two of which are right next to each other. Same world does not crash on Windows. |
| Comment by Chris David [ 09/Feb/21 ] |
|
Also seeing this issue. First noticed it on Realms. Then stood up my own linux server and could see the error log, and it's the same issue as this. If any Mojang developer needs help reproducing please let me know. I have a world that reliably reproduces this issue. thanks. |
| Comment by ace earvin arellano [ 29/Jan/21 ] |
|
same as mine, it happened a week ago only in a specific village near my base(other villages is fine, we are managing 4 villages), i have tried switching servers and reinstalling ubuntu server 20.04 but it still causes the same issue and after several crashes it finally stopped then all of my villagers and traders near my base despawned even with the nametag RIP! right now im fine with no villagers than rebuilding all my structures |
| Comment by Joost Bruining [ 28/Jan/21 ] |
|
We hit the issue on our Bedrock server as well, similar crash stack:
[INFO] Package: com.mojang.minecraft.dedicatedserver Version: 1.16.201.2 OS: Linux Server start: 2021-01-27 20:45:43 PST Dmp timestamp: 2021-01-27 20:47:53 PST Upload Date: 2021-01-27 20:47:53 PST Session ID: 2bf4a1fd-8a19-4d84-b30b-075036697657 Commit hash: Build id: development CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293 Crash [INFO] at std::__shared_count<[__gnu_cxx::_Lock_policy]2>::__shared_count[std::__weak_count<[__gnu_cxx::_Lock_policy]2> const&, std::nothrow_t] (UnknownFile:?) at std::__shared_ptr<POIInstance, [__gnu_cxx::_Lock_policy]2>::__shared_ptr[std::__weak_ptr<POIInstance, [__gnu_cxx::_Lock_policy]2> const&, std::nothrow_t] (UnknownFile:?) at std::shared_ptr<POIInstance>::shared_ptr[std::weak_ptr<POIInstance> const&, std::nothrow_t] (UnknownFile:?) at std::weak_ptr<POIInstance>::lock[] const (UnknownFile:?) at Village::getBedPOICount[] const (UnknownFile:?) at Village::tick[Tick, BlockSource&] (UnknownFile:?) at VillageManager::tickVillages[Tick const&, Vec3 const&, BlockSource&] (UnknownFile:?) at ServerPlayer::tickWorld[Tick const&] (UnknownFile:?) at std::function<bool [Player&]>::operator[][Player&] const (UnknownFile:?) at Level::forEachPlayer[std::function<bool [Player&]>] (UnknownFile:?) at Level::tick[] (UnknownFile:?) at ServerLevel::tick[] (UnknownFile:?) at GameSession::tick[] (UnknownFile:?) at Minecraft::tickSimtime[int, int] (UnknownFile:?) at Minecraft::update[] (UnknownFile:?) at ServerInstance::_update[] (UnknownFile:?) at clone (UnknownFile:?)
We did a bunch of testing, including killing off all villagers in the affected chunk, attempting to remove all beds - made no difference. The issue occurs in the chunk containing -1871, -2140, world files uploaded for testing purposes: https://drive.google.com/file/d/1egoKVwvqRxNqzu9LZ7j72UvQktkDHz9T/view?usp=sharing Let me know if further testing and/or access is needed, we're not shy. |
| Comment by Joe Colafrancesco [ 28/Jan/21 ] |
|
server.properties World file - https://drive.google.com/drive/folders/1K2Ox7PXnxEkbP1Z0wygXqp2u3t3dlEpG?usp=sharing |
| Comment by Ali Ershad-Manesh [ 27/Jan/21 ] |
|
I checked the server last night the world was corrupted and server was not working. The server has been offline (no access from users) but has been running. It seems like a couple of weeks ago the server somehow corrupted the world. I have nightly backups and restored the world from couple of weeks ago (after going back through several days of broken worlds) and everything is back to the way it was. This makes me wonder if a server crash, or the server just running idle by itself can actually corrupt the world. I guess I will find out in a couple of days that the server has been running to see if the world goes bad again. If that is the case this is yet another problem with this version. |
| Comment by Marius Petcu [ 27/Jan/21 ] |
|
I got the same crash with the same call stack reproducing when players were around our village (we made a village near our base). After one of the crashes, some of the villagers despawned. The world is too big to attach here, but here's my server.properties and the two Dockerfiles that I tried: Version: 1.16.201.2 OS: Linux Server start: 2021-01-25 23:07:58 UTC Dmp timestamp: 2021-01-25 23:30:20 UTC Upload Date: 2021-01-25 23:30:20 UTC Session ID: 7d975cd1-003c-4497-bd3c-716266ac4c9b Commit hash: Build id: development CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293 Crash [INFO] at std::__shared_count<[__gnu_cxx::_Lock_policy]2>::__shared_count[std::__weak_count<[__gnu_cxx::_Lock_policy]2> const&, std::nothrow_t] (UnknownFile:?) at std::__shared_ptr<POIInstance, [__gnu_cxx::_Lock_policy]2>::__shared_ptr[std::__weak_ptr<POIInstance, [__gnu_cxx::_Lock_policy]2> const&, std::nothrow_t] (UnknownFile:?) at std::shared_ptr<POIInstance>::shared_ptr[std::weak_ptr<POIInstance> const&, std::nothrow_t] (UnknownFile:?) at std::weak_ptr<POIInstance>::lock[] const (UnknownFile:?) at Village::getBedPOICount[] const (UnknownFile:?) at Village::tick[Tick, BlockSource&] (UnknownFile:?) at VillageManager::tickVillages[Tick const&, Vec3 const&, BlockSource&] (UnknownFile:?) at ServerPlayer::tickWorld[Tick const&] (UnknownFile:?) at std::function<bool [Player&]>::operator[][Player&] const (UnknownFile:?) at Level::forEachPlayer[std::function<bool [Player&]>] (UnknownFile:?) at Level::tick[] (UnknownFile:?) at ServerLevel::tick[] (UnknownFile:?) at GameSession::tick[] (UnknownFile:?) at Minecraft::tickSimtime[int, int] (UnknownFile:?) at Minecraft::update[] (UnknownFile:?) at ServerInstance::_update[] (UnknownFile:?) at clone (UnknownFile:?) |
| Comment by Marius Petcu [ 27/Jan/21 ] |
|
@Joe Colafrancesco Can you attach the world files, your `server.properties` and your Dockerfile here? This would make it easier for the devs to reproduce. |
| Comment by Joe Colafrancesco [ 27/Jan/21 ] |
|
Have the same issue - I can reproduce on demand. Some further clarity: Version: 1.16.201.2 Crash |
| Comment by Jeff [ 25/Jan/21 ] |
|
Followed the steps. Did not crash. |
| Comment by Frederic [ 24/Jan/21 ] |
|
| Comment by Jeff [ 24/Jan/21 ] |
|
Need to get confirmation status changed to confirmed. Is there a verified way to reproduce this issue? |
| Comment by Ali Ershad-Manesh [ 23/Jan/21 ] |
|
My question at this point is: is this site even being monitored by the developers at all? If these people can't maintain their own software, they may either discontinue the product or just make the server opensource so people can fix this themselves. It has been over 5 weeks since they release the update. They have had enough time to start looking at the bug report. Maybe I'm misunderstanding something here... This site is where the bugs for the Minecraft Bedrock Edition Dedicated servers are reported to the developers, correct? or at least I was under the impression that this was the place... am I at the wrong place? |
| Comment by slamdunx [ 21/Jan/21 ] |
|
@Jam approximately 5 hours of play since villagers had somewhere to sleep again and no server crashes to report. Hope it is something that can be fixed as easily as moving the null-pointer check and that it can be fixed across the whole code-base so that we don't find it elsewhere. |
| Comment by Jeff [ 20/Jan/21 ] |
|
You're probably right. That a null check can be so catastrophic tho... |
| Comment by Ian Rehwinkel [ 20/Jan/21 ] |
|
This seems to be an issue with locking a weak_ptr. By debugging i've found, that the weak_ptr being locked is null, which causes a segfault. Since MSVC and gcc/clang have different implementations of the standard library, it might be related to that. I've seen that there is a null-check for a pointer, but only after locking. I believe this would be a simple fix, simply by checking for null before locking the weak_ptr. |
| Comment by Jeff [ 20/Jan/21 ] |
|
Could this be a ticking entity problem? I've seen ways to fix this on other platforms but not for worlds on BDS. |
| Comment by Jam [ 19/Jan/21 ] |
|
@slamdunx thanks for the info, it would be good to get an update on how your server is going after rebuilding the village. |
| Comment by slamdunx [ 19/Jan/21 ] |
|
Having looked at the error message and reviewed |
| Comment by Christopher Haws [ 18/Jan/21 ] |
|
I ended up switching to the Windows version of BDS which doesn't have this issue. It also seems to run a lot better than the linux version in general (less bugs, chunk load times are much quicker, NPC's don't glitch out all the time, and it uses way less system resources). This is really unfortunate since I prefer to host the server using docker and not on a VM, but oh well. Hope the Mojang team can fix these issues soon! |
| Comment by Jam [ 17/Jan/21 ] |
|
I can confirm that I'm experiencing a very similar issue, my player is in a large village and the server disconnects / crashes within a minute or so of logging in. Journalctl output shows the Village::getBedPOICount[] const (UnknownFile:?) error line. It does seem like a recent system update could have caused the issue since I had updated very recently.
Linux 5.10.7-arch1-1 x86_64 GNU/Linux
$ for i in $(ldd bedrock_server | cut -f 3 -d ' '); do readlink $i; done libcurl.so.4.7.0 libpthread-2.32.so libdl-2.32.so libstdc++.so.6.0.28 libm-2.32.so libc-2.32.so ld-2.32.so libnghttp2.so.14.20.0 libidn2.so.0.3.7 libssh2.so.1.0.1 libpsl.so.5.3.3 libgssapi_krb5.so.2.2 libkrb5.so.3.3 libk5crypto.so.3.1 libcom_err.so.2.1 libzstd.so.1.4.5 libz.so.1.2.11 libunistring.so.2.1.0 libkrb5support.so.0.1 libkeyutils.so.1.10 libresolv-2.32.so
|
| Comment by Andras Katona [ 17/Jan/21 ] |
|
We switched to realm where this issue seemed not happening, and worked fine for a while. But now it looks very similar there too. When my friend joins the realm crashes and rolls back. He's in a big village, and I'm suspecting it has to do with bed searching villagers and this bug. |
| Comment by Jeff [ 11/Jan/21 ] |
|
Did a package update too. Among them was this one... |
| Comment by Sean Kennedy [ 10/Jan/21 ] |
|
ok I was able to get a working version of the server. My process on the build was minimize the updating. Commands I ran to get the ubuntu lxc running:
apt install wget
wget https://minecraft.azureedge.net/bin-linux/bedrock-server-1.16.201.02.zip
apt install unzip
unzip *zip
LD_LIBRARY_PATH=. ./bedrock_server
Got a libcurl error
apt install libcurl3
LD_LIBRARY_PATH=. ./bedrock_server
Got a libssl error 1.1.1 needed
apt update
apt install libssl1.1
LD_LIBRARY_PATH=. ./bedrock_server
Started running. Stopped.
Copied world that is disconnecting into the worlds dir
LD_LIBRARY_PATH=. ./bedrock_server
Started running.
Testing world - no disconnects occuring!
root@bds-test:~# more /etc/os-release NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic root@bds-test:~# uname -a Linux bds-test 5.4.73-1-pve #1 SMP PVE 5.4.73-1 (Mon, 16 Nov 2020 10:52:16 +0100) x86_64 x86_64 x86_64 GNU/Linux root@bds-test:~# apt list --installed | egrep "libc|libssl|libstd" klibc-utils/bionic,now 2.0.4-9ubuntu2 amd64 [installed] libc-bin/bionic,now 2.27-3ubuntu1 amd64 [installed,upgradable to: 2.27-3ubuntu1.4] libc6/bionic,now 2.27-3ubuntu1 amd64 [installed,upgradable to: 2.27-3ubuntu1.4] libcap-ng0/bionic,now 0.7.7-3.1 amd64 [installed] libcap2/bionic,now 1:2.25-1.2 amd64 [installed] libcap2-bin/bionic,now 1:2.25-1.2 amd64 [installed] libcom-err2/now 1.44.1-1ubuntu1 amd64 [installed,upgradable to: 1.44.1-1ubuntu1.3] libcryptsetup12/now 2:2.0.2-1ubuntu1.1 amd64 [installed,upgradable to: 2:2.0.2-1ubuntu1.2] libcurl3/bionic,now 7.58.0-2ubuntu2 amd64 [installed] libklibc/bionic,now 2.0.4-9ubuntu2 amd64 [installed] libssl1.0.0/now 1.0.2n-1ubuntu5.2 amd64 [installed,upgradable to: 1.0.2n-1ubuntu5.5] libssl1.1/bionic-updates,bionic-security,now 1.1.1-1ubuntu2.1~18.04.7 amd64 [installed] libstdc++6/bionic-updates,bionic-security,now 8.4.0-1ubuntu1~18.04 amd64 [installed] root@bds-test:~# for i in $(ldd bedrock_server | cut -f 3 -d ' '); do readlink $i; done libcurl.so.4.5.0 libpthread-2.27.so libdl-2.27.so libstdc++.so.6.0.25 libm-2.27.so libc-2.27.so libnghttp2.so.14.15.2 libidn2.so.0.3.3 libpsl.so.5.2.0 libgssapi_krb5.so.2.2 libldap_r-2.4.so.2.10.8 liblber-2.4.so.2.10.8 libz.so.1.2.11 libunistring.so.2.1.0 libgnutls.so.30.14.10 libhogweed.so.4.4 libnettle.so.6.4 libgmp.so.10.3.2 libkrb5.so.3.3 libk5crypto.so.3.1 libcom_err.so.2.1 libkrb5support.so.0.1 libresolv-2.27.so libsasl2.so.2.0.25 libgssapi.so.3.0.0 libp11-kit.so.0.3.0 libtasn1.so.6.5.5 libkeyutils.so.1.5 libheimntlm.so.0.1.0 libkrb5.so.26.0.0 libasn1.so.8.0.0 libhcrypto.so.4.1.0 libroken.so.18.1.0 libffi.so.6.0.4 libwind.so.0.0.0 libheimbase.so.1.0.0 libhx509.so.5.0.0 libsqlite3.so.0.8.6 libcrypt-2.27.so root@bds-test:~# |
| Comment by Jelle Terpstra [ 10/Jan/21 ] |
|
Here's my ldd output. I already diffed it with yours (Tom) and found no differences. I'm gonna test some more with the village that is causing the crash, it is only one of the villages in my world. jelle@hydros:~/minecraftbe/Hydros$ for i in $(ldd bedrock_server | cut -f 3 -d ' '); do readlink $i; done libcurl.so.4.5.0 libpthread-2.27.so libdl-2.27.so libstdc++.so.6.0.25 libm-2.27.so libc-2.27.so libnghttp2.so.14.15.2 libidn2.so.0.3.3 libpsl.so.5.2.0 libgssapi_krb5.so.2.2 libldap_r-2.4.so.2.10.8 liblber-2.4.so.2.10.8 libz.so.1.2.11 libunistring.so.2.1.0 libgnutls.so.30.14.10 libhogweed.so.4.4 libnettle.so.6.4 libgmp.so.10.3.2 libkrb5.so.3.3 libk5crypto.so.3.1 libcom_err.so.2.1 libkrb5support.so.0.1 libresolv-2.27.so libsasl2.so.2.0.25 libgssapi.so.3.0.0 libp11-kit.so.0.3.0 libtasn1.so.6.5.5 libkeyutils.so.1.5 libheimntlm.so.0.1.0 libkrb5.so.26.0.0 libasn1.so.8.0.0 libhcrypto.so.4.1.0 libroken.so.18.1.0 libffi.so.6.0.4 libwind.so.0.0.0 libheimbase.so.1.0.0 libhx509.so.5.0.0 libsqlite3.so.0.8.6 libcrypt-2.27.so |
| Comment by Jeff [ 10/Jan/21 ] |
|
Ubuntu 20.04 linux-vdso.so.1 (0x00007ffd4bddf000) |
| Comment by Tom Gray [ 10/Jan/21 ] |
|
@Jelle Terpstra - thanks for checking. Can you compare the output of ldd for the bedrock_server binary from my working 18.04 install with your setup? This is the raw output: linux-vdso.so.1 (0x00007ffc44b3d000) libcurl.so.4 => /usr/lib/x86_64-linux-gnu/libcurl.so.4 (0x00007f4aa2cb0000) libCrypto.so => /app/libCrypto.so (0x00007f4aa2a79000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4aa285a000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4aa2656000) libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007f4aa23c9000) libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f4aa1efe000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f4aa1b75000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4aa17d7000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f4aa15bf000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4aa11ce000) /lib64/ld-linux-x86-64.so.2 (0x00007f4ab92aa000) libnghttp2.so.14 => /usr/lib/x86_64-linux-gnu/libnghttp2.so.14 (0x00007f4aa0fa9000) libidn2.so.0 => /usr/lib/x86_64-linux-gnu/libidn2.so.0 (0x00007f4aa0d8c000) librtmp.so.1 => /usr/lib/x86_64-linux-gnu/librtmp.so.1 (0x00007f4aa0b70000) libpsl.so.5 => /usr/lib/x86_64-linux-gnu/libpsl.so.5 (0x00007f4aa0962000) libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f4aa0717000) libldap_r-2.4.so.2 => /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007f4aa04c5000) liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x00007f4aa02b7000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f4aa009a000) libunistring.so.2 => /usr/lib/x86_64-linux-gnu/libunistring.so.2 (0x00007f4a9fd1c000) libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007f4a9f9b6000) libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x00007f4a9f782000) libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x00007f4a9f54c000) libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x00007f4a9f2cb000) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007f4a9eff5000) libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007f4a9edc3000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007f4a9ebbf000) libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f4a9e9b4000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f4a9e799000) libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007f4a9e57e000) libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 (0x00007f4a9e33d000) libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007f4a9e00e000) libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f4a9ddfb000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007f4a9dbf7000) libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 (0x00007f4a9d9ee000) libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 (0x00007f4a9d761000) libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 (0x00007f4a9d4bf000) libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 (0x00007f4a9d289000) libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18 (0x00007f4a9d073000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f4a9ce6b000) libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0 (0x00007f4a9cc42000) libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1 (0x00007f4a9ca33000) libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5 (0x00007f4a9c7e9000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f4a9c4e0000) libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f4a9c2a8000) This is the output with symlinks resolved: for i in $(ldd bedrock_server | cut -f 3 -d ' '); do readlink $i; done libcurl.so.4.5.0 libpthread-2.27.so libdl-2.27.so libstdc++.so.6.0.25 libm-2.27.so libc-2.27.so libnghttp2.so.14.15.2 libidn2.so.0.3.3 libpsl.so.5.2.0 libgssapi_krb5.so.2.2 libldap_r-2.4.so.2.10.8 liblber-2.4.so.2.10.8 libz.so.1.2.11 libunistring.so.2.1.0 libgnutls.so.30.14.10 libhogweed.so.4.4 libnettle.so.6.4 libgmp.so.10.3.2 libkrb5.so.3.3 libk5crypto.so.3.1 libcom_err.so.2.1 libkrb5support.so.0.1 libresolv-2.27.so libsasl2.so.2.0.25 libgssapi.so.3.0.0 libp11-kit.so.0.3.0 libtasn1.so.6.5.5 libkeyutils.so.1.5 libheimntlm.so.0.1.0 libkrb5.so.26.0.0 libasn1.so.8.0.0 libhcrypto.so.4.1.0 libroken.so.18.1.0 libffi.so.6.0.4 libwind.so.0.0.0 libheimbase.so.1.0.0 libhx509.so.5.0.0 libsqlite3.so.0.8.6 libcrypt-2.27.so I've also attached a screenshot comparing diffs of .so versions between working 18.04 install (on left) and broken 20.04 install (on right). (you may need to right click the image and view in a new tab to see all of it).
|
| Comment by Jelle Terpstra [ 09/Jan/21 ] |
|
My ubuntu 18.04 has /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25 So both libs on our 18.04 systems are identical, yet the crash still occurs on my server while your 18.04 seems to work. I'm not running it in a docker container.
|
| Comment by Tom Gray [ 09/Jan/21 ] |
|
I should add - I'm testing using a Docker container and the standard Ubuntu provided images (ubuntu:18.04 and ubuntu:20.04). |
| Comment by Tom Gray [ 09/Jan/21 ] |
|
I've done some more testing using the world files from With this world I can reliably reproduce the crash under Ubuntu 20.04 following the instructions in that issue (teleport, walk around). That world has lots of villagers present in beds. Under Ubuntu 18.04, I cannot reproduce the crash using that world.
I don't believe libc is the issue here - rather, potentially a behavioural change in libstdc+. The stack trace for this crash has std:: in the top few frames, which is provided by libstdc++ (aka GNU Standard C++ Library v3). libstdc++ versions used in my tests: Ubuntu 18.04: libstdc++.so.6.0.25 Ubuntu 20.04: libstdc++.so.6.0.28
Can you confirm what libstdc++ version you have present? |
| Comment by Jelle Terpstra [ 08/Jan/21 ] |
|
I moved my world to a system with Ubuntu 18.04.5 LTS with libc-2.27, installed bedrock server there, but it still crashes
root@hydros:~# lsb_release -d Description: Ubuntu 18.04.5 LTS root@hydros:~# ldd --version ldd (Ubuntu GLIBC 2.27-3ubuntu1.4) 2.27
|
| Comment by Tom Gray [ 08/Jan/21 ] |
|
I've got a world that reliably crashes using bedrock-server 1.16.201.02 on Linux (Docker hosted). I've just tried with Ubuntu 18.04 (after an apt update/upgrade) and I've not been able to reproduce a crash.
In summary: Ubuntu 21.04 (libc: 2.32): crashes Ubuntu 20.04 (libc: 2.31): crashes Ubuntu 18.04 (libc: 2.27): working so far Please can someone else try using Ubuntu 18.04, confirm libc version and see if they can reproduce the crash. confirm libc version with something like:
nobody@14caa8275b4b:/app$ ls -al /lib/x86_64-linux-gnu/libc.so.6 lrwxrwxrwx 1 root root 12 Jun 4 2020 /lib/x86_64-linux-gnu/libc.so.6 -> libc-2.27.so
|
| Comment by Jaroslaw Kowalski [ 06/Jan/21 ] |
|
Sean, I think the suggestion about libc version was that you need to downgrade it, as issue started after updating the server. Trying on not up-to-date Ubuntu 18 or similar could be a good test.
|
| Comment by Sean Kennedy [ 05/Jan/21 ] |
|
Fresh install of ubuntu 20.04 still causes the issue. A temp workaround is to copy the world to a client or use the windows bedrock server which as Ali mentioned is not ideal for a number of reasons. Using the newer libc libraries did not help.
Version: 1.16.201.2 OS: Linux Server start: 2021-01-05 19:41:24 UTC Dmp timestamp: 2021-01-05 19:41:57 UTC Upload Date: 2021-01-05 19:41:57 UTC Session ID: c5d74dff-2715-47fa-8554-563909cbb467 Commit hash: Build id: development CrashReporter Key: 3fda6e15-a682-3497-ba49-8f114dcd62af Crash [INFO] at std::__shared_count<[__gnu_cxx::_Lock_policy]2>::__shared_count[std::__weak_count<[__gnu_cxx::_Lock_policy]2> const&, std::nothrow_t] (UnknownFile:?) at std::__shared_ptr<POIInstance, [__gnu_cxx::_Lock_policy]2>::__shared_ptr[std::__weak_ptr<POIInstance, [__gnu_cxx::_Lock_policy]2> const&, std::nothrow_t] (UnknownFile:?) at std::shared_ptr<POIInstance>::shared_ptr[std::weak_ptr<POIInstance> const&, std::nothrow_t] (UnknownFile:?) at std::weak_ptr<POIInstance>::lock[] const (UnknownFile:?) at Village::getBedPOICount[] const (UnknownFile:?) at Village::tick[Tick, BlockSource&] (UnknownFile:?) at VillageManager::tickVillages[Tick const&, Vec3 const&, BlockSource&] (UnknownFile:?) at ServerPlayer::tickWorld[Tick const&] (UnknownFile:?) at std::function<bool [Player&]>::operator[][Player&] const (UnknownFile:?) at Level::forEachPlayer[std::function<bool [Player&]>] (UnknownFile:?) at Level::tick[] (UnknownFile:?) at ServerLevel::tick[] (UnknownFile:?) at GameSession::tick[] (UnknownFile:?) at Minecraft::tickSimtime[int, int] (UnknownFile:?) at Minecraft::update[] (UnknownFile:?) at ServerInstance::_update[] (UnknownFile:?) at clone (UnknownFile:?) ebc1894e-3d35-40ed-9835-c67ca947ad1f
Details on the environment:
root@minecraft2:~/bds# uname -a Linux minecraft2 5.4.73-1-pve #1 SMP PVE 5.4.73-1 (Mon, 16 Nov 2020 10:52:16 +0100) x86_64 x86_64 x86_64 GNU/Linux root@minecraft2:/etc# more os-release NAME="Ubuntu" VERSION="20.04.1 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.1 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal root@minecraft2:~/bds# apt list --installed | grep libc WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libc-bin/focal-updates,now 2.31-0ubuntu9.1 amd64 [installed] libc6/focal-updates,now 2.31-0ubuntu9.1 amd64 [installed] libcap-ng0/focal,now 0.7.9-2.1build1 amd64 [installed] libcap2-bin/focal,now 1:2.32-1 amd64 [installed] libcap2/focal,now 1:2.32-1 amd64 [installed] libcbor0.6/focal,now 0.6.0-0ubuntu1 amd64 [installed] libcom-err2/focal,now 1.45.5-2ubuntu1 amd64 [installed] libcrypt1/focal,now 1:4.4.10-10ubuntu4 amd64 [installed] libcryptsetup12/focal-updates,now 2:2.2.2-3ubuntu2.3 amd64 [installed] libcurl4/focal-updates,focal-security,now 7.68.0-1ubuntu2.4 amd64 [installed] root@minecraft2:~/bds#
|
| Comment by Ali Ershad-Manesh [ 05/Jan/21 ] |
|
Thank you for testing this. This confirms that this is an issue with the application itself that the developers should be fixing. At least we are not wasting more time with this. I have yet to hear anything back from the support requests as well after many days. |
| Comment by Sean Kennedy [ 05/Jan/21 ] |
|
Ran the same world on the same windows version of the bedrock server and it does not exhibit the UnknownFile crash behavior. Looks like this is specific to the linux server release 1.16.201.2. (at least in my case) I'm checking on my libc version now to see if I can fix the problem with updating libc to the latest. |
| Comment by Sean Kennedy [ 04/Jan/21 ] |
|
I'm having the same issue (client disconnects with UnknownFile java crash on the server side) using docker and the current itzg/minecraft-bedrock-server image (1.16.201.2). Tried running on a fresh download on a regular ubuntu server and with the world copied over had the same issue. Interestingly if I copy the affected world to a windows 10 system and run as a client world it does not have problems! My next step is to try running a windows BDS server with the same world and see if it exhibits the problem. I'll keep isolating. |
| Comment by Jaroslaw Kowalski [ 31/Dec/20 ] |
|
Just to help out dev here, there are number of tickets reporting same issue. Related tickets:
Similar issue resolved in the past: BDS-7551
Come on devs, fix it, we did the leg work for you |
| Comment by Ruli Manurung [ 31/Dec/20 ] |
|
I have the same issue, using dedicated Bedrock server on Linux, all players report getting disconnected after several minutes of playing, and the server console shows the same error. Seems to occur when invoking the Village:getBedPOICount function. This started earlier this week when the server was on version 1.16.200 – today I tried updating the server to 1.16.201.2 and the issue still persists. Edit: FWIW, I am on Arch Linux (5.9.14-arch1-1), so it doesn't look like it is specific to Ubuntu/Debian systems. [INFO] Package: com.mojang.minecraft.dedicatedserver Crash |
| Comment by Frederic [ 31/Dec/20 ] |
|
For what it's worth, I also have a similar issue and I opened a new ticket with a copy of the world where it happens and exact repro step (
I managed to repro the issue 10 times in a row in the above ticket using a brand new user (one that had never logged in to that server before), so it's not related to the specific user. |
| Comment by Marcus Hearne [ 29/Dec/20 ] |
|
Getting the exact same error on an Ubuntu 20 server here. |
| Comment by Gregg Choma [ 27/Dec/20 ] |
|
I did the same and moved it to a windows 10 machine and it is working with out problems as well. Before I moved it to windows 10 I moved it to CentOS 8 and it still crashed with the same errors. |
| Comment by Jaroslaw Kowalski [ 25/Dec/20 ] |
|
I'm getting the same error on Ubuntu 20 server. I moved the world to Windows 10 server and it's working without problems (just a workaround if anyone interested). I don't want to use win 10 just for that. Please fix it. |
| Comment by Gregg Choma [ 24/Dec/20 ] |
|
I am getting the same error and narrowed it down to just being my user that causes it to crash. It didn't matter if it was being accessed from a win10 client, Android device or an iOS device. I took the world and loaded it as a local world to my win10 client where it won't crash but going to where the coordinates are that crash it on the server and I find a lot of quartz blocks missing. It is making me think the chunk in that area is corrupt. |
| Comment by Ali Ershad-Manesh [ 23/Dec/20 ] |
|
Lucky you guys that got it working. I have tried completely removing this off of my server and installing it again, and regardless of navigating away in Windows 10 or not it crashes with this output somewhere between few seconds to a couple of minuets from the time user logs in. I have also tried filling the form to get in touch with support but it has been several days and I have not heard anything back. I suspect they have no customer support at all. |
| Comment by Daniel Mayer [ 23/Dec/20 ] |
|
I still do have the problem (also Ubuntu 18.04.5 LTS (GNU/Linux 4.15.0 x86_64)). |
| Comment by Radoslaw P. [ 22/Dec/20 ] |
|
I moved the Minecraft installation to the Ubuntu 18.04.5 LTS and for now seems to be fine.
|
| Comment by Ali Ershad-Manesh [ 21/Dec/20 ] |
|
[2020-12-21 17:37:19 INFO] Starting Server Crash |
| Comment by Daniel Mayer [ 21/Dec/20 ] |
|
I have the exact same problem, server starts and crashes after some time ( seemingly random, from seconds to minutes). Fresh install didn't fix the issue. Version: 1.16.201.2 Crash |