It was running fine for more than a month now. Problems started with the new patch 🤷‍♂️. Else than that i do not know what to say...

1 hour ago, MisterB said:

It was running fine for more than a month now. Problems started with the new patch 🤷‍♂️.

What patch, that was released just now?

 

1 hour ago, MisterB said:

Else than that i do not know what to say...

Maybe try to restart the container a few times in the next few hours and see if it picks up a update.

Can you please post the Docker log from the container?

8 hours ago, ich777 said:

Please read the description from the container, the container is self maintaining and checks for updates on every start/restart.

I just restarted my server and tried to pull the update and it didn't pull. I also tried the other suggestion of validation in the template from true to false then restarted the container than back to true and restarted. It's not pulling an update.  I don't have anything else on my network such as adblocking. All other docker containers are able to pull updates just fine but not Valheim.

 

Here is the log

 

text  error  warn  system  array  login  

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

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

Session terminated, killing shell... ...killed.
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 2 milliseconds to initialize
Setting breakpad minidump AppID = 892970
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils003 before SteamAPI_Init succeeded.
---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/serverfiles/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1675223179
-- type 'quit' to exit --
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/serverfiles/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1675223179
-- 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---
---Server ready---
---Starting Backup daemon---
---Update check deprecated!---
---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/serverfiles/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1675223179
-- type 'quit' to exit --
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/serverfiles/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1675223179
-- 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---
---Server ready---
---Starting Backup daemon---
---Update check deprecated!---
---Start Server---
 

13 minutes ago, Turb0x3r said:

Success! App '896660' already up to date.

This is really strange, I really can't tell what's going on on your system...

 

You should see something like this:

---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 1675223179
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
 Update state (0x61) downloading, progress: 26.89 (130149427 / 483958864)
 Update state (0x81) verifying update, progress: 43.52 (210629021 / 483958864)
Success! App '896660' fully installed.
---Prepare Server---

