starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-24 21:56:01 +03:00

[GH-ISSUE #4773] [Bug]: 7 Days to Die server doesn't start, Permission denied. #2964

New issue

Open

opened 2026-02-27 03:06:32 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 03:06:32 +03:00

Owner

Originally created by @Dumuthy on GitHub (Mar 29, 2025).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4773

User story

Trying to install 7 Days to Die server using the vinanrra/7dtd-server image, which relies on lgsm for internal control actions of the server such as starting and stopping it. During install, everything goes smoothly up intill the actual gameserver attempts to start using the ./sdtdserver start command. At which point, the server fails to start with a "Permission Denied" error. Logs below.

Game

7 Days to Die

Linux distro

Other

Command

command: start

Further information

I chose Other for the distro because I'm running docker on Arch. I know, I know, don't run servers on bleeding edge distros. I'm working on that. However, I see no reason why this should be making a difference here. Also, my docker-root directory is a 5TB RAID volume mounted at /mnt/Storage, which I have ensured has correct permissions by running sudo chown -R 1000:1000 /mnt/Storage after the permission denied issue occurred. Docker is set to run in rootless mode.

Since the ./sdtdserver start and the ./sdtdserver debug commands equate to the same thing, but the latter gives details about the starting process, I've pasted logs of the debug command. Every other command that I have tried works perfectly fine, including update, update-lgsm, install, details, monitor, and validate. I'm not certain if any other information is needed, but I'm happy to provide it upon request.

Relevant log output

7 Days To Die Debugging
=================================
Distro:          Ubuntu 24.04.1 LTS
Architecture:    x86_64
Kernel:          6.13.8-zen1-1-zen
Hostname:        5b75e049e17d
tmux:            3.4
Avg Load:        0.42, 0.54, 1.34
Free Memory:     14GB
Free Disk:       4.6T
glibc required: 2.27
Game Server IP: 0.0.0.0:26900
Internet IP:    135.84.8.148:26900
Server password:        NOT SET
Start parameters:
 ./7DaysToDieServer.x86_64 -quit -batchmode -nographics -dedicated -configfile=/home/sdtdserver/serverfiles/sdtdserver.xml
 
Use debug for identifying server issues only!
Press CTRL+c to drop out of debug mode.
Warning! If sdtdserver is already running it will be stopped.
 
Continue? [Y/n] Y
[ INFO ] Debugging sdtdserver: Stopping any running servers
[ SKIP ] Stopping sdtdserver: My Game Host is already stopped
[  OK  ] Debugging sdtdserver: Starting debug
/home/sdtdserver/lgsm/modules/command_debug.sh: line 123: ./7DaysToDieServer.x86_64: Permission denied
[ ERROR ] Debugging sdtdserver: Server has stopped: exit code: 126
[ ERROR ] Debugging sdtdserver: Press ENTER to exit debug mode

Steps to reproduce

Open Dockge in my browser and copy/edit config.yaml for the container.
Click deploy container
Watch everything succeed without so much as a single warning or error up until the ./sdtdserver start command is run in order to actually initiate the server instance within the container.
Cry.

Originally created by @Dumuthy on GitHub (Mar 29, 2025). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4773 ### User story Trying to install 7 Days to Die server using the vinanrra/7dtd-server image, which relies on lgsm for internal control actions of the server such as starting and stopping it. During install, everything goes smoothly up intill the actual gameserver attempts to start using the `./sdtdserver start` command. At which point, the server fails to start with a "Permission Denied" error. Logs below. ### Game 7 Days to Die ### Linux distro Other ### Command command: start ### Further information I chose Other for the distro because I'm running docker on Arch. I know, I know, don't run servers on bleeding edge distros. I'm working on that. However, I see no reason why this should be making a difference here. Also, my docker-root directory is a 5TB RAID volume mounted at /mnt/Storage, which I have ensured has correct permissions by running `sudo chown -R 1000:1000 /mnt/Storage` after the permission denied issue occurred. Docker is set to run in rootless mode. Since the `./sdtdserver start` and the `./sdtdserver debug` commands equate to the same thing, but the latter gives details about the starting process, I've pasted logs of the debug command. Every other command that I have tried works perfectly fine, including update, update-lgsm, install, details, monitor, and validate. I'm not certain if any other information is needed, but I'm happy to provide it upon request. ### Relevant log output ```shell 7 Days To Die Debugging ================================= Distro: Ubuntu 24.04.1 LTS Architecture: x86_64 Kernel: 6.13.8-zen1-1-zen Hostname: 5b75e049e17d tmux: 3.4 Avg Load: 0.42, 0.54, 1.34 Free Memory: 14GB Free Disk: 4.6T glibc required: 2.27 Game Server IP: 0.0.0.0:26900 Internet IP: 135.84.8.148:26900 Server password: NOT SET Start parameters: ./7DaysToDieServer.x86_64 -quit -batchmode -nographics -dedicated -configfile=/home/sdtdserver/serverfiles/sdtdserver.xml Use debug for identifying server issues only! Press CTRL+c to drop out of debug mode. Warning! If sdtdserver is already running it will be stopped. Continue? [Y/n] Y [ INFO ] Debugging sdtdserver: Stopping any running servers [ SKIP ] Stopping sdtdserver: My Game Host is already stopped [ OK ] Debugging sdtdserver: Starting debug /home/sdtdserver/lgsm/modules/command_debug.sh: line 123: ./7DaysToDieServer.x86_64: Permission denied [ ERROR ] Debugging sdtdserver: Server has stopped: exit code: 126 [ ERROR ] Debugging sdtdserver: Press ENTER to exit debug mode ``` ### Steps to reproduce 1. Open Dockge in my browser and copy/edit config.yaml for the container. 2. Click deploy container 3. Watch everything succeed without so much as a single warning or error up until the ./sdtdserver start command is run in order to actually initiate the server instance within the container. 4. Cry.

kerem added the

labels

2026-02-27 03:06:32 +03:00

kerem commented

2026-02-27 03:06:33 +03:00

Author

Owner

@Dumuthy commented on GitHub (Mar 31, 2025):

Update, this is not an issue with how the container is deployed. Dockge, Portainer, and even just command line will not work. Same results no matter what method is used to deploy the container. It's also not the permissions of the host file system, as all volume variables were removed and I allowed Docker to decide where volumes would be placed.

The issue appears to be in the "7DaysToDieServer.x86_64" executable permissions. When checking the permissions after logging into the container with docker exec -it 7days sh, hunting the file down in ~/serverfiles, and running ls -l on the file, the result is...
-rwxr-xr-x 1 sdtdserver sdtdserver 14800 Mar 31 15:57 7DaysToDieServer.x86_64

I do not know what they should be, so I'm leaving this open for now, as I don't want to attempt to change the permissions and create more issues that might make the problems worse.

@Dumuthy commented on GitHub (Mar 31, 2025): Update, this is not an issue with how the container is deployed. Dockge, Portainer, and even just command line will not work. Same results no matter what method is used to deploy the container. It's also not the permissions of the host file system, as all volume variables were removed and I allowed Docker to decide where volumes would be placed. The issue appears to be in the "7DaysToDieServer.x86_64" executable permissions. When checking the permissions after logging into the container with `docker exec -it 7days sh`, hunting the file down in `~/serverfiles`, and running `ls -l` on the file, the result is... `-rwxr-xr-x 1 sdtdserver sdtdserver 14800 Mar 31 15:57 7DaysToDieServer.x86_64` I do not know what they should be, so I'm leaving this open for now, as I don't want to attempt to change the permissions and create more issues that might make the problems worse.

kerem commented

2026-02-27 03:06:33 +03:00

Author

Owner

@Dumuthy commented on GitHub (Apr 7, 2025):

Cross posted this issue/bug here...
https://github.com/vinanrra/Docker-7DaysToDie/issues/298

@Dumuthy commented on GitHub (Apr 7, 2025): Cross posted this issue/bug here... https://github.com/vinanrra/Docker-7DaysToDie/issues/298

kerem referenced this issue

2026-02-27 03:56:04 +03:00

[PR #2964] [MERGED] feat(details): add appid and branch password to details #3855