[MC-60039] Server logging broken

Fails to write to any log file when server is started.

On startup, outputs the following:

ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [thread]
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [level]
ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [logger]
ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [msg]
ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [n]
ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [thread]
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [level]
ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [logger]
ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [msg]
ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [n]
ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.

Linked issues

is cloned by 1

MC-115797 Server output shows errors and nothing else Resolved

is duplicated by 23

MC-59858 Loading a server is printing random errors... Resolved

MC-59883 Console not showing Resolved

MC-59907 Crash on Startup - "Unrecognized format specifier" Resolved

MC-59952 When starting a server with the .jar, it appears as if it isn't working, but still works. Resolved

MC-60066 Server java not showing logging information in Log and Chat area. Resolved

18 more links

Comments 33

Jeremy 2014-07-02T16:59:28Z

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

Anon Ymus 2014-07-02T20:29:32Z

Confirmed.

Steve Blouin 2014-07-02T20:29:35Z

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

Dirk Schlüter 2014-07-02T20:51:15Z

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.

Nick Currier 2014-07-02T21:40:25Z

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

23 more comments

John Palmer 2014-07-02T21:51:36Z

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

Fenhl (Max Dominik Weber) 2014-07-02T21:51:39Z

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

Ryan Berger 2014-07-02T21:53:01Z

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

Maxwell Huenink 2014-07-02T21:53:44Z

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)

Albert YouDon'tNeedMyLastName 2014-07-02T22:01:22Z

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)

William Sandey 2014-07-02T23:24:28Z

Same here.

Slackware64 14.0
Java 8u5

Ian 2014-07-03T00:24:53Z

Same:

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

Joona-M Heikkilä 2014-07-03T06:47:30Z

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)

Fenhl (Max Dominik Weber) 2014-07-03T06:57:18Z

@@unknown: That's probably unrelated.

haybale100 2014-07-03T07:02:01Z

Happens for me as well

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

Jacob Vejlgaard Knudsen 2014-07-03T07:05:15Z

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

Viljams Volosovskis 2014-07-03T16:46:14Z

Same problem

14w27b
Ubuntu 14.04
Java version "1.7.0_60"

EarlyReflections 2014-07-03T22:16:43Z

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

Jason C. McDonald 2014-07-04T14:55:02Z

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

Matt Rothtauscher 2014-07-04T20:35:32Z

The same for me:

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

Andrey 2014-07-05T14:14:27Z

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

William Sandey 2014-07-05T16:14:19Z

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.

StanleyMines 2014-07-06T15:15:47Z

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?

user-f2760 2014-07-06T18:20:52Z

@Stanly Sisson that's another bug

Mark Loh 2014-07-10T09:26:59Z

Still happening on 14w28a

Fenhl (Max Dominik Weber) 2014-07-10T10:48:17Z

cannot confirm, it's fixed for us

John Palmer 2014-07-10T14:08:36Z

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.)

Mark Loh 2014-07-10T14:15:38Z

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

Snarf Attack 2014-07-10T14:18:28Z

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

John Palmer 2014-07-10T15:09:48Z

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.

Mario 2017-04-12T18:34:14Z

Broken again in 17w15a

Andy (Romaq) Smith 2017-04-13T03:03:35Z

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

Anon Ymus 2017-04-16T20:26:22Z

Now being tracked in MC-115797.