Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Minecraft Bedrock Doesn't Show "Started" on Some Instances #786

Closed
3 tasks done
IceOfWraith opened this issue Dec 2, 2022 · 18 comments
Closed
3 tasks done

Minecraft Bedrock Doesn't Show "Started" on Some Instances #786

IceOfWraith opened this issue Dec 2, 2022 · 18 comments
Labels
bug module-specific Windows

Comments

@IceOfWraith
Copy link
Collaborator

Bug Report

System Information

  • Operating System - Windows 11 Pro 64-bit
  • AMP version and build date - v2.4.0.10, built 27/10/2022 18:15
  • Which AMP release stream you're using - Mainline

I confirm:

  • that I have searched for an existing bug report for this issue.
  • that I am using the latest available version of AMP.
  • that my operating system is up-to-date.

Symptoms

  • What are you trying to do?
    Run a Minecraft Bedrock server.

  • What are you expecting to happen?
    The startup (and other regex) should account for the below.

  • What is actually happening? ('Nothing' is not an acceptable answer!)
    The logging looks different than normal. This happens consistently for the instances affected, but I don't see a pattern of why only some instances cause it.

[21:15:46] NO LOG FILE! - setting up server logging...
[21:15:46] NO LOG FILE! - [2022-12-02 13:15:46:158 INFO] Starting Server
[21:15:46] NO LOG FILE! - [2022-12-02 13:15:46:158 INFO] Version 1.19.41.01
[21:15:46] NO LOG FILE! - [2022-12-02 13:15:46:158 INFO] Session ID d97a9345-9eb6-4877-bfa7-bdcf0adb03d9
[21:15:46] NO LOG FILE! - [2022-12-02 13:15:46:159 INFO] Level Name: FlyJessDaMess's Realm - Copy
[21:15:46] NO LOG FILE! - [2022-12-02 13:15:46:164 WARN] 'whitelist.json' will be deprecated. Please migrate to 'allowlist.json'.
[21:15:46] NO LOG FILE! - [2022-12-02 13:15:46:171 INFO] Game mode: 0 Survival
[21:15:46] NO LOG FILE! - [2022-12-02 13:15:46:171 INFO] Difficulty: 2 NORMAL
[21:15:46] NO LOG FILE! - [2022-12-02 13:15:46:329 INFO] opening worlds/FlyJessDaMess's Realm - Copy/db
[21:15:47] NO LOG FILE! - [2022-12-02 13:15:47:550 INFO] IPv4 supported, port: 40025
[21:15:47] NO LOG FILE! - [2022-12-02 13:15:47:550 INFO] IPv6 supported, port: 40026
[21:15:47] NO LOG FILE! - [2022-12-02 13:15:47:914 INFO] Server started.
[21:15:48] NO LOG FILE! - [2022-12-02 13:15:48:976 INFO] ================ TELEMETRY MESSAGE ===================
[21:15:48] NO LOG FILE! - [2022-12-02 13:15:48:976 INFO] Server Telemetry is currently not enabled. 
[21:15:48] NO LOG FILE! - [2022-12-02 13:15:48:976 INFO] Enabling this telemetry helps us improve the game.
[21:15:48] NO LOG FILE! - [2022-12-02 13:15:48:976 INFO] 
[21:15:48] NO LOG FILE! - [2022-12-02 13:15:48:976 INFO] To enable this feature, add the line 'emit-server-telemetry=true'
[21:15:48] NO LOG FILE! - [2022-12-02 13:15:48:976 INFO] to the server.properties file in the handheld/src-server directory
[21:15:48] NO LOG FILE! - [2022-12-02 13:15:48:976 INFO] ======================================================
[21:15:48] NO LOG FILE! - [2022-12-02 13:15:48:149 INFO] Please note that LAN discovery will not function for this server.
[21:15:48] NO LOG FILE! - [2022-12-02 13:15:48:149 INFO] Server IP must be specified in Servers tab in game.

Reproduction

Create a Bedrock instance, update and start. Sometimes an instance will give the lines above, other times it gives the same without the first parts.
@GreenWing034
Copy link

GreenWing034 commented Mar 10, 2023 •
edited

I'm encountering the same issue and these are the things I've noticed (all with Minecraft Bedrock):

  • Instance#1 & its server are created (default ports of 19132-19133) and the server starts normally and I can connect to it. However, any instance & server that I try to start afterwards produces the same logs as posted and do not show “Running”, only “Starting”. Despite them not showing started I can still connect to each and it will show that connection in the console. Also, each additional instance and server has had their ports changed.

  • Starting any other instance’s server before Instance#1’s server (which has the default ports) begins normally. However, now when attempting to start instance#1’s server, it attempts to start and then fails, giving the error message that the server began and stopped within 5 seconds. The logs after that say the the server can’t run because the port is being used—despite all additional instance’s using different ports.

