Startup Issue with Minecraft - Server stall on startup, not failing but stuck in startup

System Information

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

Problem Description

Issue

I installed a modpack directly from forge, the server is set on the correct version and it appears I have enough resources to run the modpack. It works in singleplayer but stalls on startup when I try and launch the server with the modpack.

Reproduction Steps

  • Installed Forge Modpack
  • Attempted to launch server
  • Server begins loading but stalls on startup, RAM stays constant but CPU sitting at 0%

Do you get any console output?

Crash Report UUID: 017a2a67-bc5a-40f4-b4d9-c3b5a7e688c9

FML: 43.3

Forge: net.minecraftforge:43.3.5[17:21:56] [main/ERROR] [minecraft/Main]: Failed to start the minecraft server

net.minecraftforge.fml.LoadingFailedException: Loading errors encountered: [

Oculus (oculus) has failed to load correctly

§7java.lang.RuntimeException: Attempted to load class net/minecraft/client/gui/screens/Screen for invalid dist DEDICATED_SERVER,

Legendary Tooltips (legendarytooltips) has failed to load correctly

§7java.lang.ExceptionInInitializerError: null

]

at net.minecraftforge.fml.ModLoader.waitForTransition(ModLoader.java:243) ~[fmlcore-1.19.2-43.3.5.jar%23656!/:?] {}

at net.minecraftforge.fml.ModLoader.lambda$dispatchAndHandleError$24(ModLoader.java:208) ~[fmlcore-1.19.2-43.3.5.jar%23656!/:?] {}

at java.util.Optional.ifPresent(Optional.java:178) ~[?:?] {re:mixin}

at net.minecraftforge.fml.ModLoader.dispatchAndHandleError(ModLoader.java:208) ~[fmlcore-1.19.2-43.3.5.jar%23656!/:?] {}

at net.minecraftforge.fml.ModLoader.lambda$gatherAndInitializeMods$14(ModLoader.java:185) ~[fmlcore-1.19.2-43.3.5.jar%23656!/:?] {}

at java.lang.Iterable.forEach(Iterable.java:75) ~[?:?] {re:mixin}

at net.minecraftforge.fml.ModLoader.gatherAndInitializeMods(ModLoader.java:185) ~[fmlcore-1.19.2-43.3.5.jar%23656!/:?] {}

at net.minecraftforge.server.loading.ServerModLoader.load(ServerModLoader.java:32) ~[forge-1.19.2-43.3.5-universal.jar%23660!/:?] {re:classloading}

at net.minecraft.server.Main.main(Main.java:113) ~[server-1.19.2-20220805.130853-srg.jar%23655!/:?] {re:classloading,re:mixin,pl:mixin:A}

at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) ~[?:?] {}

at java.lang.reflect.Method.invoke(Method.java:580) ~[?:?] {}

at net.minecraftforge.fml.loading.targets.CommonServerLaunchHandler.lambda$launchService$0(CommonServerLaunchHandler.java:29) ~[fmlloader-1.19.2-43.3.5.jar%2367!/:?] {}

at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:30) [modlauncher-10.0.8.jar%2354!/:?] {}

at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-10.0.8.jar%2354!/:?] {}

at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-10.0.8.jar%2354!/:?] {}

at cpw.mods.modlauncher.Launcher.run(Launcher.java:106) [modlauncher-10.0.8.jar%2354!/:?] {}

at cpw.mods.modlauncher.Launcher.main(Launcher.java:77) [modlauncher-10.0.8.jar%2354!/:?] {}

at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-10.0.8.jar%2354!/:?] {}

at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-10.0.8.jar%2354!/:?] {}

at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:141) [bootstraplauncher-1.1.2.jar:?] {}

@CubeCoders-Bot any idea based on that log output?

I need to get better at reading, Disabling those two mods solved the issue from what I can tell

From the logs you shared, it looks like you’ve got some mods causing trouble for the dedicated server. Specifically, the “Oculus” mod is trying to load client-side classes (net/minecraft/client/gui/screens/Screen), and “Legendary Tooltips” is throwing initialization errors. These mods are likely client-only mods, which simply won’t work on a dedicated server.

Here’s your first step:

Check through the modpack and remove any client-only mods (like Oculus or anything similar) from the mods directory on the server. AMP should have a file manager for the Minecraft instance; dig in there and clear out the suspicious mods.


:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback