segfault in steamcmd.sh during post-install config #59
Comments
|
I can confirm this issue, the same happend to my server on a linux machine. |
Thank you! I was sure the answer would be “stop trying to do Linux things in Windows.” |
|
Hello! Thank you for raising your issue here. While this issue may occur in both 'Docker for Windows' and more standard Unix hosts, that does not necessarily mean that this issue is not related to 'Docker for Windows'. This issue usually relates to the game files either not being entirely downloaded, or not being downloaded at all. I have a few questions, and some suggestions for troubleshooting:
|
|
Hi @Renegade-Master , as mentioned above, I am using a linux host (specifically Ubuntu 20.04 with docker-ce 20.10.21) and the same error occurs for me too. The server is a fresh one, without any previous persisted data. The volume is mounted from the local disk. The initial installation fails because of the some error in steamcmd, it seems. When manually running the My guess is this is an issue with steamcmd and not with the image itself. |
|
Hello Renegade-Master. Thank you for developing this, and helping us troubleshoot.
I chose WSL2, as recommended by docker installer
Yes, x64, i5-7300U. All the virtualization options in BIOS are enabled. (HP EliteBook x360 1030 G2)
Your PZ server is my first interaction with Docker, so I'm not sure how to determine the manner of file mounting of another image. If you could suggest an appropriate image, I would be happy to check.
Yes. I tried both as admin, then as regular user (removed and recreated dirs). Logs were identical between all three.
Maybe because I am using the free version, there is no "Shared Drives" when I opened the settings. I do not have a shared drive set up, so I do not think this is relevant.
I was hoping to avoid this when I found your PZ container. Thanks again for the help! |
|
Hello again Renegade-Master, I installed docker on the fresh Debian 11 VM, following the directions at https://docs.docker.com/desktop/install/debian/ and https://docs.docker.com/engine/install/debian/ I used only the default commands given in your instructions, and had a nearly identical log, except this time the segfault happened at the "### Updating Project Zomboid Server..." step: max@debian-pz:/ws/project-zomboid$ sudo docker run --detach --mount type=bind,source="$(pwd)/ZomboidDedicatedServer",target=/home/steam/ZomboidDedicatedServer --mount type=bind,source="$(pwd)/ZomboidConfig",target=/home/steam/Zomboid --publish 16261:16261/udp --publish 16262:16262/udp --name zomboid-server docker.io/renegademaster/zomboid-dedicated-server:latest ### Setting variables... ### Applying Pre Install Configuration... ### Pre Install Configuration applied. ### Updating Project Zomboid Server... ### Project Zomboid Server updated. ### Checking if this is the first run... ### This is the first run. ### Starting Project Zomboid Server... ### Project Zomboid Server stopped. ### First run check complete. ### Applying Post Install Configuration... ### Post Install Configuration applied. ### Starting Project Zomboid Server... ### Project Zomboid Server stopped. |
|
I am also having the same problem now. Six days ago, I made a container and is currently running. Only the ip.txt file is created in the ZomboidConfig folder. Command - docker-compose up -d OS - Ubuntu 20.04.3 LTS ---- logs ---- |
|
I suspected an issue with kernel compatibility, similar to https://github.com/lloesche/valheim-server-docker/issues/401, so tried with the older kernel on the Deb 11, and also with a fresh Deb 10 install with the same results every time. @Renegade-Master, which flavour and version of Linux do you work in to make this container? I would like to see if I get the same error from trying to do it in a VM of that. I even tried (on the debian 11 VM) pulling the 2.3.0 version with the same log output. At this point I'd say it's down to something machine-specific, or somethign with steamcmd. Was there maybe a recent update to steamctl that's broken things (I'm not sure if the 2.3.0 version would pull the same latest steamctl version on first run)? |
|
Also running into this exact issue. Ubuntu 22.04 x64 VM, pre-created the required mapped folders with the correct permissions. |
Running this as root will give you more problems than you started with. It says not to do that in multiple places in the README, as well as it being a pinned issue. I'm working on a potential fix for this in a new PR #60. The extra "same" issues being reported by others in this thread are not necessarily related at all, and do nothing to help. Please only comment if you have actual information 🙂 |
Ah, noob mistake, my apologies. max@debian-pz: 2cf2958bcb3538fdbaa8ff987b438e351ea23d31c5f21d6d23901e478b94cee4 max@debian-pz:~/ws/zomboid-server$ docker logs --follow zomboid-server ### Setting variables... ### Applying Pre Install Configuration... ### Pre Install Configuration applied. ### Updating Project Zomboid Server... ### Project Zomboid Server updated. ### Checking if this is the first run... ### This is the first run. ### Starting Project Zomboid Server... ### Project Zomboid Server stopped. ### First run check complete. ### Applying Post Install Configuration... ### Post Install Configuration applied. ### Starting Project Zomboid Server... ### Project Zomboid Server stopped. max@debian-pz:~/ws/zomboid-server$ cd /ws/project-zomboid/ zomboid-server max@debian-pz:/ws/project-zomboid$ mkdir ZomboidConfig eaecab19f20cd6283c01ffff4d559fd55f63b66a82f3c9cf02c4d13aab489db0 max@debian-pz:/ws/project-zomboid$ docker logs --follow zomboid-server ### Setting variables... ### Applying Pre Install Configuration... ### Pre Install Configuration applied. ### Updating Project Zomboid Server... ### Project Zomboid Server updated. ### Checking if this is the first run... ### This is the first run. ### Starting Project Zomboid Server... ### Project Zomboid Server stopped. ### First run check complete. ### Applying Post Install Configuration... ### Post Install Configuration applied. ### Starting Project Zomboid Server... ### Project Zomboid Server stopped. |
|
Same error -> Welcome to Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-1031-azure x86_64) |
|
Same issue here. Google seems to point to Steam being the issue here but the fact that this is still happening a few days later probably isn't the case. My stack is identical to Ronin's. |
|
While I work on a fix, has anyone tried using an older version of this image? Steam and Zomboid will still be up to date in older images. |
|
I tried 2.3 and gave up after that. Didnt try older than that. |
|
I did try pulling 2.3.0 with the same segfault and same log output. |
|
If older versions aren't working either, it's looking more like Steam's fault. I'll still be working on this fix though |
|
I thought so too but I would expect afeys image to also have the same issue if that was the case. |
|
My images always download latest Steam during runtime. Most other images package them. |
|
I've kicked off a GH Action to see what it does. |
|
It failed! 🎉 In one way this is a good thing because we know it isn't the image. Literally nothing except time has changed between those two runs, so we at least know that the issue is a recent Steamcmd update. |
|
Hello. Any update on this? I tried both on Windows with Docker Desktop and on Ubuntu but it's always the same result :( |
Yes, the developer gave an update just 2 days ago. They will assuredly post again once they have some news. |
|
Sorry, I just thought I'd ask if there was any update concerning the situation since it doesn't seem related to this docker at all. |
|
Hi, The issue at the moment is that it appears that latest I found a thread that mentions encountering similar issues, and that appears to come down to dependencies. Steam doesn't make it easy to specify a particular verion that I may want to download. I can either download the latest (which is what I do), or I can use a distribution of I will re-run the GH Action every now and again while I work away on my other fix [#60]. Unfortunately there is no guarantee that what I am working on there will have any impact on this. If the below build passes, I will update here because that means that the image works again.
|
|
@KillahB33 sorry but what is afey's docker image? I tried to find it but couldn't. |
|
@Acemond i think its this one: https://hub.docker.com/r/afey/zomboid |
|
Yes that is it, but as mentioned it's not as polished as this image so you will need to mount both directories and potentially modify some server files directly. |
|
Yeah but with this one I have the segmentation fault issue so I can’t do anything anyway. I don’t mind putting some manual work here and there, I just want something that runs in a container without having to do it from scratch myself. |
|
Same, just never know how technically capable people are so figured i would give a heads up. |
|
I'm still waiting when Renegade-Master to find a way to run his docker iso. |
|
Thank you for the interest guys. It still surprises me that so many people use this image. I am pretty pushed for time as I have to work on this when I am not feeling drained after my actual job, but I will try to put some more time into finding the route cause of this as soon as I can. I still think the issue lies with Steam, but I will probably have to find some kind of workaround. This is not really acceptable. |
|
If I get a version working that requires running as root, but does at least work, would anyone here be up for trying it out? Also, does running the image with This branch is working for me locally, although it still isn't working in GitHub Actions: I used the following command to build and run the image: $ docker build \
-t docker.io/renegademaster/zomboid-dedicated-server:new_test \
-f docker/zomboid-dedicated-server.Dockerfile . \
&& docker run --rm \
--mount type=bind,source="$(pwd)/ZomboidDedicatedServer",target=/home/steam/ZomboidDedicatedServer \
--mount type=bind,source="$(pwd)/ZomboidConfig",target=/home/steam/Zomboid \
--publish 16261:16261/udp --publish 16262:16262/udp \
--name zomboid-server \
--env DEBUG="true" \
--user 0:0 \
docker.io/renegademaster/zomboid-dedicated-server:new_test |
|
I would have no real issues with a run as root version, and will be happy to test it. |
|
What is currently on that branch (here is the exact commit for berevity: zomboid-dedicated-server/tree/9747f961a8c08b2dc1236dd8783c15725f0036cb) is working me for locally with the command I mentioned above. I don't have to run Docker itself as sudo, but I am in the Docker group on my machine. I managed to join the server running in a VM from my Windows host OS. |
|
@Renegade-Master I tried running your steam_user branch locally on my fedora server and I got further than the main branch as far as the seg fault goes but I am encountering file permission issues. I'll try troubleshooting on my end but figured I'd send you the logs in the meantime. EDIT: |
|
And just out of interest, what does the following do: # Rebuild the image with new source
sudo rm -rf ZomboidConfig ZomboidDedicatedServer
sudo mkdir ZomboidConfig ZomboidDedicatedServer
sudo docker run --detach \
--mount type=bind,source="$(pwd)/ZomboidDedicatedServer",target=/home/steam/ZomboidDedicatedServer \
--mount type=bind,source="$(pwd)/ZomboidConfig",target=/home/steam/Zomboid \
--publish 16261:16261/udp --publish 16262:16262/udp \
--name zomboid-server \
--restart=no \
--env ADMIN_PASSWORD=foobar\
--env ADMIN_USERNAME=sonicd007 \
--env MOD_NAMES="MinimalDisplayBars;TheStar;RainWash;ExtraMapSymbols;ExtraMapSymbolsUI;P4HasBeenRead;MapLegendUI;MiniHealthPanel;Skateboard;GunSuicide;VISIBLE_BACKPACK_BACKGROUND;TrueActionsDancing;CombatText;BetterSortCC;" \
--env MOD_WORKSHOP_IDS="2313387159;2619072426;2004998206;2657661246;2701170568;2544353492;2710167561;2866258937;2728300240;2402057349;2808679062;2648779556;2286124931;" \
--env RCON_PASSWORD=foobar \
--env SERVER_NAME=SonicD007server \
--env SERVER_PASSWORD=foo \
--env TZ=EST \
--env DEBUG="true" \
--user 0:0 \
docker.io/renegademaster/zomboid-dedicated-server:new_testAlso, make sure to update your local verison of the branch. I have been continuing to work on it. git add .
git stash
git fetch -a
git pull origin steam_user
git stash popOr just download the package again. I'm not sure how you interact with the repo. |
|
The error you are getting is the same one that the GitHub Action runs are getting at the moment. |
|
I pulled the latest from steam_user, removed the image and container, rebuilt, created a test directory on the host of docker, created executed Seems like the process terminated within the container as I don't see the container running via |
|
I noticed that it did that once or twice for me where it just exited at the end. Just start it up again, and it should be fine. So, at least the image can be made to work again. I might release what we have here over the weekend. I don't like that it has to be run this way at the moment, but at least it is working. |
|
I've tried restarting the container several times but I haven't had a fully successful run. I keep getting |
|
Try docker rm zomboid-serverand then try again, make sure to use sudo |
|
So I removed the container via And I'm still getting the unknown command process-status@eof On the bright side, this seems to be the server process itself that's throwing the error. Maybe there's an argument being sent to the pz server binary that's causing this issue? process-status@eof seems to be what it's complaining about. Could process-status be some command the pz server is expecting and @eof is somehow getting appended to it? Sometimes files are creating using the cat command with the file termination descriptor being @eof i.e. https://stackoverflow.com/questions/22697688/how-to-cat-eof-a-file-containing-code |
|
And it definitely isn't running in this state? The |
|
Nevermind, it's running now. Not sure what fixed it as it wasn't showing in Looks like it's up and running now |
|
Well, this is good, but also you shouldn't have to run it like that. |
|
Just a note, thanks to the clue mentioned in #64, If you update the base image from steamcmd-minimal:1.1.2 to steamcmd-minimal:2.0.0-root it will work. Using steamcmd-minimal:2.0.0 will not work as root is required in the current zomboid-dedicated-server image. -ARG BASE_IMAGE="docker.io/renegademaster/steamcmd-minimal:1.1.2"
+ARG BASE_IMAGE="renegademaster/steamcmd-minimal:2.0.0-root" |
|
Hey, I'm still encountering this issue when running |
I've submitted a pull request which provides a basic solution to this problem #71 |
|
@super-cooper you need to do the changes on docker file as my indication (as @raykrueger say). just first do git pull of Renegade-Master "zomboid-dedicated-server" (https://github.com/Renegade-Master/zomboid-dedicated-server). Or you can create your own docker-compose.yaml/docker-file (with "renegademaster/steamcmd-minimal:2.0.0-root" and then copy de "src" folder with contained files (edit_server_config.py, install_server.scmd, run_server.sh -> https://github.com/Renegade-Master/zomboid-dedicated-server/tree/main/src) inside your root docker-compose project. |
|
I tried to rebuild the steamcmd and zomboid images, but they are on nonstable versions of ubuntu, so i ended going down a rabbit hole and just creating my own from scratch. |
Describe the bug
steamcmd.sh returned a segmentation fault during post-install config stage.
In a subsequent step, the server ini and ProjectZomboid64.json were not found.
To Reproduce
Steps to reproduce the behavior:
2023-02-05 06:58:30
2023-02-05 06:58:30 ### Setting variables...
2023-02-05 06:58:30
2023-02-05 06:58:30 ### Applying Pre Install Configuration...
2023-02-05 06:58:30
2023-02-05 06:58:30 ### Pre Install Configuration applied.
2023-02-05 06:58:30
2023-02-05 06:58:30 ### Updating Project Zomboid Server...
2023-02-05 06:59:06
2023-02-05 06:59:06 ### Project Zomboid Server updated.
2023-02-05 06:59:06
2023-02-05 06:59:06 ### Checking if this is the first run...
2023-02-05 06:59:06
2023-02-05 06:59:06 ### This is the first run.
2023-02-05 06:59:06 Starting server for 60 seconds
2023-02-05 06:59:06
2023-02-05 06:59:06 ### Starting Project Zomboid Server...
2023-02-05 06:59:06
2023-02-05 06:59:06 ### Project Zomboid Server stopped.
2023-02-05 06:59:06
2023-02-05 06:59:06 ### First run check complete.
2023-02-05 06:59:06
2023-02-05 06:59:06 ### Applying Post Install Configuration...
2023-02-05 06:59:06 /usr/bin/steamcmd.sh: line 38: 13 Segmentation fault DEBUGGER STEAMEXE @
EDIT I noticed the previous line was not displaying, I guess was interpreted as markdown. I removed all the dollar signs preceding DEBUGGER, STEAMEXE, and @.
2023-02-05 06:59:06 timeout: failed to run command '/home/steam/ZomboidDedicatedServer/start-server.sh': No such file or directory
2023-02-05 06:59:06 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:06 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:06 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:06 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:06 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:07 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:07 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:07 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:07 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:07 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:07 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:07 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:07 /home/steam/Zomboid/Server/EchoHill.ini not found!
2023-02-05 06:59:07 sed: can't read /home/steam/ZomboidDedicatedServer/ProjectZomboid64.json: No such file or directory
2023-02-05 06:59:07 sed: can't read /home/steam/ZomboidDedicatedServer/ProjectZomboid64.json: No such file or directory
2023-02-05 06:59:07 timeout: failed to run command '/home/steam/ZomboidDedicatedServer/start-server.sh': No such file or directory
2023-02-05 06:59:07
2023-02-05 06:59:07 ### Post Install Configuration applied.
2023-02-05 06:59:07
Expected behavior
PZ server would remain running, and I would see the "LuaNet: Initialization [DONE]" message in the console.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: