5 hours ago, devnet said:

Not sure where the name Linux is set nor by what or how but it will change how we have to map the volume.

So I assume everything is now working for you correct?

3 hours ago, bamtan said:

Edit: migrated over the binarylane VPS [AU], debian 11 2core 4gb memory and all working 😃 Thank you

Seems also a bit low but should do the job just fine for 2 - 3 players.

9 minutes ago, ich777 said:

So I assume everything is now working for you correct?

 

Indeed.  The only thing I'm not clear on is the steps to install the mods on an Ark server...I list them in the GameUserSettings.ini and then....not sure.

 

There may be more steps to it...like creating a folder inside the mods directory, and then putting the .mod file in there...but I can't seem to find a proper page of documentation that tells me the proper way to do so.

 

Anyways, thanks again.

4 minutes ago, devnet said:

Indeed.  The only thing I'm not clear on is the steps to install the mods on an Ark server...I list them in the GameUserSettings.ini and then....not sure.

Please read this post over here:

 

I think you also need -automanagemods if I'm not mistaken, after a server restart the server should pull the mods all automatically from my understanding.

10 hours ago, ich777 said:

Please read this post over here:

 

I think you also need -automanagemods if I'm not mistaken, after a server restart the server should pull the mods all automatically from my understanding.

 

 

Yep, I did all those things in that post.  But I'm not seeing folders for each of my mods inside the mod directory after the server starts...so I'm not sure they're downloading and loading server side. 

 

I saw other posts in steamcommunity about installing mods on Linux servers and some folks had to create the mod folder (mod number is the name) and then they had to manually drop the .mod file in there...and I'd rather avoid having to do that.  I'll do some more testing here and report back what happens.

Just a quick update.  Figured out the issue...in the post referenced there is a typo.  It's -automanagedmods and not -automanagemods.

 

Replaced that in my extra game parameters and tried this again....it seems to be doing something because now the container reboots every 11 seconds...trying to trace down logs to see what is going on.

Well I'm not sure what's up...it's stuck in a loop and won't boot and I can't find logs that tell me what's going on.  Just keeps on restarting...

 

Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
---Update Server---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1669935972
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
Success! App '376030' already up to date.
---Prepare Server---
---Server ready---
---Start Server---
---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'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1669935972
-- type 'quit' to exit --
Loading Steam API...OK

 

21 minutes ago, devnet said:

Well I'm not sure what's up...it's stuck in a loop and won't boot and I can't find logs that tell me what's going on.  Just keeps on restarting...

Seems like a mod broke the container that prevent a proper start from Ark.

1 hour ago, ich777 said:

Seems like a mod broke the container that prevent a proper start from Ark.

 

 

I'll try setting this thing up fresh and let you know how it goes.

Force pull on this didn't work but it did give me the following error:

 

 

I'm finding posts on this inside steamcommunity and they're saying in Linux servers you do not need to use -automanagedmods for extra parameters?

 

Not sure what to believe lol.

I think this has to do with the extra space that I found previously in the path for the 'Linux ' directory.  If we mount the automods directory with the instructions from DBone-Unraid, we do the following:

 

 

But that of course, doesn't exist...because the last part is 'Linux ' with the extra space on the end and that's not what is mounted...so we're installing or looking inside a different directory or one that doesn't exist.

 

@ich777 where is that path set?  Do you think if I rename it and remove the space and correct all the paths it will start working or will it pull down a fresh copy with the space if it's set by Steam?  Is this a bug?

Edited January 8, 20233 yr by devnet

7 hours ago, devnet said:

I'm finding posts on this inside steamcommunity and they're saying in Linux servers you do not need to use -automanagedmods for extra parameters?

This can be actually be true but I'm not that familiar with modding the containers exspecially not with Ark.

 

I only provide the base functionality because I can't know how to mod every server and I can't know every mod.

 

Please look into the 2nd recommended post from this thread from @Cyd he has a Github Repo where he describes how to set up a cluster and I'm pretty sure he mentions mods there too. I could be wrong about that but it's worth a try.

7 hours ago, devnet said:

I think this has to do with the extra space that I found previously in the path for the 'Linux ' directory.

This is definitely unexpected that this path has a space in it and I really don't know how to solve that.

Will try that later on my machine.

 

7 hours ago, devnet said:

If we mount the automods directory with the instructions from DBone-Unraid, we do the following:

I can't help here because I simply never done it like that. I can only try if it's the same with the Linux directory if I also have a space at the end.

Please also keep in mind that the path /mnt/cache/appdata/... is not done by accident and you also should use /mnt/cache/appdata/... instead of /mnt/user/appdata/... <- some games won't run on that path because it's a FUSE file path and it is set to /mnt/cache/appdata/... to avoid other weird behavior (please also make sure that you've set your appdata share in the Share settings to Use Cache "Only" or "Prefer".

 

7 hours ago, devnet said:

@ich777 where is that path set?  Do you think if I rename it and remove the space and correct all the paths it will start working or will it pull down a fresh copy with the space if it's set by Steam?  Is this a bug?

This path is set by the developers and nothing I can do about.

Basically this container will do the same as you run the dedicated server on bare metal and install everything by hand but everything is automated.

Hi @ich777,

 

Does your MinecraftBasicServer docker container allow a BungeeCord proxy and multiple child servers tied to it? I'm not sure if this is a single-server setup or it allows a network as well.

 

Thank you!

44 minutes ago, robertpaolella said:

Does your MinecraftBasicServer docker container allow a BungeeCord proxy and multiple child servers tied to it? I'm not sure if this is a single-server setup or it allows a network as well.

Sorry I'm not into modding Minecraft whatsoever, you can try.

 

You can usa a complete custom startup command, you can use your own specific Minecraft versions and so on.

I think it should be possible but as said, not really into modding Minecraft.

2 minutes ago, ich777 said:

Sorry I'm not into modding Minecraft whatsoever, you can try.

 

You can usa a complete custom startup command, you can use your own specific Minecraft versions and so on.

I think it should be possible but as said, not really into modding Minecraft.

 

No problem! The only real requirement for the docker container is the ability to run multiple servers at once. Do you know if that is possible?

1 minute ago, robertpaolella said:

No problem! The only real requirement for the docker container is the ability to run multiple servers at once. Do you know if that is possible?

Why is that needed? You can run multiple containers each with it's own server and link the networks together that it seems to the containers that they are running on one machen, hope that makes sense.

 

This is basically the same as if you route the traffic from a container through another VPN container.

On 1/7/2023 at 7:38 PM, devnet said:

BTW,

 

I was unable to mount to the path for engineapps...Error message was as follows:

 

Error response from daemon: invalid volume specification: '/mnt/smbcache/appdata/ark-se/steamapps/: /serverdata/serverfiles/Engine/Binaries/ThirdParty/SteamCMD/Linux/steamapps :rw': invalid mount config for type "bind": invalid mount path: ' /serverdata/serverfiles/Engine/Binaries/ThirdParty/SteamCMD/Linux/steamapps ' mount path must be absolute

 

 

Here's the issue once I connected to the docker console:

 

#

# ls
'Linux '   Win64
# cd Linux
sh: 7: cd: can't cd to Linux
# cd 'Linux '
# pwd
/serverdata/serverfiles/Engine/Binaries/ThirdParty/SteamCMD/Linux 
# ls -lrt
total 4
-rwxrwx--- 1 steam users 1212 Oct  6  2021 steamcmd.sh
drwxrwx--- 1 steam users   14 Nov 25 16:23 siteserverui
drwxrwx--- 1 steam users 1690 Nov 25 16:23 public
drwxrwx--- 1 steam users   28 Dec  2 18:42 linux64
drwxrwx--- 1 steam users  224 Dec  2 18:42 linux32
drwxrwx--- 1 steam users  728 Jan  7 20:32 package
# 

 

So it seems there is a space in the name for this path.  This prevents the volume from being mounted as the volume path has to be absolute.

 

Not sure where the name Linux is set nor by what or how but it will change how we have to map the volume.

 

/mnt/YOURCACHE/appdata/ark-se/steamapps/ will now have to be mapped to /serverdata/serverfiles/Engine/Binaries/ThirdParty/SteamCMD/Linux /steamapps

 

@devnet When you did the mappings for the engineapps, did you accidentally include a space after Linux?

The container path should be:  /serverdata/serverfiles/Engine/Binaries/ThirdParty/SteamCMD/Linux/steamapps

 

From what I can tell that is the only place where the space could have been added that would cause this issue.

23 hours ago, devnet said:

I think this has to do with the extra space that I found previously in the path for the 'Linux ' directory.  If we mount the automods directory with the instructions from DBone-Unraid, we do the following:

 

 

But that of course, doesn't exist...because the last part is 'Linux ' with the extra space on the end and that's not what is mounted...so we're installing or looking inside a different directory or one that doesn't exist.

 

@ich777 where is that path set?  Do you think if I rename it and remove the space and correct all the paths it will start working or will it pull down a fresh copy with the space if it's set by Steam?  Is this a bug?

@devnet can you check your path setup to make sure there isn't a space at the end of the container path?

Apologies if this has been worked out in another post, I have spent several hours redoing the process differently and reading a large portion of this topic but have no luck in getting a Valheim server up in Unraid.

 

I am running Unraid 6.11.5 and everything is up-to-date.

I have also forwarded the ports to my Unraid Server IP

 

Config:

 

Router:

 

Log:

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
---Update Server---
Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1669935972
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
Success! App '896660' already up to date.
---Prepare Server---
---BepInEx for Valheim enabled!---
---BepInEx for Valheim Version Check---

---https://valheim.thunderstore.io/package/denikson/BepInExPack_Valheim/---

---BepInEx v5.4.1901 up-to-date---
---Server ready---
---Starting Backup daemon---
---Update check deprecated!---
---Start Server---
---with BepInEx for Valheim---

---https://valheim.thunderstore.io/package/denikson/BepInExPack_Valheim/---

[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 1 milliseconds to initialize
Setting breakpad minidump AppID = 892970
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils003 before SteamAPI_Init succeeded.

 

The server simply doesn't show up in the list ever, nor can I connect to it locally. What am I missing?

Edited January 10, 20233 yr by kjpolker
Duplicate image

1 hour ago, DBone-Unraid said:

@devnet can you check your path setup to make sure there isn't a space at the end of the container path?

 

There definitely is...because inside the container, the directory is 'Linux '

 

root@86753OHNeeeeeyeeeine:/serverdata/serverfiles/Engine/Binaries/ThirdParty/SteamCMD# ls -lrt
total 0
drwxrwx--- 1 steam users  24 Jan  9 15:05  Win64
drwxrwx--- 1 steam users 118 Jan  9 18:48 'Linux '

 

 

Tested something on this...renamed my /mnt/cache/steamcmd folder and then edited my container to remove the spaces.  This time around I get 3 directories in that path:

 

root@86753OHNeeeeeyeeeine:/serverdata/serverfiles/Engine/Binaries/ThirdParty/SteamCMD# ls -lrt
total 0
drwxrwx--- 1 steam users   0 Jan  9 12:19 'Linux '
drwxrwx--- 1 steam users  24 Jan  9 15:05  Win64
drwxrwx--- 1 steam users 118 Jan  9 19:01  Linux

 

Edited January 10, 20233 yr by devnet

Just as an FYI...I changed all my /mnt/user paths to /mnt/cache...I then deleted everything to start fresh.  I was able to manually load the plugins by copying them over from my Windows Steam client after hosting a local game with the plugins I wanted enabled.  To do that, I had to subscribe to the plugins in the Steam workshop and then enable them when hosting the local game.  Then I did 'Manage' on the game in my steam library and was able to browse the file location, grab the mods, and copy them to the container.

 

Still can't do -automanage....it just causes an infinite reboot loop.

Edited January 9, 20233 yr by devnet

2 hours ago, devnet said:

Just as an FYI...I changed all my /mnt/user paths to /mnt/cache...I then deleted everything to start fresh.  I was able to manually load the plugins by copying them over from my Windows Steam client after hosting a local game with the plugins I wanted enabled.  To do that, I had to subscribe to the plugins in the Steam workshop and then enable them when hosting the local game.  Then I did 'Manage' on the game in my steam library and was able to browse the file location, grab the mods, and copy them to the container.

 

Still can't do -automanage....it just causes an infinite reboot loop.

 

Good call on changing to /mnt/cache, I didn't even notice one of my paths was setup that way until it was pointed out in a previous post, thank you @ich777 & @devnet.

I cannot say that I have ever run into the loop issue you are having.  Just a little bit ago a started a brand new server from scratch installing it to a completely new folder for both the server files and steamcmd.  I put in all the custom path mappings making sure to modify them to my new paths for the new server and steamcmd directories and used the same exact settings in my Game Parameters and Extra Game Parameters including the -automanagedmods flag.  Here is what I have for my "Extra Game Parameters": 

-server -log -automanagedmods -NoBattlEye -crossplay

 

If it still gives you the loop, then take the -automanagedmods and then continue on as follows.

 

After the docker template is setup, let the docker launch so that it can download all the files and start the server.  The first run you will not have any mods because the GameUserSettings.ini file will be generated upon the first startup.

 

Once the server starts up, I check to make sure it shows up in the server browser in game.  You will note that the column "W/Mods" will be blank at this time. 

 

Then stop the server and edit your GameUserSettings.ini file adding the ActiveMods= along with all the mods you want separated by a comma.

 

Launch the server now and give it some time to download the mods.  You should be able to open the logs of the docker while it is running and see messages like "Downloading item 1999447172 ..." for each mod you have listed in your GameUserSettings.ini file.

 

I'm wondering if one of your other custom paths still has an extra space after Linux. 

After the new server was setup I checked my directory and this is what I have:

/serverdata/serverfiles/Engine/Binaries/ThirdParty/SteamCMD# ls -lrt
total 0
drwxrwx--- 1 steam users  24 Jan  9 17:14 Win64
drwxrwx--- 1 steam users 118 Jan  9 20:21 Linux

 

After booting the server with mods, check this folder from the console of the docker to see if you have the "workshop" folder. 

/serverdata/serverfiles/Engine/Binaries/ThirdParty/SteamCMD/Linux/steamapps# ls -lrt
total 8
-rwxrwxrwx 1 steam users 220 Jan  9 20:21 libraryfolders.vdf
drwxrwx--- 1 steam users  84 Jan  9 20:21 workshop

 

If the workshop folder is not being created in the "Linux" no space directory but is going into the "Linux " with the space directory then there is most likely an extra space somewhere in one of the custom path configurations.

 

7 hours ago, ich777 said:

Why is that needed? You can run multiple containers each with it's own server and link the networks together that it seems to the containers that they are running on one machen, hope that makes sense.

 

This is basically the same as if you route the traffic from a container through another VPN container.

Okay, glad to know that's how it needs to be setup. How do I get a second container running?

10 hours ago, kjpolker said:

Apologies if this has been worked out in another post, I have spent several hours redoing the process differently and reading a large portion of this topic but have no luck in getting a Valheim server up in Unraid.

 

I am running Unraid 6.11.5 and everything is up-to-date.

I have also forwarded the ports to my Unraid Server IP

 

Config:

 

Router:

 

Log:

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
---Update Server---
Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1669935972
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
Success! App '896660' already up to date.
---Prepare Server---
---BepInEx for Valheim enabled!---
---BepInEx for Valheim Version Check---

---https://valheim.thunderstore.io/package/denikson/BepInExPack_Valheim/---

---BepInEx v5.4.1901 up-to-date---
---Server ready---
---Starting Backup daemon---
---Update check deprecated!---
---Start Server---
---with BepInEx for Valheim---

---https://valheim.thunderstore.io/package/denikson/BepInExPack_Valheim/---

[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 1 milliseconds to initialize
Setting breakpad minidump AppID = 892970
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils003 before SteamAPI_Init succeeded.

 

The server simply doesn't show up in the list ever, nor can I connect to it locally. What am I missing?

I just have same problem... it's a fresh container from ich's repo