(this is actually my old Valheim server that I haven't updated yet)

 

After the update I've connected to it and it seems to work fine.

 

Can you post a screenshot from the template? Is the Data Path set to /mnt/cache/...?

If yes, do you have a cache drive installed in your server? If yes to what is the appdata share set in terms of Use Cache in the Share settings? Yes, No, Prefer or Only?

I do have a cache drive on the server. Appdata says "prefer cache"

 

Also one thing I've noticed in the docker template for Valheim is that I didn't put in the steamuser name and password. Should I add that in there?

 

 

21 minutes ago, Turb0x3r said:

Should I add that in there?

No, it has a reason why it‘s not shown by default.

 

Please try to pull another copy from the template from CA, change the name and the path to the game files and see if you can connect to that instance afterwards, of course you have to stop the current container before doing that.

15 minutes ago, ich777 said:

No, it has a reason why it‘s not shown by default.

 

Please try to pull another copy from the template from CA, change the name and the path to the game files and see if you can connect to that instance afterwards, of course you have to stop the current container before doing that.

It won't mess up the existing game? I have others on there and alot of hours being put on Valheim. Last time there was a major update the entire world was lost and i was unable to recover it. 

7 hours ago, ich777 said:

What patch, that was released just now?

 

Maybe try to restart the container a few times in the next few hours and see if it picks up a update.

Can you please post the Docker log from the container?

Here's what i get as LOG after restarting the container:

  

/serverdata/steamcmd/steamcmd.sh: line 39:    33 Segmentation fault      $DEBUGGER "$STEAMEXE" "$@"
/serverdata/steamcmd/steamcmd.sh: line 39:    39 Segmentation fault      $DEBUGGER "$STEAMEXE" "$@"
[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.
---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---
---Update Server---
---Validating installation---
---Prepare Server---
---Server ready---
---Starting Backup daemon---
---Update check deprecated!---
---Start Server---

Attempting to get a Core Keeper server running but it isn't starting. The server log shows this and no game ID seems to be created.

Preloaded 'lib_burst_generated.so'
Preloaded 'libsteam_api.so'
Unable to preload the following plugins:
    libsentry.so
Display 0 '0': 1x1 (primary device).
Loading player data from /serverdata/serverfiles/CoreKeeperServer_Data/data.unity3d
Unable to load player prefs
Desktop is 1 x 1 @ 0 Hz

14 hours ago, Turb0x3r said:

It won't mess up the existing game?

If you do it like I've mentioned above (edit the name from the container and the Data Dir), it won't mess up the existing container.

 

To save your world, you can also backup the "Backup" and/or the ".config" directory which lives in your main folder for Valheim in your appdata directory.

13 hours ago, MisterB said:

Here's what i get as LOG after restarting the container:

On what Unraid version are you?

 

I can't reproduce your issues here, I've now connected to my Valheim+ container (it is also working with the new patch version) and to my default Valheim container (without Valheim+).

18 hours ago, rocklord2004 said:

Attempting to get a Core Keeper server running but it isn't starting. The server log shows this and no game ID seems to be created.

I will look into this and report back.

 

@rocklord2004 please update the container itself and see if it is now working for you.

I attached a log from a successful start: CoreKeeper.log

3 minutes ago, ich777 said:

On what Unraid version are you?

6.11.5

4 minutes ago, MisterB said:

6.11.5

Please do the following I've recommended here and see if the new instance is working:

 

This won't mess up your existing container as long as you change the Container name and Data Dir path where the game files are, of course as said, you have to stop the not working container first.

On 2/6/2023 at 11:53 PM, ich777 said:

You can also go through my start script from the container what it does and port it over to your installation and it should hopefully start and run just fine.

 

Completely understood.

I used to also run everything in a VM, but now I have only two, one for compiling plugins for VM when a new Unraid version drops and one for testing that is basically never running.

 

Currently there are 28 Docker containers (without game servers) and 3 LXC containers running to keep everything up and at my home...

 

Please also let me know if it is working with a native installation.

Hey @ich777  I'm back from a couple days ago and wanted to commend you for being such a saint and responding to everyone all the time

 

I know you were curious, so turns out, the native installation on CentOS with Wine ended up with the same exact issue.  I ended up upgrading the Xigmanas (main FreeBSD Server that hosts the CentOS VM) and that made everything start working, both the native install AND your docker.   I guess technically the OS version and various packages in FreeBSD were a couple years old, so it really does go back to your original question "is your distribution up to date".

 

Thanks again for the help and i should have tried upgrading all the distros in the first place, my bad!

 

12 hours ago, ich777 said:

I will look into this and report back.

 

@rocklord2004 please update the container itself and see if it is now working for you.

I attached a log from a successful start: CoreKeeper.log

Whatever you did fixed it. Thanks a ton!

13 hours ago, ich777 said:

Please do the following I've recommended here and see if the new instance is working:

 

This won't mess up your existing container as long as you change the Container name and Data Dir path where the game files are, of course as said, you have to stop the not working container first.

It didn't worked... i simply kept a copy of my maps, deleted everything and started everything over... It's working now. Thanks for the help

I've got something weird. All my server doesn'T show anymore in any game list except those that list lan. Nothing changed for the past months. I tried rebooting server, firewall, redoing port forwarding, nothing. Same problem on Valheim, Ark, conan Exiled, V Rising.... Really weird.

 

I did try to setup steam-healess the last week, but it had it's own folder to not touch steamcmd or any other folder. I also played a bit with debian in docker but still shouldn't affect the other docker. Currently on 6.11.5

 

edit: I found out that when they are trying to start steamcmd, they get this error:

 

Quote

 

  0%] Checking for available update...
KeyValues Error: LoadFromBuffer: missing {   (current key: '<!DOCTYPE') in file manifest [offset: 15]

../tier1/KeyValues.cpp (2925) : Assertion Failed: Error while parsing text KeyValues for resource manifest
[----] Verifying installation...
[  0%] Downloading Update...
[  0%] Checking for available update...
KeyValues Error: LoadFromBuffer: missing {   (current key: '<!DOCTYPE') in file manifest [offset: 15]

../tier1/KeyValues.cpp (2925) : Assertion Failed: Error while parsing text KeyValues for resource manifest
[----] !!! Fatal Error: Steamcmd needs to be online to update.   Please confirm your network connection and try again.
CWorkThreadPool::~CWorkThreadPool: work complete queue not empty, 1 items discarded.
threadtools.cpp (3294) : Assertion Failed: Illegal termination of worker thread 'Thread(0x0x56a82320/0x0x2a185b'

 

 

I tried to ping google from the container and it worked

Edited February 10, 20233 yr by Nodiaque

42 minutes ago, Nodiaque said:

KeyValues Error: LoadFromBuffer: missing {   (current key: '<!DOCTYPE') in file manifest [offset: 15]

This is usually a indicator that SteamCMD can‘t connect with Steam Pipe.

Are you sure that nothing on your network changed?

maybe try to stop all game server containers and delete the contents of the steamcmd folder (including hidden files) and then start one container so that it can pull SteamCMD.

14 hours ago, ich777 said:

This is usually a indicator that SteamCMD can‘t connect with Steam Pipe.

Are you sure that nothing on your network changed?

maybe try to stop all game server containers and delete the contents of the steamcmd folder (including hidden files) and then start one container so that it can pull SteamCMD.

Thats what I tried, I renamed the folder so it created a new one. It was downloaded and now I get this message. Very weird. Only thing that happen is a power outage maybe a week ago (but all server gracefully shutdown due to ups). Very weird.

 

edit: I also found out that my conan exile server is identified as invalid. Ark server are showned in lan only and working, Valheim server are nowhere to be found. O_O

 

re-edit: I just tried disabling unbounb and pihole (just incase something went wrong in the past week) and it didn't solved it

 

edit again!

I just compared both steamcmd and the backup, normal they have different files?

 

edit back: yeah it's normal since it doesn't download.... I don't get why it doesn't download

 

Edit yet again: I just tried to create a new conan server, new steamcmd folder, new basedir and I connected it to bridge (just wanted to see if it would download). Ended with the same error + error saying conansandbox folder doesn't exist (since steam couldn't run). I'm really out of clues :(

 

More edit: I have 2 unraid installation, just tried on the other unraid and everything is fine... What config could do that on my unraid? They are using same DNS, DHCP and router

 

so much edit: I just tried this container

https://hub.docker.com/r/cm2network/steamcmd/

 

and steamcmd.sh start and download steam O_O

Edited February 10, 20233 yr by Nodiaque

6 hours ago, Nodiaque said:

Thats what I tried, I renamed the folder so it created a new one. It was downloaded and now I get this message. Very weird. Only thing that happen is a power outage maybe a week ago (but all server gracefully shutdown due to ups). Very weird.

Sorry but all my game servers that I've running are working fine, I can only think of a corruption of the Docker images itself.

I have never seen this issue before...

 

You are on 6.11.5 I assume correct?

 

Please try to delete all containers (so that no SteamCMD container from me is on your server anymore) and then add it again with the button Add Container on the Docker page and selecting the appropriate containers again from the drop down, with this you make sure that your paths and everything is set as before.

2 minutes ago, ich777 said:

Sorry but all my game servers that I've running are working fine, I can only think of a corruption of the Docker images itself.

I have never seen this issue before...

 

You are on 6.11.5 I assume correct?

 

Please try to delete all containers (so that no SteamCMD container from me is on your server anymore) and then add it again with the button Add Container on the Docker page and selecting the appropriate containers again from the drop down, with this you make sure that your paths and everything is set as before.

That'S what I'm thinking right now. Since it's working on my other instance of unraid and it's also working from someone else steamcmd docker I found and try. Delete time. At least, it's less painfull then redoing docker.img

didn'T worked I deleted all image that were from you, when I downloaded ark back it downloaded all layers. And when it started, same problem

 

edit: yup 6.11.5

Edited February 10, 20233 yr by Nodiaque

3 minutes ago, Nodiaque said:

didn'T worked I deleted all image that were from you, when I downloaded ark back it downloaded all layers. And when it started, same problem

Do you have anything custom on your system like many packages from NerdTools or similar?

 

I really can't tell what's going on on your machine, have you yet tried to reboot your entire server?

 

11 minutes ago, Nodiaque said:

At least, it's less painfull then redoing docker.img

Why are you using a docker.img? I would strongly recommend to use a directory instead of a image file.

6 minutes ago, ich777 said:

Do you have anything custom on your system like many packages from NerdTools or similar?

 

I really can't tell what's going on on your machine, have you yet tried to reboot your entire server?

 

Why are you using a docker.img? I would strongly recommend to use a directory instead of a image file.

docker.img simply because it was the default setting when I started using unraid years ago. And since it was all new to me, I didn't wanted to modify to much stuff.

 

rebooted server and router.

 

nerdtool only have tmux and unrar package installed