I run a 1.7.2 Minecraft server in Amazon's cloud using Amazon linux version 3.4.68-59.97.amzn1.i686. The server time is set to MST but when the server starts up, logging timestamps appear in UTC. This makes it difficult to correlate events with the logs.
Previous versions have always captured the server time as it's set on the host. When I start a minecraft_server.1.7.2.jar server on OS X, the logging timestamps are correct and match the computer's time. So this appears to be just a problem with Linux, and perhaps only with Amazon Linux.
Comments 10
Thank you so much for the reply!
Apologies for wasting your time, but I realized the issue had a different cause when I went to recreate the problem. I had recently upgraded my JRE from jre-1.6.0-openjdk to jre-1.7.0-openjdk. When 1.7 is in use, the timestamps in the log reflect the correct timezone. I confirmed this was the case with the 1.7.2 server as well.
So it definitely was a problem caused by an out of date JRE. Thanks again for looking at the issue and please close this ticket.
Just a final note, I wanted to mention that I tested both the 1.7.2 and 14w03b versions of the minecraft server using both the jre-1.6.0-openjdk and jre-1.7.0-openjdk. Both versions of the server indicated the wrong timezone with the 1.6 JRE and both indicated the correct timezone with the 1.7 JRE. Issue resolved.
I have the same issue. Running Minecraft ver 1.9.2 on a headless Debian. Not sure which Java version it is using, but "java -version" in shell (pc one, not MC one) says:
openjdk version "1.8.0_72-internal"
OpenJDK Runtime Environment (build 1.8.0_72-internal-b15)
OpenJDK 64-Bit Server VM (build 25.72-b15, mixed mode)(Sorry for necroposting, but i assumed this would be better than to make a new issue about the same thing)
Thanks for your attention. I installed the package openjdk-7-jre-headless after removing the previous openjdk-8-jre-headless (remove instead of purge; latter also removes configuration files; i didnt want to break anything 😃 ) and the problem persisted.
EDIT: Also tried purging (removed all config) of 7 and 8 and reinstalled both of them (at different times) and both times the problem didnt disappear.
Btw is there a way to find out which Java version is my MC server using?
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time.
1.10.2 is still affected, yes. I cant edit affected versions since im not the initial Reporter. Also technically my environment is different - Debian based OS (as mentioned above).
Is this still an issue in the most recent versions (currently that is 1.12.2) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
Is this still a concern in the latest Minecraft version 14w03b? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.