Problem Server works on shell but not on batch file (EDIT: Only console broken)

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

TurboSlayer

New Member
Jan 6, 2021
6
0
2
Yesterday I tried running the FTB Revelation 3.4.0 server with the included 'start.bat' file. It starts up fine but eventually, it would get stuck in an infinite loop of something like this (shortened):

[Server thread/INFO] [woot]: Woot: Added custom drop Dragon Egg for minecraft:ender_dragon
[Server thread/INFO] [woot]: Woot: Added custom drop Dragon's Breath for minecraft:ender_dragon
[Server thread/INFO] [woot]: Woot: Added custom drop Dragon Heart for minecraft:ender_dragon
[Server thread/INFO] [woot]: Woot: Added custom drop Draconium Dust for minecraft:ender_dragon


When I ran 'start.sh', however, it would start up just fine, and it would only display the above once in the log (EDIT: I mean console), rather than looping infinitely.

I've gotten rid of the eula stuff from the batch and shell files, so all that's left is the java command (and a cd command I added to allow it to work in cmd). The java args are identical.

Does anyone know why this might be happening?
 
Last edited:

TurboSlayer

New Member
Jan 6, 2021
6
0
2
I deleted the file paths for privacy reasons.
Here is the log for start.sh (works): https://paste.feed-the-beast.com/view/5d5faa37
And this is the log for start.bat (doesn't work, also I closed manually at the end): https://paste.feed-the-beast.com/view/64405ab1
FYI, the woot part begins at line 4260 I believe.

I've noticed that it loops in the console but doesn't loop in the log file. However, it's still quite unusable since in the console I can't see any of the commands I type. I typed the /stop command blindly at the end lol.
 

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
Did you try and connect to the server after it's started?
 

TurboSlayer

New Member
Jan 6, 2021
6
0
2
Yes, connecting to the server works. The console remains broken but the log does show that I've joined.
This is what the repeating part looks like btw (from the console): https://paste.feed-the-beast.com/view/cf67b20f
Eventually it stops repeating but I still can't see anything I type.
When I did /stop this showed up, don't think it's related though:
[10:38:38] [Server thread/INFO] [woot]: Woot: Added custom 2021-01-10 10:56:34,958 Server Shutdown Thread ERROR An exception occurred processing Appender Console java.lang.NullPointerException
at net.minecraftforge.server.terminalconsole.TerminalConsoleAppender.append(TerminalConsoleAppender.java:308)
at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129)
at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120)
at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84)
at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:448)
at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:433)
at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:417)
at org.apache.logging.log4j.core.config.LoggerConfig.logParent(LoggerConfig.java:439)
at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:434)
at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:417)
at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:403)
at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:63)
at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:146)
at org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2091)
at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:1988)
at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1960)
at org.apache.logging.log4j.spi.AbstractLogger.info(AbstractLogger.java:1297)
at net.minecraft.server.MinecraftServer.func_71260_j(MinecraftServer.java:420)
at net.minecraft.server.MinecraftServer$4.run(MinecraftServer.java:1579)
 

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
The console remains broken
Broken how?

Can't you use commands in the console?
(try /list or /help - in console it should work without / - but should work with / as well)

If you can connect and everything looks fine in-game, then you're good.
 

TurboSlayer

New Member
Jan 6, 2021
6
0
2
It may not be a big issue, but I think it's definitely worth fixing. As mentioned in the first post, I am unable to see what I am typing into the console. No matter what I type all I see are the errors. Suppose I'm trying to execute a really long command and I make a typo. I wouldn't even be able to see that. Even worse, I wouldn't even be able to see the console output so I can't determine whether I typed it correctly or not.

Also when I said that eventually it stops repeating, I forgot to mention that whenever I type anything, the errors kinda flash and look like they're looping again but they're actually not because their timestamps never change. It's hard to explain but it's sorta like as if I had scrolled up the console and scrolled back down again really fast (it's the scrolling down part that is visible).

This may be a bug. Not exactly sure how to reproduce it though. Also whenever I say error I mean the woot stuff (idk if they are errors or whatever).

That being said no one else has gotten this bug before afaik. Maybe it isn't worth fixing after all? :(