Startup Issue with Minecraft - Minecraft stuck in Application State: Preparing to start

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Decadeus’ v2.4.8.0 (Mainline)
Virtualization Docker
Application Minecraft
Module MinecraftModule
Running in Container Yes
Current State PreStart

Problem Description


Booting AMP server from cold start or restart causes Minecraft instance to start as expected. Docker shows as running via CLI (docker ps). Application stuck in “Preparing to start” state. I have to stop and start the instance to get the application to start.

Reproduction Steps

  • Shutdown AMP server VM
  • Boot AMP server VM
  • Wait for Minecraft instance and application to autostart

Right click the instance, hit “view logs”, then share that here.
Probably just some data fetching that’s being slow, you could try and stop/start the instance to see if it kicks over

I’m not sure how to attach a text file, but the contents were short, so I’m pasting them below. The manual instance stop and start does clear up the issue until the next system shutdown or reboot.

[00:04:21] [Core Info] : Starting AMP version (Decadeus), built 29/01/2024 18:40
[00:04:21] [Core Info] : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[00:04:21] [Logger Info] : Purging old audit logs (this may take a moment)…
[00:04:21] [Core Info] : Running in a Docker environment.
[00:04:21] [Core Info] : OS: Linux / x86_64
[00:04:21] [Core Info] : CPU: Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz (12C/12T)
[00:04:21] [Core Info] : RAM: 48165MB
[00:04:21] [Core Info] : AMP Instance ID: 6968ecce-9c15-413b-bf5e-3a74c6f21801
[00:04:21] [Loader Info] : Loaded MinecraftModule version by CubeCoders Limited
[00:04:21] [Core Info] : Metrics publishing is enabled at udp://localhost:12820.
[00:04:21] [Loader Info] : Loaded FileManagerPlugin by CubeCoders Limited
[00:04:21] [Loader Info] : Loaded EmailSenderPlugin by CubeCoders Limited
[00:04:21] [Loader Info] : Loaded WebRequestPlugin by CubeCoders Limited
[00:04:21] [Loader Info] : Loaded LocalFileBackupPlugin by CubeCoders Limited
[00:04:21] [Loader Info] : Loaded CommonCorePlugin by CubeCoders Limited
[00:04:21] [Core Info] : Licence Present: AMP Advanced Edition
[00:04:23] [FileManager Notice] : Using keypair with fingerprint SjqHyTfitQYq8ENTeEGAOkn/XT1W08lrposB9GlNqj4=
[00:04:23] [FileManager Info] : SFTP Server started on
[00:04:23] [Webserver Info] : Websockets are enabled.
[00:04:23] [Webserver Info] : Webserver started on
[00:04:23] [Logger Info] : RouterTimer@10Hz with 2 jobs started
[00:04:23] [Core Info] : Checking for AMP updates…
[00:04:23] [Core Info] : Startup mode is StartApplication.
[00:04:23] [Minecraft Info] : Java located at /usr/lib/jvm/temurin-18-jdk-amd64/bin/java
[00:04:23] [Minecraft Error] : Process configuration failed. AMP wasn’t able to query the Forge version list. Please try again later.
[00:04:23] [Minecraft Info] : Modpack cache is up-to-date.
[00:04:23] [Minecraft Warning] : Unable to get Bedrock version data from Match not found.
[00:04:23] [Minecraft Info] : Trying first Bedrock info fallback…
[00:04:23] [Core Info] : AMP is up to date.
[00:04:28] [Minecraft Info] : Latest Bedrock version:
[00:06:14] [Core Activity] : Authentication attempt for user mark from
[00:06:14] [Core Activity] : Authentication success

Yeah, that all looks fine, not entirely sure why it would be stalling out during the preStart phase

Hi, I wanted to give an update:
I recently upgraded to AMP 2.5, and I’m still experiencing this issue. I got curious and poked around more for potential workarounds, but I don’t see a way within the Schedule function to automate restarting an instance if the state is “Preparing to start.” I’m unsure if AMP will even accept a Start or Restart Minecraft server command when that function isn’t available in the GUI when the state is stuck. Is there a way to fix or workaround the startup issue short of using cron to run ampinstmgr?

I personally haven’t been able to replicate this at all, and it hasn’t shown up much since it was happening to you and a couple other users.
In terms of a workaround, you could use the AMP API to attempt to start things, but honestly cron would be the easier choice in this scenario.
I do wonder however, if this happens to new instances on your machine, or if it’s just select instances created when PreStart was being buggy or something strange like that.

I feel a little stupid for not trying out a new instance previously.

Of course, when I created the new instance and replicated the mods setup from the problem instance, I no longer got the “Preparing to start” hang. Both instances started up just fine after I rebooted the Ubuntu VM (I’ve rebooted at least a dozen times to make sure proper startup wasn’t a fluke). I am stumped, but I’m glad it’s working correctly.

Thank you so much, @ThePotatoKing, for your suggestions and patience!

These sorts of things are usually solved when instances get updated, but every so often they’ll get buggered enough that re-creating them is the only option. It’s too bad it doesn’t happen often enough to actually narrow down the cause.