If server.properties is unwritable, the server goes into a loop printing this:
at le.b(SourceFile:54) [minecraft_server.1.11.2.jar:?]
at le.a(SourceFile:44) [minecraft_server.1.11.2.jar:?]then it has to be killed.
I ran into this because I own the server.properties file but run minecraft_server as another user. I understand that the file must be writable for the server to operate correctly, but if the file isn't writable, the server should give an error and exit rather than going into this loop.
Linked issues
is duplicated by 1
Attachments
Comments 13
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Is this still an issue in the current Minecraft Snapshot 15w49b or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Why? If you haven't fixed it in three years, is there any realistic expectation that you will ever fix it?
Sorry, four years.
It was resolved as awaiting response for 1+year as such it got no attention from the devs, if you keep it updates, the devs will actually see the issue and attempt to fix it.
You have a bug in your server code. You run a public bug reporting service, so I reported it. I have provided all the information you need to find and fix the bug, should you choose to do so.
You closed the bug. It wasn't fixed. Someone (not me) re-opened it. I re-verified that the bug is still there. This took me about one minute. I did your testing for you because I'm a generous guy and want to help you out.
Did you thank me? No. You suggested that I have not done enough of your work for you, and that I should do more. I would like to remind you that you do not pay me for this work. In fact, I paid you for Minecraft.
Please do not close this bug. Other users will come across this problem. They won't know there is a bug, and will want to know how to get their server to run. They may search this bug database and find the solution. I know it took me a while to figure this out, although I don't remember exactly how long since it was over four years ago. If you close the bug, they may think it's been fixed, or they may not find the report at all.
Also, closing the bug report does not actually fix the bug. The bug is still there. You have obviously decided it's not a priority to fix this. But that doesn't mean it's fixed.
I believe that this is the same error that I'm experiencing as well. I'm running the Mojang 1.11.12 server on my personal Windows PC. I only noticed it starting yesterday. It doesn't seem to affect gameplay. Players seem to be able to log in fine and the map seems to be able to run fine. What irks me is, why was this thing TRYING to generate a new properties file? My server doesn't need one. We're playing on an existing map. We're not generating a new one!
[media]
Also confirmed for latest snapshot.