Closed wertercatt closed 2 years ago
I am not aware of corrected log4j configs provided by forge so the fallback mitigation is applied
Please let me know there are official config files to obtain and I'll add that into the conditionals there.
I am not aware of corrected log4j configs provided by forge so the fallback mitigation is applied
Please let me know there are official config files to obtain and I'll add that into the conditionals there.
Looking at the debug output, it was properly applying the JVM_OPTS mitigation. But now I'm wondering what the TerminalConsole error was referring to, as it vanished upon turning DEBUG on. It didn't return when I turned DEBUG off and used the container Environment variables to regenerate my server.properties files, so they were clearly the culprit. I threw my previous server.properties files on GitHub Gist if they can aid in reproducing what happened. https://gist.github.com/wertercatt/e6cdac1ab9986e8a2d6d1675974fcbb2 My new docker compose that properly outputs the server logs to the host follows:
MCSurvival:
ports:
- '25566:25565'
volumes:
- './MCSurvival/:/data'
environment:
EULA: true
TYPE: "MAGMA"
VERSION: "1.12.2"
MEMORY: ""
JVM_DD_OPTS: "disable.watchdog=true"
MOTD: "wertercatt.com's Game Room"
DIFFICULTY: easy
LEVEL: oopsie
ALLOW_FLIGHT: true
SPAWN_PROTECTION: "0"
tty: TRUE
stdin_open: TRUE
restart: unless-stopped
image: 'itzg/minecraft-server:java8-multiarch'
MCCreative:
ports:
- '25565:25565'
volumes:
- './MCCreative/:/data'
environment:
EULA: true
TYPE: "MAGMA"
VERSION: "1.12.2"
MEMORY: ""
JVM_DD_OPTS: "disable.watchdog=true"
MOTD: "wertercatt.com's Desertia [WIP!]"
DIFFICULTY: peaceful
LEVEL: Desertia
ALLOW_FLIGHT: true
SPAWN_PROTECTION: "0"
MODE: creative
FORCE_GAMEMODE: true
tty: TRUE
stdin_open: TRUE
restart: unless-stopped
image: 'itzg/minecraft-server:java8-multiarch'
Magma's corrected config can be found here: https://github.com/magmafoundation/Magma/blob/4152130d28363452828a1d3ae72c103952123e2a/src/main/resources/log4j2_magma.xml
Thanks for finding that. Since it is in their src/main/resources
it gets bundled into their built jar. I can also confirm they apply their adjusted config file via:
https://github.com/magmafoundation/Magma/search?q=log4j2_magma
As a result, an additional log4j2.xml in the filesystem is not necessary.
This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.
Describe the problem
I was previously running Magma-1.12.2 on my system raw. But I'm currently working on dockerizing my currently running services in preparation for migrating to a new server. As I didn't want to lose my existing server configuration, with all of its mods/plugins/worlds, I decided to just mount my existing folder to the /data volume. However, I believe that since my server.properties file already existed, the container assumed that the rest of the files in https://github.com/itzg/docker-minecraft-server/tree/master/files existed as well. This has the minor issue of TerminalConsole not being set properly to output my server's log to the host with
DEBUG: "False"
but presumably also has the issue of the fix for #1177 not being applied either.Container definition
Container logs