As a note, the additional instances, as far as I can tell, are the only ones show the “no log file” parts of the log.

@IceOfWraith
Copy link
Collaborator Author

I think I found a pattern that if you start a second instance it happens. Basically they use a shared log directory and the first server is currently using it. So no way to fix that except Docker. As long as AMP accounts for the log showing this it would be fine.

@GreenWing034
Copy link

I think I found a pattern that if you start a second instance it happens. Basically they use a shared log directory and the first server is currently using it. So no way to fix that except Docker. As long as AMP accounts for the log showing this it would be fine.

Ah that makes sense. Have you tried it using a Docker?

I found something that somewhat fixes the failed start issue I was having in case it's helpful. I was reading around and found the 'enable-lan-visibility' server property that was added in 1.19.50. I didn't see that setting in the server.properties file, so I added it manually and now instance#1's server no longer crashes when starting after another instance. Still shows the yellow "Starting" status, though.

@jrose323
Copy link

This is still an issue. Any progress on a fix for this without having to use Docker as a solution?

@IceOfWraith
Copy link
Collaborator Author

This fix is included in the next AMP release.

@jrose323
Copy link

jrose323 commented Dec 7, 2023 •
edited

@IceOfWraith after upgrading to the latest version that came out today, this is still an issue. In fact, now the second instance of minecraft wont start at all instead of starting but not reporting it started as it did before.

@IceOfWraith IceOfWraith reopened this Dec 7, 2023
@IceOfWraith
Copy link
Collaborator Author

Yeah, had a couple support requests about this. The development release has a fix for the most common issue, but there is another I'm looking into.

@jrose323
Copy link

jrose323 commented Dec 7, 2023

Any chance of a hot fix release as this is impacting now. Before, all the Minecraft instances would run but not show the server status. Now I can only run one at a time on the same box.

@IceOfWraith
Copy link
Collaborator Author

Ahh mixed this up with another issue. Share your log so I cam review what it's doing?

@jrose323
Copy link

jrose323 commented Dec 7, 2023

Well, weird...Now it seems to be working as intended after trying to reboot the instances again to get the logs.

@IceOfWraith
Copy link
Collaborator Author

You may have been having the other bug that's causing an old version to download.

@jrose323
Copy link

jrose323 commented Dec 7, 2023 •
edited

@IceOfWraith Well, I rebooted the server and it seems the issue is intermittent. It seems to think the port is being used by another instance when in fact it is not. If I manually stop all instances and start them one by one, it works.

[15:59:16] [2023-12-07 10:59:16:850 ERROR]: Port [19132] may be in use by another process. Free up port and re-run program or adjust server.properties file to use alternate ports for server
[15:59:16] [2023-12-07 10:59:16:852 ERROR]: Port [19133] may be in use by another process. Free up port and re-run program or adjust server.properties file to use alternate ports for server
[15:59:16] [2023-12-07 10:59:16:853 ERROR]: Exiting program
[15:59:18] [Minecraft Warning] : Server failed to start 6/5 times...

@IceOfWraith
Copy link
Collaborator Author

Share the whole log please. A snippet like that doesn't share the whole story.

@jrose323
Copy link

jrose323 commented Dec 7, 2023

AMPLOG 2023-12-07 15-56-29.log

@jrose323
Copy link

jrose323 commented Dec 7, 2023

Here is the logs from the second instance

AMPLOG 2023-12-07 15-56-29.log

@IceOfWraith
Copy link
Collaborator Author

That's the same log twice. Heh

@jrose323
Copy link

jrose323 commented Dec 7, 2023

Weird...here you go

AMPLOG 2023-12-07 15-56-29.log
AMPLOG 2023-12-07 16-20-53.log

@IceOfWraith
Copy link
Collaborator Author

The first instance seems to be having tons of errors from the Minecraft server itself. No idea what's going on there, the second looks like it's unable to update which is the other issue we're dealing with. Try these steps:

Go to terminal/SSH and run these commands to switch it sudo su -l amp (if Linux) then ampinstmgr switch instancename Development replacing instancename with the actual name of the instance in AMP. After it's done, start the instance and manage it. Inside run an update again before starting and it should work fine.

If that doesn't work go to https://www.minecraft.net/en-us/download/server/bedrock and download it manually and place that file on your server using the File Manager or SFTP in that instance. Then just start it up. Be sure to not update again or it will replace it with the old version still!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug module-specific Windows
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jrose323 @GreenWing034 @IceOfWraith