MC-9385Unwritable server.properties makes server loop instead of throwing an error
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.
Environment
Ubuntu 12.04, Java SE 1.7.0_05-b05,
Linked Issues
Attachments1
Created Issue:
Unwritable server.properties makes server loop
If server.properties is unwritable, the server goes into a loop printing this:
at go.b(SourceFile:48)
at go.a(SourceFile:38)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.
Environment
Ubuntu 12.04, Java SE 1.7.0_05-b05
is duplicated by
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Unwritable server.properties makes server loop instead of throwing an error
relates to
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
If server.properties is unwritable, the server goes into a loop printing this:
atgo.b(SourceFile:48)
atgo.a(SourceFile:38)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.
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.
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.
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.
A comment with security level 'global-moderators' was removed.
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
Please consistently manage the server.properties order by writing all property keys in case-insensitive alpha-numeric order.
Problem Description
Every time Minecraft Java Edition starts it rewrites the server.properties file, with the output containing timestamp comments and settings as consumed by the server.
While it isn't ideal at all to be rewriting configuration (do those timestamp really belong in there), the main issue is that you cannot compare configuration because the order can change.
It appears that minecraft is writing properties in 'hashCode' order. Unfortunately this order changes between Java versions. This order is not sensible to the primary producer of these properties - the server administrator.
In addition, for servers that version their configuration, this means a manual comparison since diffs provided by source-control tools cannot help with showing the material differences.
History
This appears to have been raised in MC-26781 in 2013 and claimed to be resolved in 2016 (though it hasn't ever been resolved). It is linked to MC-9385 but this appears to be unrelated to the original bug or this request (other than maybe a developer might decide to tackle both at once).
Also confirmed for latest snapshot.
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.
Confirmed on 1.8.1-pre3
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.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.
This is still broken in server 1.11.2, although the line numbers have changed:
at le.b(SourceFile:54) [minecraft_server.1.11.2.jar:?]
at le.a(SourceFile:44) [minecraft_server.1.11.2.jar:?]
Then please keep the ticket updated.
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!
Cannot reproduce in 20w07a.
It just writes the following errors to the log: