Ali Ershad-Manesh
Assigned
Reported
Comments
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.
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?
There is one issue open here: BDS-10666 which seems to have more votes.
So far from what I have gathered this issue is exclusive to the worlds running in the Linux version of the dedicated server. Other users report that the same worlds work fine in Windows server and clients.
It seems like they screwed up something with the Linux version, and there is nothing we can do to fix this from our end (or at least there are no known solutions). Given that we have yet to get any response from the company on any of the support tickets and other report on this site, currently the known solutions are:
1. move to Windows server (not a viable option for me)
2. give up (there is nothing we can do if they do not want to support Linux version of the software, which is not surprising since the parent company that owns this product is known to be monopolistic).
I have nothing against MS or Mojang, it is just that I do not have the resource and time to fire up, configure, maintain, and secure a Windows server just for this one game.
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.
If the developer doesn't fix/support the Linux version I will be completely dropping this game all together. I will not trust to move this application to a Windows box and then expose it to internet (not even willing to do it from behind a VPN). My installation in Linux is somewhat hardened to ensure this thing is contained and cannot mess with anything else. In Windows, even on a dedicated box/VM I don't trust to expose this to internet at all. Windows server is too costly and is too much of a pain to admin, configure, backup, etc... this is just not worth it at all. It's too bad, they are going to lose several customers (although I don't really think they care at this point, since they already got their money for Xbox live and the Windows 10 and Xbox clients).
Right now I have only 1 user connecting to my server at a time, and the server crashes consistently within a minuet from the time any single user logs in, regardless of even if they move or not. All the users are at/near a village, but I don't even get enough time to teleport one away to test to see if the village is the cause.
I have support ticket open since the day the update was releases few weeks ago, and that they have not responded yet, and also there is this: BDS-10666
I wonder if the developers actually care at all to look into this at all or give a crap. I really do not trust a Windows server to be running this app, as my Linux is hardened and Minecraft BE server is contained in Linux in ways that it cannot be secured down in Windows. I'm not sure what the problem is here, are they not making enough money to maintain their software anymore?
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.
That server has several other roles and services, so I'm not scrapping or reinstalling the entire Linux server just for this. This program is simply not worth it. If I could get my money back for the clients at this point I would have, and totally scrapped this garbage. We have had to already find something else to do anyways.
When I reported the issue the server was working fine and I could see the clients connect and disconnect from the console. Today I tried redownloading the latest version from the website to be 100% sure that this is not due to any issues with the server. However as of today the server is actually crashing:
[2020-12-21 17:37:19 INFO] Starting Server
[2020-12-21 17:37:19 INFO] Version 1.16.201.2
[2020-12-21 17:37:19 INFO] Session ID f37976d5-9e3d-4505-9221-3fdf7f9484a0
[2020-12-21 17:37:19 INFO] Level Name: Bedrock level
[2020-12-21 17:37:19 INFO] Game mode: 0 Survival
[2020-12-21 17:37:19 INFO] Difficulty: 1 EASY
[INFO] opening worlds/Bedrock level/db
[INFO] IPv4 supported, port: 19132
[INFO] IPv6 supported, port: 19133
[INFO] IPv4 supported, port: 52520
[INFO] IPv6 supported, port: 49707
[INFO] Server started.
[INFO] Player connected: <removed> xuid: <removed>
[INFO] Running AutoCompaction...
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.201.2
OS: Linux
Server start: 2020-12-21 17:37:19 EST
Dmp timestamp: 2020-12-21 17:48:07 EST
Upload Date: 2020-12-21 17:48:07 EST
Session ID: f37976d5-9e3d-4505-9221-3fdf7f9484a0
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:?)
There has got to be a back to roll back to the older version of the client in Windows Store... I can install the older version of the server on the Linux server so it will run, but can't downgrade the client since it is the Windows Store version... Shame on Microsoft... This is a really horrible mess... But this is the long standing Microsoft culture that is inherent here...
[2020-12-21 17:37:19 INFO] Starting Server
[2020-12-21 17:37:19 INFO] Version 1.16.201.2
[2020-12-21 17:37:19 INFO] Session ID f37976d5-9e3d-4505-9221-3fdf7f9484a0
[2020-12-21 17:37:19 INFO] Level Name: Bedrock level
[2020-12-21 17:37:19 INFO] Game mode: 0 Survival
[2020-12-21 17:37:19 INFO] Difficulty: 1 EASY
[INFO] opening worlds/Bedrock level/db
[INFO] IPv4 supported, port: 19132
[INFO] IPv6 supported, port: 19133
[INFO] IPv4 supported, port: 52520
[INFO] IPv6 supported, port: 49707
[INFO] Server started.
[INFO] Player connected: <removed>, xuid: <removed>
[INFO] Running AutoCompaction...
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.201.2
OS: Linux
Server start: 2020-12-21 17:37:19 EST
Dmp timestamp: 2020-12-21 17:48:07 EST
Upload Date: 2020-12-21 17:48:07 EST
Session ID: f37976d5-9e3d-4505-9221-3fdf7f9484a0
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:?)
I have dedicated server on local network, and with the latest update (1.16.20102.0), the game connects to server, and after a few min it disconnects and cannot connect to server any longer (cannot connect to world error). Have to exit Minecraft, start again, or restart the system to connect back. This is not a server or network issue, and it was working fine before the update to this version yesterday.
Finally server updated to version 1.14.60.5. It took hours for this update to come to server after being pushed to all clients. This is even with me being proactive and actively trying to download the server to see what version I can get.
It would be nice if Mojang and Microsoft somehow avoid this kind of problem in future? maybe make the client backward compatible, release a backward compatible server first, or just try to release these at the same time? I think the server should take priority as it may affect many more users at the same time.
Hey Joe, this is a closed source program. I doubt they are willing to discuss the issues and mistakes with their code.
This was eye-opening for me. It took them over two months to fix these issues while the admins toiled away in despair. People in this forum had done far more troubleshooting than they had to, and pointed to the exact problems, yet it took a long time for them to fix the code (or even respond to my support tickets with absolutely incompetent replies). If we could see the source code we could have had it fixed probably on the same day. We could probably address many long-standing performance issues with the product as well.
Additionally, to me, this means that I will be extremely careful and skeptical of products that are distributed via "Stores". Especially when the updates cannot be rolled back and are not optional. luckily this is just a stupid game and doesn't make a difference in life of most people. I have other products that I manage that I'm extremely worried about now.