Server logging broken

Occurs for me also on two different systems

Windows 8.1 - Java 7 update 15 (x64)
Windows 7 SP1 - JDK 8 update 5 (x64)

Issue is also present in 14w27b

Confirmed.

Occurs for me on my Ubuntu server, java version 7u55 x64, 14w27b

Same here. Server seems running, but no logging.

CentOS Linux Server

java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)

AND

java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)

Minecraft Server 14w27b, 14w26c runs fine.

Also, can close out mine as a dupe: MC-60119

Same issue. The file latest.log does not update after starting with 14w27b snapshot jar.

Ubuntu Server 14.04 LTS
java version 1.8.0_05

I thought adding a custom log4j configuration would fix this, but no such luck.

Also occurs to me OpenSuse Linux 13.1 java version- 1.7.0_50 (or something like that)

Also same issue. Server runs fine, logs broken.
Ubuntu Desktop 14.04 LTS
java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)

Also happens on Mac OSX 10.9.2
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)

Same here.

Slackware64 14.0
Java 8u5

Same:

14w27a
Windows 8 Pro 64-bit
Java version "1.7.0_60"

Sometimes it spits out this 2

java.util.ConcurrentModificationException
at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1115)
at java.util.TreeMap$KeyIterator.next(TreeMap.java:1169)
at pb.a(SourceFile:557)
at pb.a(SourceFile:537)
at bah.a(SourceFile:258)
at bah.a(SourceFile:113)
at pa.b(SourceFile:167)
at pa.a(SourceFile:210)
at pb.a(SourceFile:739)
at net.minecraft.server.MinecraftServer.a(SourceFile:340)
at net.minecraft.server.MinecraftServer.p(SourceFile:363)
at nq.run(SourceFile:691)

@@unknown: That's probably unrelated.

Happens for me as well

14w27b
Windows 7 Home Premium (x64)
Java build 1.8.0_05-b13

Got the same problem, trying to update my server. 14w27b.

Same problem

14w27b
Ubuntu 14.04
Java version "1.7.0_60"

Exact same problem here. Even when starting clean with a fresh jar in an empty folder.

Same with me for 14w27b. Ubuntu 14.04 "Trusty Tahr", and the world runs just fine on 14w26c, so it isn't that.

The same for me:

Windows 8.1 Pro
Java Version: 1.7.0_60
Java SE Runtime Environment: Build 1.7.0_60-b19

Also have this bug under win 8, jdk 1.7.0 and minecraft_server.jar from latest snapshot.

Also note that the server does run fine, and players can log in and play on the server. It's only the console that is messed up.

Glitch with player logging in?
it say:
Player joined the game.
Player joined the game.
Player left the game.
Player joined the game.
Player left the game.
Then they are standing there.(i was already on, and he was joining from a city in Taiwan. I am in California. anything to do with that?)
Anything to do with this?

@Stanly Sisson that's another bug

Still happening on 14w28a

cannot confirm, it's fixed for us

Logging is working again in 14w28a (Ubuntu Linux)

But, another issue I previously reported still exists on Windows. The latest.log file will not update until you 'touch' the file. You do not need to open it, but rather just selecting it in File Explorer will cause the logging engine to flush the log entries to the file. This is reproducible on any Windows server but was dismissed as a bug because the behavior was different within Linux.

Mark Loh, what type of system are you on? Can you see if your issue is the log flushing issue? To reproduce: Note the size of the latest.log file before starting the game. Make sure to select a different file or folder, then do some log generating events in the game (chat, etc). Then, just select the file in File Explorer. You will see the size update. (This is actually helpful when debugging log reader scripts, but a deal-breaker for production use.)

Apologies for all the confusion, problems on my end, not the game.

John, this is a "feature" in Windows and how it updates the file size and date properties not specific to minecraft.

Snarf, you are wrong.  Trust me, I know what I'm talking about and can reproduce it. System.io.filesystemwatcher and Linux ported tools such as 'tail' report no changes until something else tries to read it.  There other bugs concerning the implementation of log caching in log4j, this is clearly another.

Broken again in 17w15a

Confirm broken on our server as well, and our service provider confirmed it was broken for him also. 17w15a

Now being tracked in MC-115797.