Startup Issue with Minecraft - Server stuck in Starting status

System Information

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

Problem Description

Issue

I moved over server files for a mod pack for minecraft. I changed the Forge version then went to start the server and it just sits at starting server status. I have attempted to stop and start it again and same thing. It has been sitting at starting status for over 10 minutes now

Reproduction Steps

  • Moved over files
  • Changed Forge Version
  • Changed JAR version to match the mod pack version
  • Stopped and restarted server
  • Just to test one further thing, I just stopped the server and selected Update and restarted. So far no change and still just sitting in starting. Has been maybe 3-5 minutes since I had attempted to start the server again. Logs on my end do not show any issues either.

Some servers just take that long to start, or the startup message might be altered by some mod, you can try and join the server to see if it’s accessible

Does not appear to be joinable. I do see the option there but says the server is not reachable. On average, how long would a server with around 400 mods take to start? I can leave it and not mess with it for awhile but i had it running for nearly 40 minutes before i finally tried troubleshooting on my own again.

Depends on how many resources you have dedicated to it, a server like that can take anywhere from 8-12GB of ram just to start (you can start it with less, it’ll just be uber slow).
Might be a decent bet to check the log to see if there’s a user-interaction step you’re missing, esp if there was a vanilla world loaded before you installed the modpack (if it’s a new server you can try and delete the world folder on the next attempt to see if that helps)

Thank you. I can try to delete the world folder. Logs only show the session starting step and nothing afterwards.

Maybe sanity check that you’ve bumped the Memory (Ram) limit under Java and Memory

@ThePotatoKing

After some further testing, I fully deleted the instance, created a new, made sure no vanilla world was created first, moved over just the server files needed for the mod pack i am using, did not transfer any world folders over, changed the RAM to correct levels, changed the JAVA and Forge versions to match the mod pack and changed the JAR to the one from the mod pack files.
It once just went from starting and would run for a few seconds then loop back into the starting status over an over for about 30 minutes before i stopped it and then the server would not start again and would provide the error “Killed by User” after about 5 minutes. I am not sure what could be missing at this point.

You’ll need to read the log to know why it’s stopped, but it could just not have enough resources to start a pack that big

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.