vinanrra / Docker-7DaysToDie

7 days to die server using LinuxGSM in Docker with backups, monitor, auto-installable mods and more
GNU General Public License v3.0
236 stars 47 forks source link

[BUG] Undead Legacy's run_bepinex_server.sh script gets killed when map is not Navezgane #110

Closed zstephens closed 2 years ago

zstephens commented 2 years ago

Describe the bug:

Getting an error when trying to run a server with Undead Legacy + enZombies on a GameWorld other than Navezgane.

To Reproduce:

(1) A fresh instance of the game is created by running the docker command provided below.

The Undead Legacy server starts as expected with the default configuration, and I verify that I am able to join the game from another computer.

(2) Container is stopped and removed. (3) Edit sdtdserver.xml and change GameWorld to something other than Navezgane, e.g. <property name="GameWorld" value="PREGEN6k"/> (4) Start the server by again running the same docker command provided below.

After the usual lengthy initialization the run_bepinex_server.sh script gets killed with the following error:

./run_bepinex_server.sh: line 123: 1693 Killed "${executable_path}" -configfile=$config_file -noeac -nogs

Here is the full console log: https://pastebin.com/q6DezaAM

And for comparison here is the console log when running with Navezgane (which runs successfully): https://pastebin.com/1f6nwsR9

Looking at where the log ends it seems like the 7days exe is erroring out at the line "Loading and parsing of generator took Xms"

I've tried a number of different GameWorlds but Navezgane is the only one that seems to work.

Versions:

$ docker inspect -f '{{ index .Config.Labels "build_version" }}' 7dtdserver
version: 0.2.9
$ docker inspect -f '{{ index .Config.Labels "build_version" }}' vinanrra/7dtd-server
version: 0.2.9

(even though the version here says 2.9 I'm pretty sure I'm running 3.0, as the docker image tag is "latest")

Docker:

docker run -d \
--name 7dtdserver \
--restart unless-stopped \
-v "/Users/zach/Desktop/undead_legacy_docker/7DaysToDie:/home/sdtdserver/.local/share/7DaysToDie/" \
-v "/Users/zach/Desktop/undead_legacy_docker/ServerFiles:/home/sdtdserver/serverfiles/" \
-v "/Users/zach/Desktop/undead_legacy_docker/LogFolder:/home/sdtdserver/log/" \
-v "/Users/zach/Desktop/undead_legacy_docker/BackupFolder:/home/sdtdserver/lgsm/backup/" \
-v "/Users/zach/Desktop/undead_legacy_docker/LGSM-Config:/home/sdtdserver/lgsm/config-lgsm/sdtdserver/" \
-p 26900:26900/tcp \
-p 26900:26900/udp \
-p 26901:26901/udp \
-p 26902:26902/udp \
-e START_MODE=1 \
-e VERSION=stable \
-e TEST_ALERT=NO \
-e UPDATE_MODS=NO \
-e ALLOC_FIXES=NO \
-e ALLOC_FIXES_UPDATE=NO \
-e UNDEAD_LEGACY=YES \
-e UNDEAD_LEGACY_VERSION=stable \
-e UNDEAD_LEGACY_UPDATE=NO \
-e ENZOMBIES=YES \
-e ENZOMBIES_ADDON_SNUFKIN=NO \
-e ENZOMBIES_ADDON_ROBELOTO=NO \
-e ENZOMBIES_ADDON_NONUDES=NO \
-e ENZOMBIES_UPDATE=NO \
-e CPM=NO \
-e CPM_UPDATE=NO \
-e BEPINEX=NO \
-e BEPINEX_UPDATE=NO \
-e BACKUP=NO \
-e MONITOR=NO \
-e PUID=1000 \
-e PGID=1000 \
-e TimeZone=America/Chicago \
-e CHANGE_CONFIG_DIR_OWNERSHIP=YES \
vinanrra/7dtd-server

vinanrra commented 2 years ago

Could you try increasing querydelay to 20 in: /lgsm/config-lgsm/sdtdserver/sdtdserver.cfg

Maybe it's because the linuxgsm script it's killing it

I'm not able to test it now

zstephens commented 2 years ago

Unfortunately with this change the error still occurs, always at the same spot:

... 2022-04-19T13:54:59 293.630 INF Started thread GenerateChunks 2022-04-19T13:55:00 295.399 INF Calculating world hashes took 1677 ms (world size 149 MiB) 2022-04-19T13:55:01 295.874 INF Loading dtm raw file took 2204ms 2022-04-19T13:55:02 296.676 INF Biomes image size w= 6144, h = 6144 2022-04-19T13:55:04 298.552 INF Loading and creating biomes took 2677ms 2022-04-19T13:55:05 300.290 INF Loading and creating shader control textures took 1737ms ./run_bepinex_server.sh: line 123: 1692 Killed "${executable_path}" -configfile=$config_file -noeac -nogs

vinanrra commented 2 years ago

How much RAM do you have?

zstephens commented 2 years ago

Wow, that was it! The computer I'm running it on has 16GB of RAM but Docker's preferences were set to use 7.9GB for some reason. I increased the amount and it was able to successfully launch (the container's memory usage peaked at just over 8GB at the step where it was crashing before).

Much appreciated!