[Bug]: Issues with migrated ingame project zomboid server to linuxGSM docker container

RagingFlames commented 11 months ago

User story

As a project zomboid server host, I want to be able to use the server console without errors, so that I can run and/or shutdown the server.

Game

Project Zomboid

Linux distro

Ubuntu 22.04, Debian 11

Command

command: console

Further information

The server is running debian 11, the docker container reports as Ubuntu.

I was running a project zomboid server thru the ingame server hosting feature. I wanted to switch to a dedicated server, so I moved over the ingame data to the new dedicated server I was setting up. Initially I was having trouble with our player data not transferring but I found this guide and that straightened everything out. After fixing that I started playing with my friends on the server and immediately ran into problems.

First, whenever I would run a command, like to make someone an admin, the server would show an sql error, and then say that I need to whitelist that player in order to make them an admin. If I tried to whitelist a player, it would just show an sql error. Interestingly, if the player I wanted to make an admin was online, it would actually make them an admin, but this setting would not persist.

Second, I've left the server running for 2 weeks now and I came back to it to try and shut it down and maybe move to a different solution. However, when I tried to access the server console I got this.

So I can no longer change anything about the server. I can't provide screenshots of the first problem, because I didn't save any and can't access the server anymore. And I can't provide logs because I can't access the server.

Relevant log output

No response

Steps to reproduce

Setup the linuxGSM ProjectZomboid docker server
Transfer a save from the ingame host to the new dedicated host
Try to make someone an admin
Try to white list someone
Try to access the server console

dgibbs64 commented 11 months ago

Just noticed your version of LinuxGSM is out of date. you need to update your docker image

RagingFlames commented 11 months ago

I updated the docker yaml to have it update on launch

version: '3'
services:
  lgsm-zomboid:
    image: gameservermanagers/gameserver:pz
    pull_policy: always
    container_name: lgsm-zomboid
    restart: unless-stopped
    network_mode: host
    ports:
    - "16261:16261"
    - "16262:16262"
    volumes:
    - /home/my-name/zomboid:/data

It did update but I have the same problem

RagingFlames commented 11 months ago

Some updates on this, so I learned that the problem was that the LGSM_SERVERFILES environment variable wasn't getting set. I have no idea why. I set it manually when I launch the container for now. I can at least run the pz server script now, but I have a new problem.

The server is absolutely 100% running. I can connect to it and play. If I tell the script to start the server, it'll start a second instance of the pzserver, that will fail to startup.

dgibbs64 commented 11 months ago

How odd the env variables are not working for you. I am having no issues with my servers. Are you have the latest image by using docker pull?

docker pull gameservermanagers/gameserver:pz

RagingFlames commented 11 months ago

How odd the env variables are not working for you. I am having no issues with my servers. Are you have the latest image by using docker pull?
docker pull gameservermanagers/gameserver:pz

I get this back

I updated the docker yaml to have it update on launch

I updated my docker yaml to update whenever I launch it, so I should always be up to date.

RagingFlames commented 11 months ago

I switched everything over to the official server software that's outlined on the wiki. Everything works perfectly now, so what ever was wrong it is something to do with LGSM or my container. If people want to mark this as closed, I'm fine with it, but the LGSM container still doesn't work.

GameServerManagers / LinuxGSM