Trying to diagnose new MC Bedrock error after update

  • 151 Views
  • Last Post 13 December 2020
  • Topic Is Solved
Scott posted this 18 November 2020

MC updated Bedrock, and of course, they want to make it difficult. I ran the update, and when i go to launch the server, AMP comes up with that the server has shutdown right away and to check MC logs. However, I searched where to find MC logs, and have been lead to believe there aren't any.

That being said, I created a new instance, which does seem to work, however, when I go to start the application, the notifications never stops showing, and the control stays to abort (no stop etc). When I check the console, it appears to be good. I can also log into the newly created instance of MC, even though the gui shows it hasn't started yet.

I'm guessing MC made some changes that affect with how AMP communicates with it, but I really have no idea. If i can provide any other information, please let me know, and hopefully you have some thoughts.

Thanks, Scott

Order By: Standard | Newest | Votes
Mike posted this 18 November 2020

They changed the logging format which confused AMP a bit, the next nightly build has a workaround for this.

  • Liked by
  • Scott
Scott posted this 19 November 2020

Hi Mike,

Thanks for the reply. Today, I set AMP to use nightly for new instances, and then went with a straight/clean minecraft bedrock install. It fails within 5 seconds (again, says that it's a minecraft issue). However, I still can't tell where Minecraft logs exist in the directory structure. I did notice that ipv4 and ipv6 are both set to port 0, but as I mentioned, this is a straight clean install. Any help would be greatly appreciated.

INFO 11:11:49 Starting Server Version 1.16.100.4 Session ID 98d577dc-22e3-41e6-af8c-a8533e69baeb Level Name: world Game mode: 0 Survival Difficulty: 2 NORMAL opening worlds/world/db 11:11:53 IPv4 supported, port: 0 IPv6 supported, port: 0 Package: com.mojang.minecraft.dedicatedserver Console 11:11:53 [19:11:53] Version: 1.16.100.4 [19:11:53] OS: Linux [19:11:53] Server start: 2020-11-19 19:11:49 UTC [19:11:53] Dmp timestamp: 2020-11-19 19:11:53 UTC [19:11:53] Upload Date: 2020-11-19 19:11:53 UTC [19:11:53] Session ID: 98d577dc-22e3-41e6-af8c-a8533e69baeb [19:11:53] Commit hash: [19:11:53] Build id: development [19:11:53] CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293 [19:11:53] Crash [19:11:53] [INFO] [19:11:53] 464b717f-bcde-4d95-9e50-efcfbed9d4d4

earwiged posted this 11 December 2020

Curious if you landed an answer for this issue, Scott? I have the same issue, but have not been able to dig out the answer. I noticed that the ports are 0 and the server.properties IP is also 0.0.0.0 albeit the port is correct.

[API:admin Activity]   : Starting the application. [05:08:27] NO LOG FILE! - setting up server logging... [05:08:27] [INFO]: Starting Server [05:08:27] [INFO]: Version 1.16.200.2 [05:08:27] [INFO]: Session ID e45ed39e-1cf7-4d5a-b399-d15338c4a67d [05:08:27] [INFO]: Level Name: world [05:08:27] [INFO]: Game mode: 0 Survival [05:08:27] [INFO]: Difficulty: 2 NORMAL [05:08:27] [INFO] opening worlds/world/db [05:08:30] [INFO] IPv4 supported, port: 0 [05:08:30] [INFO] IPv6 supported, port: 0 [05:08:30] [INFO] Package: com.mojang.minecraft.dedicatedserver [05:08:30] Version: 1.16.200.2 [05:08:30] OS: Linux [05:08:30] Server start: 2020-12-11 05:08:27 UTC [05:08:30] Dmp timestamp: 2020-12-11 05:08:30 UTC [05:08:30] Upload Date: 2020-12-11 05:08:30 UTC [05:08:30] Session ID: e45ed39e-1cf7-4d5a-b399-d15338c4a67d [05:08:30] Commit hash: [05:08:30] Build id: development [05:08:30] CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293 [05:08:30] Crash [05:08:30] [INFO] [05:08:31] 5b851aac-84bf-4cda-8f75-25099d48d954 [05:08:31] [Minecraft:admin Warning] : Server failed to start 6/5 times... [05:08:31] [Minecraft:admin Warning] : Server failed to start 5 times, not restarting.

Scott posted this 11 December 2020

MIke's working on an update. MC changed everything in their last update which he's diligently working on fixing.

  • Liked by
  • earwiged
earwiged posted this 13 December 2020

Thanks Scott, new here and didn't know the protocol on issues and if the issue was just mine. I'll listen here to see when the update is pushed out.

Close