log-limit is not a recognized option
i cant load up the older snapshots and have tried a new server and get the same issue
i loaded 1.13.2 on the same server and all was fine.
[CC] Initializing. This may take a minute or two.
[CC] Starting process.
[16:22:44] [main/FATAL]: Failed to start the minecraft server
joptsimple.UnrecognizedOptionException: log-limit is not a recognized option
at joptsimple.OptionException.unrecognizedOption(OptionException.java:108) ~[server.jar:?]
at joptsimple.OptionParser.handleLongOptionToken(OptionParser.java:510) ~[server.jar:?]
at joptsimple.OptionParserState$2.handleArgument(OptionParserState.java:56) ~[server.jar:?]
at joptsimple.OptionParser.parse(OptionParser.java:396) ~[server.jar:?]
at net.minecraft.server.MinecraftServer.main(SourceFile:840) [server.jar:?]
>
Linked issues
is duplicated by 1
Attachments
Comments 6
i cant load up the older snapshots and have tried a new server and get the same issue
What older snapshots?
sorry for the late reply, that was a typo, it was meant to say:- i CAN load up the older snapshots and they work fine.
I have tried a new server and get the same issue, so i would assume it isn't the server.
I too am experiencing the same issue. I can launch up to snapshot 18w47 as a server on a Mac, but with 18w48 and forward (to latest as of now – 18w50) I get the error above.
Latest java installed, on Mac OS X 10.13.3
An attachment with a disallowed file extension has been removed from this ticket.
Executable files and documents are not allowed as attachments.
Please attach crash reports, log files and screenshots as they are instead of pasting them into a document.
-- I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
I ran some tests of my own and ran in to no issues aside from one of my worlds apparently being corrupt.
Debian 9, amd64, 5GB server RAM
openjdk version 1.8.0_181
openJDK Runtime Environment
openJDK 64-bit Server VM
Attached are files of interest.
latest.log is from an import of a 1.13.2 world (no issues).
2018-12-05-2.log is a brand spanking new world
2018-12-05-2.log is an import from 1.12.2, however I have reason to believe the world is corrupted and therefore the crash report irrelevant to this issue.
mcstart.sh is the script I use to start/stop/manage my MC server(s) (included in case there may be something of interest that I need to change to reproduce).
Fibro, could you provide more info? Do you know how to replicate this issue on a fresh world?