Jump to content

[SOLVED] Forge Server Fails to Start, Post-Initilization at Incorrect State


Recommended Posts

Posted

EDIT: After a bit of research on the Minecraft forums, I managed to find a solution (for Linux). I will explain it briefly to help anyone in the future with this problem. With the Forge Installer, install in the directory you wish e.x. /home/username/Documents/Forge or anything like that. Then in your terminal, type cd Documents/Forge or whatever you directory was. Then type pwd & if it says the directory you specified, type java -jar forgeserverfile (just type forge and then press TAB). This should start up the server, & create all the files in the specified directory. Best of luck to anyone who encounters this problem! Glad this was resolved! Cheers

 

 

So, I was trying to run a Forge Server, & I'm only planning to use Flans Mod and a few content packs for it.

However, I didn't even make it nearly that far.

I installed the latest Forge installer (I'm using Linux, so I made sure not to use the Windows installer). I ran it in OpenJDK 6, and installed it in a custom directory - everything's going good. I check out the folder where it installed, only 3 things were in it. Libraries, the Forge Server, & Minecraft Server jars. I ran the Forge one, and no files were created. This being said, no logs were there. Since I ran the executable in the command line, I managed to get all the information.

Any help is greatly appreciated, thanks in advance!!! (also, I know it mentions about accepting the EULA. I'd be happy to but the eula.txt file was never generated).

 

[15:22:48] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.FMLServerTweaker

[15:22:48] [main/INFO] [LaunchWrapper]: Using primary tweak class name cpw.mods.fml.common.launcher.FMLServerTweaker

[15:22:48] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLServerTweaker

[15:22:48] [main/INFO] [FML]: Forge Mod Loader version 7.10.85.1283 for Minecraft 1.7.10 loading

[15:22:48] [main/INFO] [FML]: Java is OpenJDK 64-Bit Server VM, version 1.6.0_34, running on Linux:amd64:3.13.0-45-generic, installed at /usr/lib/jvm/java-6-openjdk-amd64/jre

[15:22:48] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker

[15:22:48] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.FMLDeobfTweaker

[15:22:48] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker

[15:22:48] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker

[15:22:48] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.relauncher.CoreModManager$FMLPluginWrapper

[15:22:51] [main/INFO] [FML]: Found valid fingerprint for Minecraft Forge. Certificate fingerprint e3c3d50c7c986df74c645c0ac54639741c90a557

[15:22:51] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.relauncher.CoreModManager$FMLPluginWrapper

[15:22:51] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLDeobfTweaker

[15:22:54] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.TerminalTweaker

[15:22:54] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.TerminalTweaker

[15:22:56] [main/INFO] [LaunchWrapper]: Launching wrapped minecraft {net.minecraft.server.MinecraftServer}

 

(java:3200): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

 

(java:3200): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

 

(java:3200): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

 

(java:3200): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

 

(java:3200): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

Gtk-Message: Failed to load module "canberra-gtk-module"

[15:23:03] [main/WARN] [FML]: =============================================================

[15:23:03] [main/WARN] [FML]: MOD HAS DIRECT REFERENCE System.exit() THIS IS NOT ALLOWED REROUTING TO FML!

[15:23:03] [main/WARN] [FML]: Offendor: net/minecraft/server/gui/MinecraftServerGui$1.windowClosing(Ljava/awt/event/WindowEvent;)V

[15:23:03] [main/WARN] [FML]: Use FMLCommonHandler.exitJava instead

[15:23:03] [main/WARN] [FML]: =============================================================

[15:23:03] [server thread/INFO]: Starting minecraft server version 1.7.10

[15:23:03] [server thread/INFO] [MinecraftForge]: Attempting early MinecraftForge initialization

[15:23:03] [server thread/INFO] [FML]: MinecraftForge v10.13.2.1283 Initialized

[15:23:03] [server thread/INFO] [FML]: Replaced 183 ore recipies

[15:23:04] [server thread/INFO] [MinecraftForge]: Completed early MinecraftForge initialization

[15:23:04] [server thread/INFO] [FML]: Searching /home/alan/mods for mods

[15:23:05] [server thread/INFO] [FML]: Forge Mod Loader has identified 3 mods to load

[15:23:06] [server thread/INFO] [FML]: Attempting connection with missing mods [mcp, FML, Forge] at CLIENT

[15:23:06] [server thread/INFO] [FML]: Attempting connection with missing mods [mcp, FML, Forge] at SERVER

[15:23:07] [server thread/INFO] [FML]: Processing ObjectHolder annotations

[15:23:07] [server thread/INFO] [FML]: Found 341 ObjectHolder annotations

[15:23:07] [server thread/INFO] [FML]: Configured a dormant chunk cache size of 0

[15:23:07] [server thread/INFO] [FML]: Applying holder lookups

[15:23:07] [server thread/INFO] [FML]: Holder lookups applied

[15:23:07] [server thread/INFO]: Loading properties

[15:23:07] [server thread/INFO]: You need to agree to the EULA in order to run the server. Go to eula.txt for more info.

[15:23:07] [server thread/WARN] [FML]: Can't revert to frozen GameData state without freezing first.

[15:23:07] [server thread/INFO] [FML]: Applying holder lookups

[15:23:07] [server thread/INFO] [FML]: Holder lookups applied

[15:23:07] [server thread/INFO] [FML]: The state engine was in incorrect state POSTINITIALIZATION and forced into state SERVER_STOPPED. Errors may have been discarded.

 

Posted

From the log:

[15:23:07] [server thread/INFO]: You need to agree to the EULA in order to run the server. Go to eula.txt for more info.

Don't PM me with questions. They will be ignored! Make a thread on the appropriate board for support.

 

1.12 -> 1.13 primer by williewillus.

 

1.7.10 and older versions of Minecraft are no longer supported due to it's age! Update to the latest version for support.

 

http://www.howoldisminecraft1710.today/

Posted

I stated that after running the Forge Server that the files usually downloaded - weren't. The eula.txt file isn't there. I only have the Minecraft Server file, Minecraft Forge Server file, & the libraries folder.

Posted

Nothing is 'downloaded'

However, the issue is simple whatever way you are running the server is NOT running it in the folder you think it is.

It's 'working directory' is somewhere else, thus the EULA is put somewhere else.

How are you running the server?

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Posted

Thanks for the reply. I'm not exactly sure what you mean by how I'm running the server... sorry.

I'm running the server off an Ubuntu-based distro.

I'm running the server on OpenJDK 6 (had problems getting 7)

I checked a plethora of places, couldn't find any of the server files. Also, using the Forge Install Tool I set the directory to the one I wanted. A few time I deleted the directory, & attempted using the default directory (.minecraft) which unfortunately didn't work. Thanks for the reply, means a lot. I hope this gets resolved!  :)

Posted

You run a command

Click a button

Double click a icon

SOMETHING to start the server.

Whatever it is is running it SOMEWHERE.

 

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Posted

Thanks again for the reply. I'm not sure if this would particularly help but...

I tried to run the Forge Server (same version) on my gaming computer with Windows 8.1 & it worked perfectly fine. I chose the directory, and all the files required went in the place I chose. I'm starting to wonder if its just a problem with my system or not. The Minecraft Server, the Forge Server, & the Libraries file no matter what I do are the only files that go in the directory I choose.

I double-click the Forge Server .jar file (yup, its executable), it opens up the GUI for a few seconds (many times not opening the GUI at all just never appearing). The file I run is in the directory I choose, what kind of place could it be running besides where the file I ran is? I'm sorry - I know I sound really stupid right now, I'm just honestly confused with no ideas. -braindead-

 

Guest
This topic is now closed to further replies.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Back then there was a number which determined the tier of an item and block. If the block tier is lower or equal to the item number, the block would be mined. this however, has changed and now it goes by "needs_netherite_tool" which is fine, until you realized that some mods had items and blocks that exceeded these values. You can make you own "needs_mod_tool" but I feel that this is more limiting(and just more work) than before. So is there anyway to use something similar to the old tier system while also still being compatible with a lot of other mod tools?
    • Well, when I log in to the server, sometimes within an hour, sometimes within a minute, the server closes and informs me that there was a Ticking entity error. Below is the crash report
    • This forum is for Forge, not NeoForge. Please go to them for support.
    • Forge version: 55.0.0 Minecraft version: 1.21.5 Downloads: As this is the start of a new version, it is recommended that you check the downloads page and use the latest version to receive any bug fixes. Downloads page Intro: Good evening! Today, we have released our initial build of Forge 55.0 for Minecraft 1.21.5. 1.21.5 is the newest member of the 1.21 family of versions, which was released yesterday on March 25, 2025. As a reminder, the first minor (X.0) of a Forge version is a beta. Forge betas are marked as such on the bottom left of the title screen and are candidates for any breaking changes. Additionally, there are a couple of important things to note about this update, which I've made sure to mention in this post as well. Feel free to chat with us about bugs or these implementation changes on GitHub and in our Discord server. As always, we will continue to keep all versions of 1.21 and 1.20 in active support as covered by our tiered support policy. Cheers, happy modding, and good luck porting! Rendering Refactor For those who tuned in to Minecraft Live on March 22, 2025, you may already know that Mojang have announced their intention to bring their new Vibrant Visuals overhaul to Java in the future. They've taken the first steps toward this by refactoring how rendering pipelines and render types are handled internally. This has, in turn, made many of Forge's rendering APIs that have existed for years obsolete, as they (for the most part) can be done directly in vanilla. If there was a rendering API that was provided by Forge which you believe should be re-implemented, we're happy to discuss on GitHub through an issue or a pull request. Deprecation of weapon-like ToolActions In 1.21.5, Minecraft added new data components for defining the characteristics of weapons in data. This includes attack speed, block tags which define efficient blocks, and more. As such, we will begin marking our ToolActions solution for this as deprecated. ToolActions were originally added to address the problem of creating modded tools that needed to perform the same actions as vanilla tools. There are still a few tool actions that will continue to be used, such as the shears tool action for example. There are some existing Forge tool actions that are currently obsolete and have no effect given the way the new data components are implemented. We will continue to work on these deprecations and invite you to chat with us on GitHub or Discord if you have any questions.
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.