HoloFear Posted February 10, 2016 Share Posted February 10, 2016 here's the console log, ik it's weird but you read it from the bottom up. 10.02 15:05:37 [Multicraft] Server stopped 10.02 15:05:37 [Multicraft] Server shut down 10.02 15:05:36 [server] INFO /run.sh: line 68: 22838 Killed /monitor.sh "$PID" "$USER" 10.02 15:05:36 [server] INFO Process 22836 detected 10.02 15:05:36 [server] INFO Process 22836 dead! 10.02 15:04:52 [server] INFO 2016-02-10 15:04:52,332 ERROR Unable to locate appender Console for logger net.minecraft 10.02 15:04:52 [server] INFO 2016-02-10 15:04:52,331 ERROR Unable to locate appender FmlConsole for logger 10.02 15:04:52 [server] INFO 2016-02-10 15:04:52,331 ERROR Unable to locate appender Console for logger com.mojang 10.02 15:04:51 [server] INFO 2016-02-10 15:04:51,386 ERROR Error processing element TerminalConsole: CLASS_NOT_FOUND 10.02 15:04:51 [server] INFO 2016-02-10 15:04:51,385 ERROR Error processing element TerminalConsole: CLASS_NOT_FOUND 10.02 15:04:38 [server] INFO 2016-02-10 15:04:38,654 ERROR Unable to locate appender Console for logger net.minecraft 10.02 15:04:38 [server] INFO 2016-02-10 15:04:38,653 ERROR Unable to locate appender FmlConsole for logger 10.02 15:04:38 [server] INFO 2016-02-10 15:04:38,653 ERROR Unable to locate appender Console for logger com.mojang 10.02 15:04:35 [server] INFO 2016-02-10 15:04:35,151 ERROR Error processing element TerminalConsole: CLASS_NOT_FOUND 10.02 15:04:35 [server] INFO 2016-02-10 15:04:35,151 ERROR Error processing element TerminalConsole: CLASS_NOT_FOUND 10.02 15:04:34 [server] main/INFO [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLServerTweaker 10.02 15:04:34 [server] main/INFO [LaunchWrapper]: Using primary tweak class name net.minecraftforge.fml.common.launcher.FMLServerTweaker 10.02 15:04:34 [server] main/INFO [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLServerTweaker 10.02 15:04:32 [server] INFO /usr/bin/java $START 10.02 15:04:31 [Multicraft] Loaded config for "Mod: Custom Server" Quote Link to comment Share on other sites More sharing options...
jeffryfisher Posted February 11, 2016 Share Posted February 11, 2016 Attempting to upgrade a Forge server between recommended builds (from1450 to 1722), I am crashing at the same location, but my rickety old CentOS 4 server, stuck at Java 1.6, fails to convert the underlying floating point exception into a catchable Java exception. Consequently, I've been analyzing a SIGFPE = SIG_INTDIV fault and have gotten this far today: Looking into the source location (TerminalConsoleAppender.start()V+38) indicated by the dumped stack trace, I see it bracketed by a test for JLINE_ENABLED. I suspect that setting jline.enabled to false could branch around the offending statement (maybe only to encounter another in super.start, which my execution hasn't reached yet). If this is a known bug that's fixed in a more recent Forge build, then perhaps the "recommended" tag should be moved. If not, then does anybody know where I could inject a "jline.enabled=false" setting to assuage my ancient server? I'm still looking for existing instructions of Forge server properties arguments / file(s), but haven't found any yet. Quote The debugger is a powerful and necessary tool in any IDE, so learn how to use it. You'll be able to tell us more and get better help here if you investigate your runtime problems in the debugger before posting. Link to comment Share on other sites More sharing options...
jeffryfisher Posted February 11, 2016 Share Posted February 11, 2016 Huzzah! Inserting -Djline.enable=false before the -jar in my Forge server command line worked. The tweakers survived, and Forge got all the way into my mods before hitting one that didn't like version 1.8.9 (and I know how to fix its annotations). If anyone else hits an exception during console start, you may want to try this system property as a workaround, especially if you have old tech like mine. Quote The debugger is a powerful and necessary tool in any IDE, so learn how to use it. You'll be able to tell us more and get better help here if you investigate your runtime problems in the debugger before posting. Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.