[MC-115797] Server output shows errors and nothing else

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 No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show Log4j2 internal initialization logging.
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.

Because of this, no logs will generate in the logs folder either.

Linked issues

clones 1

MC-60039 Server logging broken Resolved

is duplicated by 14

MC-115820 the minecraft server snepshot 17w15a don't working Resolved

MC-115823 Console output does not work, log attached Resolved

MC-115836 Starting server, getting format specifier error Resolved

MC-115848 17w15a Sever does not start! Resolved

MC-115854 Server won't start, throws up errors in console. Resolved

9 more links

Comments 17

Warren Liddell 2017-04-12T09:54:30Z

I can confirm this indeed occurs on at least MS systems. Linux based server starts, but server logging does not work

md_5 2017-04-12T10:30:23Z

Doesn't work on Linux here, same errors above as windows followed by server exiting.

Alberto Salazar Muñoz 2017-04-12T10:52:26Z

Maybe a bit obvious, but I can confirm that this affects macOS (10.12.5) as well.

EDIT: The server runs just fine, tho. It just doesn't output anything to console.

Warren Liddell 2017-04-12T10:59:08Z

I've run it up on Debian with MineOS, runs and can join server.

Greener 2017-04-12T11:08:52Z

the server is running in the background, just the logging engine, log4j, seems to not be able to read the config file in the jar, so it doesn't write anything to the console or latest.log

7 more comments

md_5 2017-04-12T11:09:10Z

Nevermind, reason my server wasn't running was because eula.txt wasn't set, but I didn't know that for obvious reasons.

TheMuffinPony 2017-04-12T14:20:41Z

Wow. This is basically the equiv. of the 15w34c memory allocation crash (in my opinion as a server manager). This REALLY needs to be fixed IMMEDIATELY. Can confirm for macOS .jar.

Nigel Todman 2017-04-12T14:50:30Z

Confirmed Win7 x86

eula=true is set. Issue occurs even on fresh instance with no world generated yet.

Further info:

When attempting on a fresh instance, The world does generate and the server is actually running.

When attempting on an existing upgraded world from previous snapshot. Persistent NullPointerException on every connection attempt.

In either instance, Nothing is output to console except the aforementioned errors.

Following commands also return nothing, but do execute successfully on server (client gets notified)

ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56
in conversion pattern.
op YT_Veritas0923
debug start

On the plus side. Books now craft. Advancements also work.

ShelLuser 2017-04-12T19:14:07Z

I know I'm stating the obvious but.... FreeBSD 10.3 using OpenJDK 8.121.13 gives the exact same results. Seems like a common Java logger related bug of some sort.

Ernest Craney 2017-04-12T19:34:01Z

im running windows 10 64 bit pprofessional and am running into the same problem

Ole 2017-04-12T21:25:03Z

Confirmed running standalone server with openjdk version 1.8.0_111
running snapshot17w14a (and previous) works
running snapshot17w15a fails

It seems that there are some issues with log4j 2.1 and shaded jars under Maven ?

A workaround is to open minecraft_server.jar and remove the two files under
/META-INF/org/apache/logging/log4j/core/config/plugins/

This seems to make the server log output to the console again

Phillip 2017-04-13T01:46:33Z

The problem is the jar has two files with the same name:

META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat

Using the following did the trick for me:

unzip <jar> META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat

which then asks me if I want to replace the first with the second--I say no.

Then:

zip -d <jar> META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat

and again:

zip -d <jar> META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat

And then:

jar -uvf <jar> META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat

Phillip 2017-04-13T05:45:35Z

BTW, I no longer see the StatusLogger errors after going through the above workaround.

Nigel Todman 2017-04-13T10:11:40Z

What i did on Win7 x86 is just open up the minecraft_server.jar in WinRAR and deleted the duplicate named files mentioned above.

META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat

Noticed in the previous snapshot such files did not exist in the archive.

Regular console output is now restored.

[media]

alex berrios 2017-04-14T05:00:50Z

http://www.minecraftforum.net/forums/support/server-support/2715194-keeping-entity-that-already-exists-server-version

this also help with the client side when ppl having entiy with the same uuid works for me very well and the above metion also worked for me

SnipUndercover 2017-04-17T15:52:54Z

For people who don't understand what Phillip said:
(Phillip's comment link:
https://bugs.mojang.com/browse/MC-115797?focusedCommentId=377682&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-377682)

How to fix:
1.Open the jar file using an unzipper like WinRAR/7-zip File manager/etc...
2.Navigate to: META-INF\org\apache\logging\log4j\core\config\plugins\ 3.Delete the Log4j2Plugins.dat file that is 67 bytes long
4.Run the server if you want using either the jar file itself or a batch script that:
a) is with jar file in the same directory containing code:

scriptInDirectory.bat

java -Xms<least memory to use> -Xmx<max memory to use> -jar minecraft_server.<server version>.jar nogui

b) is in a different directory containing code:

scriptOutsideDirectory.bat

cd <jar file directory in double quote marks, i.e: "C:\Users\<username>\Desktop">
java -Xms<least memory to use> -Xmx<max memory to use> -jar minecraft_server.<server version>.jar nogui

Mario 2017-04-20T02:30:45Z

It is a easy fix, so it will probably be fixed in the next snapshot (hopefully) 🙂