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:

Oh sorry! Didn't mention, that i blanked out half of the GameID for safety. I tried a bit and it's joinable from my laptop, but not from my Steamdeck. So maybe it's a Linux issue? I can PN the GameID if you want.

 

Thank you for helping

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.

Solved the problem! Preset it starts with the latest version of Proton on my steamdeck. Changed and forced this to use Linux Runtime, deleted proton files —-> works like charm!

 

thank you very much for your work 🙌

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.

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

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.

1 hour ago, Taiwendo said:

in the download API you can change the channel

I will look into this ASAP and report back, please give me a few days…

2 hours ago, Taiwendo said:

Thanks for your efforts.

Please update the container first and then create a variable like that:

 

You will be now able to change the release channel from the game now.

 

Hope that helps.

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.

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) :

(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) :

 

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.

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 July 11, 20224 yr by John2222

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.

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 July 11, 20224 yr by John2222

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 July 11, 20224 yr by Jupiler

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.

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.

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!

I just updated my Valhiem server and the world is reset, did I miss a setting somewhere or is that normal? Lost a lot of progress oof

Is there a way to manage backups or automate or would I need to manually save the world file everytime theres an update?

Edited July 12, 20223 yr by Sporical

1 hour ago, Sporical said:

I just updated my Valhiem server and the world is reset, did I miss a setting somewhere or is that normal? Lost a lot of progress oof

The container has a built in backup function and should be activated automatically.

 

Please go to your Valheim directory and look if you got a "Backup" folder in it.

 

1 hour ago, Sporical said:

Is there a way to manage backups or automate or would I need to manually save the world file everytime theres an update?

A recent update from Valheim wiped all save files, but there is nothing I can do about, rather the developers from Valheim messed up a bit I think.

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

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 50.05 kB · 1 download

ArmA3 x86.txt 49.1 kB · 1 download

(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.

I've done some search for the problem in the 32bit log:  "steamclient.so: cannot open shared object file: No such file or directory":
It seems there is some symlink missing or the rights are not set correctly.

https://community.7daystodie.com/topic/19590-dlopen-failed-trying-to-load-steamclientso-fixed/

 

Edited July 12, 20223 yr by John2222

14 minutes ago, John2222 said:

It seems there is some symlink missing or the rights are not set correctly.

Haven't got time to look into this, also don't know what 7DtD have to do with ArmA3.

These are two different engines from what I know.

 

I will fix this but I'm very busy at the moment in real life and this will take some time.

17 hours ago, ich777 said:

The container has a built in backup function and should be activated automatically.

 

Please go to your Valheim directory and look if you got a "Backup" folder in it.

 

A recent update from Valheim wiped all save files, but there is nothing I can do about, rather the developers from Valheim messed up a bit I think.

Ahh, ok good to know. Thank you for getting back to me!

Thank you for the effort @ich777you put in into those gameservers  Since a few updates the stationeers image ist broken, because the devs decided to refactor the entire codebase. Therefore the startup command have changed significantly. Do you have any plans to "fix" them?

The new ones are documented here: https://github.com/rocket2guns/StationeersDedicatedServerGuide/blob/main/README.md

Edited July 13, 20223 yr by Disane

1 hour ago, Disane said:

Do you have any plans to "fix" them?

You have to fix the startup commands, or at least the variables from "GAME_PARAMS" yourself in the template since my templates doesn't update itself if I change anything, see this post here how to do it:

 

Should be enough to change it like: