[Support] ich777 - Gameserver Dockers


Recommended Posts

39 minutes ago, John2222 said:

* GCC 4.9.0 and

* GCC 5.1.0

This wont change anything... You don't need the compiler itself in the container, you only need the runtime libraries that are compatible with the compiler that was used to compiled the binary usually the libraries are backwards compatible because Debian Bullseye is using GCC 10.2.1

 

May I ask on what Unraid version are you?

 

I will investigate further when I got more time and install it on my server.

Link to comment
21 minutes ago, ich777 said:

This wont change anything... You don't need the compiler itself in the container, you only need the runtime libraries that are compatible with the compiler that was used to compiled the binary usually the libraries are backwards compatible because Debian Bullseye is using GCC 10.2.1

 

May I ask on what Unraid version are you?

I'm on 6.10.3

Iv'e got some answers from the devs:
"We recently updated our Linux builder, as we kept running into odd compiler errors and bugs. We should be building all 32bit and 64bit binaries for Linux on the new builder from now on, which builds using glibc 2.28. We won't be using new versions of glibc, because as of 2.31 they got rid of some -ffinite-math-only stuff needed by one of the libraries we use."

So this means the actual debian version (bullseye) is too new (because of GlibC 2.31), right?

Edited by John2222
Link to comment

Will these containers redownload the server files every time the container is started? Or only if there is an update? Is there a universal variable to pin the version so it doesn't redownload?

 

I'm looking at ARK in particular but it'd be nice to know for the other containers too. ARK is 200GiB for the client side. It's probably similar for the server too.

Link to comment
52 minutes ago, Freddy23 said:

Will these containers redownload the server files every time the container is started?

Why should they?

It‘s like if you have them installed on a bare metal machine and the container will only check if a new update is available if a new version is released on container restart (this is also mentioned in the description of the container).

If no update is available nothing will be pulled/downloaded.

 

52 minutes ago, Freddy23 said:

Is there a universal variable to pin the version so it doesn't redownload?

Universal…? Depends on what is universal, you can append „-beta WHATEVERBRANCHYOUNEED“ (also like if you run steamcmd on a regular server on bare metal) to the GAME ID variable.

However the usage of branches is always unique to the games itself because every developer uses this a little different.

(I think I even put an example in the description of the variable in the container template).

 

52 minutes ago, Freddy23 said:

ARK is 200GiB for the client side. It's probably similar for the server too.

Not eveon close I think for the server side, it‘s still a lot but I think we are talking about 35 to 50GB IIRC.

  • Thanks 1
Link to comment
On 7/8/2022 at 4:44 PM, John2222 said:

Another possible fix can maybe this:
https://askubuntu.com/questions/575505/glibcxx-3-4-20-not-found-how-to-fix-this-error/582910#582910

 

This means to install/upgrade libstdc++6 as i understand.

 

Because the issues seems not with glibc but with glibc++.

 

Sorry but I can't reproduce the issue that you are describing here.

 

I've now installed ArmA3 on my server and both x64 and also the x86 version work and starting just fine:

ArmA3 x64.txt

ArmA3 x86.txt

(attached both logs)

 

Maybe try to remove the container entirely, delete the folder in you appdata directory for arma3 (maybe also try to restart your Unraid server after that) and pull a fresh copy from the CA App.

Link to comment

CoreKeeper connection issue:

 

Hey ich777 :) I really enjoy your game server dockers, great job! But i´m facing an issue with CoreKeeper. Every time i want to join a server on my unRAID the game crashes on my client device. The log file has no errors in it. Any idea what i can try to fix this?

 

Thank you very much

CoreKeeperLog.png

Link to comment
42 minutes ago, HubertusPrime said:

CoreKeeper connection issue:

Is your server still running?

Since you've posted a screenshot from your GameID I've tried to connect but it times out...

 

I've now pulled a fresh copy from the CA App and it works just fine over here.

Have you yet tried to validate the game files on your local computer? Maybe the game files are corrupt...

 

If you want me to try to connect to your server let me know and send me the Game ID or at least start the server so that I can try it.

 

You can also try to connect to my server if you want to but I think this is more of a Client side issue in your case.

 

Took a screenshot here:

grafik.thumb.png.0452feff209afd7322ac359f0b9aea1c.png

Link to comment
2 minutes ago, HubertusPrime said:

I can PN the GameID if you want.

Sure thing... send me a PM, but I don't think that much will change...

 

I have to wait a little longer for my Deck to arrive since I've preordered a little too late... :/

So I really can't tell what's wrong on the Deck.

Link to comment

Hello, running into some issues when running the V Rising version of the container, I left all the parameters as default, didn't change any configuration, and on first boot, here is the log it produces, it keeps looping after a certain point

 

---Ensuring UID: 99 matches user---
---Ensuring GID: 100 matches user---
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Taking ownership of data...---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1654574676

-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
/serverdata/steamcmd/steamcmd.sh: line 39: 32 Killed $DEBUGGER "$STEAMEXE" "$@"

Waiting for user info...---Update Server---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1654574676

-- type 'quit' to exit --
Loading Steam API...OK
"@sSteamCmdForcePlatformType" = "windows"
�[0m
Connecting anonymously to Steam Public...OK
Waiting for client config...OK
/serverdata/steamcmd/steamcmd.sh: line 39: 54 Killed $DEBUGGER "$STEAMEXE" "$@"

Waiting for user info...---BepInEx for V Rising disabled!---
---Checking if WINE workdirectory is present---
---WINE workdirectory found---
---Checking if WINE is properly installed---
---WINE properly set up---
---Checking for old display lock files---
---Server ready---
---Start Server---
tail: cannot open '/serverdata/serverfiles/logs/VRisingServer.log' for reading: No such file or directory
tail: no files remaining
tail: invalid PID: ‘’
/opt/scripts/start-watchdog.sh: line 6: kill: `': not a pid or valid job spec

---Ensuring UID: 99 matches user---
usermod: no changes
---Ensuring GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Taking ownership of data...---
---Starting...---
---Update SteamCMD---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1654574676

-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
/serverdata/steamcmd/steamcmd.sh: line 39: 20 Killed $DEBUGGER "$STEAMEXE" "$@"

Waiting for user info...---Update Server---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1654574676

-- type 'quit' to exit --
Loading Steam API...OK
"@sSteamCmdForcePlatformType" = "windows"
�[0m
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1654574676

-- type 'quit' to exit --
Loading Steam API...OK
"@sSteamCmdForcePlatformType" = "windows"
�[0m
Connecting anonymously to Steam Public...OK
Waiting for client config...OK
/serverdata/steamcmd/steamcmd.sh: line 39: 40 Killed $DEBUGGER "$STEAMEXE" "$@"

Waiting for user info...---BepInEx for V Rising disabled!---
---Checking if WINE workdirectory is present---
---WINE workdirectory found---
---Checking if WINE is properly installed---
---WINE properly set up---
---Checking for old display lock files---
---Server ready---
---Start Server---
tail: cannot open '/serverdata/serverfiles/logs/VRisingServer.log' for reading: No such file or directory
tail: no files remaining
tail: invalid PID: ‘’
/opt/scripts/start-watchdog.sh: line 6: kill: `': not a pid or valid job spec

---Ensuring UID: 99 matches user---
usermod: no changes
---Ensuring GID: 100 matches user---
---Ensuring UID: 99 matches user---
usermod: no changes
---Ensuring GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Taking ownership of data...---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1654574676

-- type 'quit' to exit --
Loading Steam API...OK

Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1654574676

-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
/serverdata/steamcmd/steamcmd.sh: line 39: 20 Killed $DEBUGGER "$STEAMEXE" "$@"

Waiting for user info...---Update Server---

 

Maybe more specifically tied to this?

Quote

tail: cannot open '/serverdata/serverfiles/logs/VRisingServer.log' for reading: No such file or directory

 

Any help/insight appreciated! I have a Valheim version of the same container running flawlessly for months.

Link to comment
1 hour ago, Jupiler said:

Maybe more specifically tied to this?

On what Unraid version are you?

What CPU are you running? Is the appdata share set to use cache only or prefer in the Share settings? What path is specified in the Docker template?

 

EDIT: If you are not already on 6.10.3 then I would strongly recommend to upgrade -> I think this causes actually the issue.

If you are on a AMD platform, try to change the path from /mnt/cache/... to /mnt/user/... in the template. <- try this only if you are already on 6.10.3

Link to comment

Hi ich777,

would it be possible to extend the config of the "Vintage Story Server".
in the download API you can change the channel;


...api.vintagestory.at/stable.json
...api.vintagestory.at/unstable.json
and
...api.vintagestory.at/pre.json

select.


Since the Pre-version offers the most features it would be cool if you add an option to switch to the Pre-version.

 

Thanks for your efforts.

 

Ps: if I can change this myself give me a tip I have tried everything.

Link to comment

Hi, I am trying to set up Rust dedicated server and used the following to run the docker:

 

docker run --name RUST --log-opt max-size=10m -d \
	-p 28015:28016/udp -p 25576:25576/udp \
	--env 'GAME_ID=258550' \
	--env 'SERVER_NAME=[SG/SEA] Gamers Paradise Rust Server' \
	--env 'SERVER_DISCRIPTION=[SG/SEA] Gamers Paradise Rust Server' \
	--env 'GAME_PARAMS=+server.maxplayers 120 +rcon.port 25576 +rcon.password xxxxxxx' \
	--env 'GAME_PORT=28015' \
	--env 'UID=1001' \
	--env 'GID=1001' \
	--env 'OXIDE_MOD=true' \
	--volume /home/rust/steamcmd:/serverdata/steamcmd \
	--volume /home/rust/steamcmd/rust:/serverdata/serverfiles \
	ich777/steamcmd:rust

 

However, when I look at the docker logs, it got killed at certain stage:

 

[7.6s] Harbors
(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)

[5.6s] Fishing Villages
(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)

[1.8s] Desert Military
(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)

[1.5s] Arctic Bases
(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)

/opt/scripts/start-server.sh: line 107:    83 Killed                  ${SERVER_DIR}/RustDedicated -batchmode +server.port ${GAME_PORT} +server.hostname "${SERVER_NAME}" +server.description "${SERVER_DISCRIPTION}" ${GAME_PARAMS}

 

Does anyone know what did I do wrong?

 

Thanks.

Link to comment
30 minutes ago, ekiken said:

Hi, I am trying to set up Rust dedicated server and used the following to run the docker:

From what I see you are not running the container on Unraid or am I wrong? What OS are you using and which version from the OS?

 

30 minutes ago, ekiken said:
	--volume /home/rust/steamcmd:/serverdata/steamcmd \
	--volume /home/rust/steamcmd/rust:/serverdata/serverfiles \

 

Please don't do the mapping like this...

Rather I would recommend that you use it like /home/rust/steamcmd and /home/rust/rust otherwise you can run into various other issues.

Please also keep in mind that if you run more than this game server from me then you can also use one steamcmd directory for multiple containers and point them to the same steamcmd directory.

 

32 minutes ago, ekiken said:

Does anyone know what did I do wrong?

How much RAM do you have on the machine that you are try to run RUST on? Keep in mind that RUST needs lot's of RAM to run, on my machine it consumes about 13GB of RAM when starting up for the first time without Oxide mod enabled (that is most likely the case on your machine at the stage where it crashes on your system, but I think you must have plenty of RAM since you are creating a server for 120 players) :

image.thumb.png.ab2385c23e705ce2d98aa56bf6b9f685.png

(the screenshot is taken after it fully started)

 

After a second start it uses about 7GB of RAM as you can see here (this is also with Oxide Mod enabled) :

image.thumb.png.0a765afa933c21f9cf93c820b9fb99e2.png

 

I've now tried it on my server and it works without a hitch.

Maybe try to first run it with:

--env 'OXIDE_MOD=false' \

to let it create the world first and then change it to true, at least that is what I've did on my server.

Maybe Oxide has some issues there, I can for sure try to set it to true in the first place and see if this works to if you want me to do that.

Link to comment
On 7/10/2022 at 9:02 AM, ich777 said:

Sorry but I can't reproduce the issue that you are describing here.

 

 

 

This happens in the beta branch, not the stable. I posted the start line in my first post for this issue:

 

"

If you want to try it by yourself, here is the starting line for the GAME_ID parameter:


233780 -beta profiling -betapassword CautionSpecialProfilingAndTestingBranchArma3

"

 

And I start in 32bit "mode".

 

This issue will be a problem for the stable, when the next update is delivered by BI. And this will be happen soon(couple of weeks) as i know.
I load the beta testing branch and also the profiling/performance branch to give feedback to the devs for the supported 32bit linux versions.

Edited by John2222
Link to comment
30 minutes ago, John2222 said:

And I start in 32bit "mode".

Please update the container and try it again, both 64bit and 32bit are now working on my machine.

 

Attached both logs:

x86.txt

x64.txt

 

But I would recommend to use the x86 versions because of known limitations of the x64 versions and Segfaulting on some machines.

Link to comment
1 hour ago, ich777 said:

Please update the container and try it again, both 64bit and 32bit are now working on my machine.

 

Attached both logs:

x86.txt 48.86 kB · 0 downloads

x64.txt 49.64 kB · 0 downloads

 

But I would recommend to use the x86 versions because of known limitations of the x64 versions and Segfaulting on some machines.

Server runs locally, but:
I am kicked because of steam ticket. But reload of steam doesn't help. Maybe this is the Propblem (see last lines of your x86 log):

 

13:42:09 BattlEye Server: Initialized (v1.217)

dlopen failed trying to load:
steamclient.so
with error:
steamclient.so: cannot open shared object file: No such file or directory
[S_API FAIL] SteamAPI_Init(): Sys_LoadModule failed to load: steamclient.so
[S_API FAIL] SteamAPI_Init() failed

 

The steamclient.so is updated in the gamefile folder.
I've started one of the old docker and there is no such errors in the log.

Edited by John2222
Link to comment
18 hours ago, ich777 said:

On what Unraid version are you?

What CPU are you running? Is the appdata share set to use cache only or prefer in the Share settings? What path is specified in the Docker template?

 

EDIT: If you are not already on 6.10.3 then I would strongly recommend to upgrade -> I think this causes actually the issue.

If you are on a AMD platform, try to change the path from /mnt/cache/... to /mnt/user/... in the template. <- try this only if you are already on 6.10.3

 

Updated to 6.10.3, running an intel CPU (Q9400), appdata is set up as "Prefer: Cache" (should I set it up as cache only?). If we're talking about ServerFiles path it's `/mnt/user/appdata/vrising`.

 

Still seeing the same errors after update:

 

tail: cannot open '/serverdata/serverfiles/logs/VRisingServer.log' for reading: No such file or directory
tail: no files remaining
tail: invalid PID: ‘’
/opt/scripts/start-watchdog.sh: line 6: kill: `': not a pid or valid job spec
tail: cannot open '/serverdata/serverfiles/logs/VRisingServer.log' for reading: No such file or directory
tail: no files remaining
tail: invalid PID: ‘’
/opt/scripts/start-watchdog.sh: line 6: kill: `': not a pid or valid job spec

Session terminated, killing shell...kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

 

Edited by Jupiler
Link to comment
5 minutes ago, Jupiler said:

Updated to 6.10.3, running an intel CPU (Q9400), appdata is set up as "Prefer: Cache" (should I set it up as cache only?). If we're talking about ServerFiles path it's `/mnt/user/appdata/vrising`.

Please try the following:

  1. Delete the container
  2. Delete the folder for vrising that lives in your appdata directory
  3. Pull a fresh copy from the CA App and leave everything at default

Hopefully this should solve the issue

 

If it doesn't solves the issue I think it's related to your CPU... Isn't this a Core2Quad? I think it's possible that it doesn't support some instructions which are needed for the game to run.

Link to comment

I've gotten my 7DTD game server running and working. is there a way to set myself as the admin so that people can't access the console in game and spawn themselves items etc? I'm not sure exactly where to go to do that in the files on my server. Any help is greatly appreciated.

Link to comment
34 minutes ago, GastonMT said:

I've gotten my 7DTD game server running and working. is there a way to set myself as the admin so that people can't access the console in game and spawn themselves items etc? I'm not sure exactly where to go to do that in the files on my server. Any help is greatly appreciated.

Ope, nevermind, found the file! sorry bout that! :)

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.