[[Support] ich777 - Gameserver Dockers]

Ich777: Thank you!

 

Just aborted my long overdue bedtime, picked myself by the neck and dragged me back to my office for a bit of late night patching. Long story short; Now running 6.9.2, 7d2d launches like it should, VMs running well, and threw in the latest PfSense update while at it. All good!

 

I'd replace heartbleed with 'sleep deprevation on christmas eve' any day:)

 

Happy holidays guys, stay safe and enjoy yourselves!

[[Support] ich777 - Gameserver Dockers]

Thanks for your valuable inputs, Ich777!

Since posting I've tried making another 7dtd docker, pulled down the dedicated server files through regular desktop steam on my main computer, and copied all the files into the new container directory. Probably not the correct way to handle this issue, and certainly not working out as i hoped.

 

Launching either container (original or the new) leads to a new issue:

---Prepare Server---
---SaveGameFolder location correct---
---Savegame location found---
---UserDataFolder location correct---
---UserDataFolder location found---
---Server ready---
---Start Server---
Found path: /serverdata/serverfiles/7DaysToDieServer.x86_64
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.
Thread failed to initialize

[ 0%] Checking for available updates...
src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.
Thread failed to initialize

---Update Server---
---Validating installation---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.
Thread failed to initialize

[ 0%] Checking for available updates...
src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.
Thread failed to initialize

 

I've tried stopping all the Steam-related dockers I had running, hoping this would somehow release the "deadlock" to no avail.

 

Now I know my Unraid is getting dated (uptime 603 days, 5 hours and counting). But my issues here and not related to me running an older build of Unraid, is it?

 

 

Quote

Have you looked into the directory for the container if there are files in it? Is there a file called '7DaysToDieServer.x86_64' in the directory?

Yes, I have the file '7DaysToDieServer.x86_64' in the docker folder. Tried removing it and forcing a validation, but I guess this file was originally added by me manually. Sorry, really cannot remember how this was all set up back in the day.

 

Quote

No, this can be ignored, SteamCMD added this message because of various reasons, however if you get this message I recommend you to upgrade the container, you are basically using a old version from the container that is outdated, have fixed this about two weeks ago.

 

According to the docker tab, the application is up to date. I did a force upgrade as well, but perhaps removing the docker all together and pulling it down again would somehow get a more recent release?(Sorry for my ignorance, but this has been 'set and forget' on my part, and it's been running so well that I've not even restarted my server in almost two years...)

[[Support] ich777 - Gameserver Dockers]

 Thanks for your effort on these containers, Ich777!

I am now in a pickle with my 7d2d server hosted on Unraid 6.6.6.
It's been a while since me and my friends have played on my hosted server, but we got a new urge to start fresh again now that 7d2d alpha 20 b238 went live. Usually I'd then just backup the current serverconfig.xml (to keep the settings for a future revisit), then change some details like the seed and servername and reboot the docker to have a new map created.

However, this time around it has proven rather difficult, and I'm now facing error messages in the docker log that I haven't experienced before. Here is an excerpt of what appears to be a continously reboot server docker:

[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1639697740
-- 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/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1639697740
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
[33;1mPlease use force_install_dir before logon!
[0mSuccess! App '294420' already up to date.
---Prepare Server---
---SaveGameFolder location correct---
---Savegame location found---
---UserDataFolder location correct---
---UserDataFolder location found---
---Server ready---
---Start Server---
Found path: /serverdata/serverfiles/7DaysToDieServer.x86_64
---Checking if UID: 99 matches user---
usermod: no changes
---Checking if GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---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 1639697740
-- 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/Steam/logs/stderr.txt'

 

This log is basically repeating endlessly.

 

As far as I can remember, 7d2d have had a history of being a bit picky with the serverconfig.xml between certain versions of the game, yet I cannot seem to find any templates for this release on the web. This makes me believe my serverconfig.xml may be alright after all, and that the problem is somewhere else. The log line "[33;1mPlease use force_install_dir before logon!" may be a hint, but I've no idea how to solve it on Unraid / inside a docker. At the same time; If it were a steamcmd-related problem causing 7d2d server not to run, I would expect other steam-game dockers to fail as well, but that is not the case. Valheim, for instance, works as it should.

 

Would love to get any input on where my problems may come from. If anyone also could provide me with a template of the serverconfig.xml for 7 days to die alpha 20 b238, that would be nice.

 

Oh and please don't just point me into the direction of that Discord-channel. I tried going there, but got lost in some account claim stuff that I also newer figured out how to solve (trying to avoid rabbit holes all together)

[[Support] Linuxserver.io - NZBHydra]

1 hour ago, blodfjert said:

Anyone care to help me?...

 

Did some additional research. Ended up removing the docker and the appdata folder, reinstalled it and tried setting it up from scratch.

Got the api working again by removing the "s" from the URL inside config -> downloaders, and changing the port from 8090 to 8080.

 

SSL seems to be the suspect, perhaps because of certificate fu**up?

[[Support] Linuxserver.io - NZBHydra]

Anyone care to help me?

I don't really know what has happened, but here goes:
hydra cannot get the "categories" from sabnzbdvpn. When tailing the nzbhydra.log, it says
"SSLError: [SSL: CERIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)"

 

Though it could be wrong API-key, so i generated a new one in both dockers, but to no avail.

It's also been so long since I first set this up, I cannot remember if I am supposed to put any certificates into certain folders or whatnot.

 

[[Support] binhex - SABnzbdVPN]

Enable privoxy in this docker, then point your other apps to it.

 

I'm sorry, but I need a bit more help.

Activated "Enable_Privoxy" in the sab docker. After that I tried to edit the Hydra docker, but found no options relevance, so I launched the Hydra gui and edited the config inside. Tried setting the "Socks" option to point to server-ip:8118. After saving the changes and restarting Hydra, gui will not load... Trying to sort it out through manually editing the settings.cfg inside the app-folder now.

How do I tell Hydra to use that vpn?

[[Support] binhex - SABnzbdVPN]

Hi there and thanks for the docker!

Got it up and running after fiddling about for a while.

 

Since the VPN is up, can it be utilized by other dockers/services on the same box? As a fixed connection for a docker or as a proxy for a virtual machine?