1 minute ago, Blacklistgames said:

Yes my appdata is so by adding disk1 should this resolve the problem?

This should resolve the issue.

11 minutes ago, ich777 said:

This should resolve the issue.

 

Still Getting the same error i have checked all other disks dont see any of the files/folders in them only on disk1. at one point it asked for the token so i added it and then now its showing.

 

setrlimit: Operation not permitted
Warning: core dumps may be truncated or non-existent
[00:00:00]: PersistRootStorage is now /serverdata/.klei//DoNotStarveTogether/Cluster_1/Master/ 
[00:00:00]: Starting Up
[00:00:00]: Version: 490729
[00:00:00]: Current time: Fri Dec 31 17:18:46 2021

[00:00:00]: System Name: Linux
[00:00:00]: Host Name: 3c1646661e9d
[00:00:00]: Release(Kernel) Version: 5.10.28-Unraid
[00:00:00]: Kernel Build Timestamp: #1 SMP Wed Apr 7 08:23:18 PDT 2021
[00:00:00]: Machine Arch: x86_64
[00:00:00]: Don't Starve Together: 490729 LINUX
[00:00:00]: Build Date: 7543
[00:00:00]: Mode: 32-bit
[00:00:00]: Parsing command line
[00:00:00]: Command Line Arguments: -shard Master 
[00:00:00]: Initializing distribution platform
[00:00:00]: ....Done
[00:00:00]: THREAD - started 'GAClient' (694070080)
[00:00:00]: Mounting file system databundles/klump.zip skipped.
[00:00:00]: CurlRequestManager::ClientThread::Main()
[00:00:00]: Mounting file system databundles/shaders.zip skipped.
[00:00:00]: Mounting file system databundles/fonts.zip skipped.
[00:00:00]: Mounting file system databundles/anim_dynamic.zip skipped.
[00:00:00]: Mounting file system databundles/bigportraits.zip skipped.
[00:00:00]: Mounting file system databundles/images.zip skipped.
[00:00:00]: Mounting file system databundles/scripts.zip skipped.
[00:00:00]: [Steam] SteamGameServer_Init(10890, 27016)
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 4 milliseconds to initialize
CApplicationManagerPopulateThread took 0 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
RecordSteamInterfaceCreation (PID 65): SteamGameServer013 / 
RecordSteamInterfaceCreation (PID 65): SteamUtils010 / 
CreateBoundSocket: ::bind couldn't find an open port between 27016 and 27016
[00:00:00]: [Steam] SteamGameServer_Init(10890, 27017)
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
RecordSteamInterfaceCreation (PID 65): SteamGameServer013 / 
RecordSteamInterfaceCreation (PID 65): SteamUtils010 / 
Setting breakpad minidump AppID = 322330
[00:00:00]: [Steam] SteamGameServer_Init success
RecordSteamInterfaceCreation (PID 65): SteamGameServer013 / 
RecordSteamInterfaceCreation (PID 65): STEAMUGC_INTERFACE_VERSION015 / 
[00:00:00]: ProfileIndex:5.13
[00:00:00]: [Connect] PendingConnection::Reset(true)
[00:00:00]: THREAD - started 'Ping Job Thread' (637524800)
[00:00:00]: Platform: 1
[00:00:00]: Network tick rate: U=15(2), D=0
[00:00:00]: Network tick rate: U=15(2), D=0
[00:00:00]: OnLoadPermissionList: /serverdata/.klei//DoNotStarveTogether/Cluster_1/blocklist.txt (Failure)
[00:00:00]: THREAD - started 'StreamInput' (633338688)
[00:00:00]: OnLoadPermissionList: /serverdata/.klei//DoNotStarveTogether/Cluster_1/adminlist.txt (Success)
[00:00:00]: Error string decoding Steam Net ID
[00:00:00]: OnLoadUserIdList: /serverdata/.klei//DoNotStarveTogether/Cluster_1/whitelist.txt (Failure)
[00:00:00]: Token retrieved from: /serverdata/.klei//DoNotStarveTogether/Cluster_1/cluster_token.txt
[00:00:00]: Token retrieved from: /serverdata/.klei//DoNotStarveTogether/Cluster_1/cluster_token.txt
[00:00:00]: cGame::InitializeOnMainThread
[00:00:00]: Renderer initialize: Okay
[00:00:00]: AnimManager initialize: Okay
[00:00:00]: Buffers initialize: Okay
[00:00:00]: cDontStarveGame::DoGameSpecificInitialize()
[00:00:00]: GameSpecific initialize: Okay
[00:00:00]: cGame::StartPlaying
[00:00:00]: AppVersion::GetArchitecture() x32
[00:00:00]: LOADING LUA
[00:00:00]: DoLuaFile scripts/main.lua
[00:00:00]: DoLuaFile Could not load lua file scripts/main.lua
[00:00:00]: Error loading main.lua
[00:00:00]: Failed mSimulation->Reset()
[00:00:00]: Error during game initialization!
Updates 0Seconds elapsed: 0.139476 fps:0
Saving Dedicated server data...
[00:00:00]: attempt to call a nil value
LUA ERROR stack traceback:
[00:00:00]: attempt to call a nil value
LUA ERROR stack traceback:
[00:00:00]: Collecting garbage...
[00:00:00]: lua_gc took 0.00 seconds
[00:00:00]: ~ShardLuaProxy()
[00:00:00]: ~cEventLeaderboardProxy()
[00:00:00]: ~ItemServerLuaProxy()
[00:00:00]: ~InventoryLuaProxy()
[00:00:00]: ~NetworkLuaProxy()
[00:00:00]: ~SimLuaProxy()
[00:00:00]: lua_close took 0.00 seconds
[00:00:00]: Orphaned unnamed resource. This resource must have used Add( resource ) to insert itself into the manager. 
[00:00:00]: CurlRequestManager::ClientThread::Main() complete
[00:00:00]: HttpClient2 discarded 0 callbacks.
[00:00:00]: Shutting down
src/tier1/fileio.cpp (4914) : Assertion Failed: s_bExit
src/tier1/fileio.cpp (4914) : Assertion Failed: s_bExit
src/tier1/fileio.cpp (4916) : Assertion Failed: m_vecRegisteredWriters.Count() == 0
src/tier1/fileio.cpp (4916) : Assertion Failed: m_vecRegisteredWriters.Count() == 0
 

1 hour ago, ich777 said:

I also now tried and have no issue whatsoever, do you run AdGuard or PiHole somewhere on your network?

It seems like something failed with the download of certain files. Are there any files in the '7dtd' folder?

 

Also here is the log from a newly installed instance on my server: 7dtd.log.txt

 

Please try to start over by deleting the container and the 7dtd folder that lives in your appdata directory and pull a fresh copy from the Container from the CA App.

No, it's a pretty vanilla Unraid setup, but this first part of the log (which acts very odd, overwriting itself and not clearing from previous attempts) and it has an error right away: "deadlock "?:

---
---Checking if UID: 99 matches user---
---Checking if GID: 100 matches user---
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.
[ 0%] Checking for available updates...
Thread failed to initialize
src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.
Thread failed to initialize
---Update Server---
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
---

On 8/18/2021 at 10:22 PM, ich777 said:

Stock ARMA 3 server?

Will look into this tomorrow, getting pretty late here.

 

Heya!

 

I wanted to ask if this was ever looked into. Went back a few pages to look for any more info but didn't find anything, so I wanted to ask about it again. I may have missed it though, in which case I hope you can point me to it! 

On 12/30/2021 at 2:01 AM, ich777 said:

Can you post the log from the container?

 

Have you yet tried to enter the IP in ProjectZomboid? You can also try to search for it in the Seam Server Browser by clicking on Favourites, Add Server enter the IP and Port (eg: IP:PORT).

Heres the logs, I restarted the container and waited for it to print "SEVER STARTED"

31-12-21_14-22-17_DebugLog-server.txt

2 hours ago, HenPo said:

Heres the logs, I restarted the container and waited for it to print "SEVER STARTED"

31-12-21_14-22-17_DebugLog-server.txt 107.94 kB · 0 downloads

Looks fine from what I see.

Have you tried to connect through your local IP too?

12 minutes ago, ich777 said:

Looks fine from what I see.

Have you tried to connect through your local IP too?

The fixed IP I was using was already in use haha. That solved the issue for me. I was also wondering if you had any guides on installing mods onto this container.

17 hours ago, ich777 said:

Please double check once more if the protocol and the ports are correct.

 

Are you trying from your local network to reach the server? Maybe try it from outside.

Have you already tried your public IP.

 

Another issue could be that you ISP blocks some ports by default.

 

If you can join locally it's most likely a network issue, as said above maybe your ISP blocks some ports by default without you knowing another thing could be that maybe NAT reflection is not working properly.

 

Thanks for your help with trouble shooting, turns out my public IP worked from outside my network which i guess means NAT reflection is not working properly? Not so much of an issue.

 

However, my domain is still not working when the public IP is working, i can confirm that my DNS provider does have my correct IP and other services are working. Do you know if satisfactory just can't resolve domain names?

7 hours ago, HenPo said:

I was also wondering if you had any guides on installing mods onto this container.

Not really, because I only create the basic dedicated server, but it shouldn't be different from installing mods to a dedicated server on bare metal.

8 hours ago, wolfenheim said:

Nturns out my public IP worked from outside my network which i guess means NAT reflection is not working properly?

Exactly.

 

8 hours ago, wolfenheim said:

Do you know if satisfactory just can't resolve domain names?

From what I know Satisfavtory should be able to resolve domain names but you have to only enter the domain name like: domain.org or if you are using DuckDNS: domain.duckdns.org

 

I will test this today if Satisfactory can resolfe domain names and report back.

 

EDIT: No issue here, Satisfactory is able to resolve DNS names.

In my case it resolved my domain name (m******.*t) just fine and I can connect to the server (tested with the experimental branch, but this should not be different to the EarlyAccess branch).

 

My testing methodology was as follows:

1. Downloaded a fresh copy from the server from the CA App
2. Forward the ports 7777, 15777, 15000 (all UDP) in my firewall
3. Disconnected the LAN connection from my PC
4. Created a WLAN HotSpot with my mobile phone
5. Connected my PC to the HotSpot
6. Started the game and entered my domain name in the Server Manager
7. Connect, create a server and join the server

 

All of the above steps worked flawlessly.

13 hours ago, Shooterism said:

 

Heya!

 

I wanted to ask if this was ever looked into. Went back a few pages to look for any more info but didn't find anything, so I wanted to ask about it again. I may have missed it though, in which case I hope you can point me to it! 

 

I realise that I probably should have provided more details. Installed the Arma 3 stock container and let it run, everything downloads as expected but the console, upon trying to run the start-server.sh script, produces the following error still:

Quote

[0mSuccess! App '233780' already up to date.
---Prepare Server---
---server.cfg found...
---Start Server---
12:37:29 Could not enable linux core dumps. Error 1 - �
/opt/scripts/start-server.sh: line 54: 71 Segmentation fault ./arma3server ${GAME_PARAMS}

 

No modifications were made to the container variables and parameters outside of what is required.

Any more insight on this error issue with the 7 Days to Die container deployment:

"src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize."

It's obviously a rare issue, but a couple of people running Unraid have ran into it, more importantly, on Satisfactory, not 7DTD, so it might be some broader issue.

A friend suggested it might have to do with the optional Steam login fields, but are those ever relevant?

4 minutes ago, DockerBubba said:

It's obviously a rare issue, but a couple of people running Unraid have ran into it, more importantly, on Satisfactory, not 7DTD, so it might be some broader issue.

Can you point me to this threads/posts where people run into this?

 

With Satisfactory it's a completely different story because this is related to older AMD CPUs who doesn't support some instructions that are necessary on for example the experimental branch.

 

7 minutes ago, DockerBubba said:

A friend suggested it might have to do with the optional Steam login fields, but are those ever relevant?

Why should this be related?

Delete them if you want to but that won't change anything and will make bo difference at all.

 

Have you yet tried to reinstall the container (delete the container, delete the 7dtd folder and pull a fresh copy from the CA App)?

Also don't forget to set your appdata share to use cache "Only" or "Prefer".

 

As said above the container works fine and also on many other systems, this is the first time that I hear about that error on unRAID, maybe @Spectral Force heard of that but I don't think so...

5 hours ago, Shooterism said:

No modifications were made to the container variables and parameters outside of what is required.

I will look into this as soon as possible and report back if it installs on my server or not.

48 minutes ago, ich777 said:

Can you point me to this threads/posts where people run into this?

 

With Satisfactory it's a completely different story because this is related to older AMD CPUs who doesn't support some instructions that are necessary on for example the experimental branch.

 

Why should this be related?

Delete them if you want to but that won't change anything and will make bo difference at all.

 

Have you yet tried to reinstall the container (delete the container, delete the 7dtd folder and pull a fresh copy from the CA App)?

Also don't forget to set your appdata share to use cache "Only" or "Prefer".

 

As said above the container works fine and also on many other systems, this is the first time that I hear about that error on unRAID, maybe @Spectral Force heard of that but I don't think so...

Yes, the first thing I did was delete the container, delete the /7dtd directory and it made no difference.

 

By the sounds of it, it's a steamcmd problem, not necessarily related to your 7dtd container.  With that in mind, if I shut-down the other Steam-centric containers, can I delete the steamcmd directories and try to re-install 7dtd from scratch?  Will that effect the other game servers that use steamcmd?
 

Waay at the bottom of this thread is where I found a reference to the exact issue:

 

https://githubmate.com/repo/MitchTalmadge/AMP-dockerized/issues/94

1 minute ago, DockerBubba said:

With that in mind, if I shut-down the other Steam-centric containers, can I delete the steamcmd directories and try to re-install 7dtd from scratch? 

You don't have to shutdown the other containers.

SteamCMD is only used/updated when a container is started/restarted.

 

2 minutes ago, DockerBubba said:

Waay at the bottom of this thread is where I found a reference to the exact issue

There is something wrong on the system itself it seems to me if you get this error.

On what hardware/unRAID version are you running the game servers?

 

Have you double checked that all files are on one disk and not spread across multiple disks?

38 minutes ago, ich777 said:

You don't have to shutdown the other containers.

SteamCMD is only used/updated when a container is started/restarted.

 

There is something wrong on the system itself it seems to me if you get this error.

On what hardware/unRAID version are you running the game servers?

 

Have you double checked that all files are on one disk and not spread across multiple disks?

There's only one drive attached to the system!

I'll fire-up the other steam-centric containers again and then delete /steamcmd and re-try 7DTD.

15 minutes ago, DockerBubba said:

There's only one drive attached to the system!

Have you changed the path to the appropriate disk in the template?

 

15 minutes ago, DockerBubba said:

I'll fire-up the other steam-centric containers again and then delete /steamcmd and re-try 7DTD.

As said above SteamCMD is only called when the container is started so you can do whatever you want when all containers are fully started or stopped.

1 hour ago, ich777 said:

Have you changed the path to the appropriate disk in the template?

 

As said above SteamCMD is only called when the container is started so you can do whatever you want when all containers are fully started or stopped.

When you choose and run the 7DTD container from Community Applications (using defaults), it DOES manage to make three empty directories, where you would expect them to be, so I don't think it's any kind of disk access issue.

Getting an issue with my Valheim servers: /opt/scripts/start-server.sh: line 240: /serverdata/serverfiles/valheim_server.x86_64: No such file or directory

I have cleared all appdata directories and SteamCMD, as well as redownloading the container from CA and still get this after it finishes downloading and tries to start.

Eventually it'll throw this error: src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.

My SteamCMD path is correct in the config, as well as the ServerFiles. 

 

This started a couple weeks ago with servers that were previously working.

 

Any thoughts?

OK, I have no idea why a 7DTD update would cause so much grief!

Now it seems that the 7DTD process has filled-up the Docker image itself, which should be impossible, no?  The Docker volume and log were at 100%, so I did a purge and rebooted, but now the very first line in the log is:

"/tmp/dumps insufficient permissions - delete and recreate"

1 hour ago, stryder said:

Getting an issue with my Valheim servers: /opt/scripts/start-server.sh: line 240: /serverdata/serverfiles/valheim_server.x86_64: No such file or directory

I have cleared all appdata directories and SteamCMD, as well as redownloading the container from CA and still get this after it finishes downloading and tries to start.

Eventually it'll throw this error: src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.

My SteamCMD path is correct in the config, as well as the ServerFiles. 

 

This started a couple weeks ago with servers that were previously working.

 

Any thoughts?

This is EXACTLY what is happening to me...  There has been some kind of recent change in either Unraid, docker or maybe the way the gameserver dockers work now.  It had been working flawlessly for more than a year now and its all gone to crap!

1 hour ago, stryder said:

Getting an issue with my Valheim servers: /opt/scripts/start-server.sh: line 240: /serverdata/serverfiles/valheim_server.x86_64: No such file or directory

I have cleared all appdata directories and SteamCMD, as well as redownloading the container from CA and still get this after it finishes downloading and tries to start.

Eventually it'll throw this error: src/tier0/threadtools.cpp (4085) : Probably deadlock or failure waiting for thread to initialize.

My SteamCMD path is correct in the config, as well as the ServerFiles. 

 

This started a couple weeks ago with servers that were previously working.

 

Any thoughts?

I am still on 6.8.3 I should point out, no changes to my shares or permissions. Tried to update after the recent patch posted by the Valheim devs and the image broke.

7 hours ago, DockerBubba said:

it DOES manage to make three empty directories

What? Where does it manage to create three empty directories?

It should only create two directories.

 

3 hours ago, DockerBubba said:

Now it seems that the 7DTD process has filled-up the Docker image itself

Then something is wrong with the directories.

Can you please post your Diagnostics and also screenshots from the template?

 

3 hours ago, DockerBubba said:

"/tmp/dumps insufficient permissions - delete and recreate"

Where did you get this error?

 

3 hours ago, DockerBubba said:

There has been some kind of recent change in either Unraid, docker or maybe the way the gameserver dockers work now. 

Nothing changed to unRAID if you are on the same version, can you please tell me which versiom from unRAID are you running as asked above (if you post the Diagnostics I'll see it too).

 

The 7DtD container got recently an update to support BepInEx amd it was confirmed by the user who requested it that it is working perfectly fine.

 

The only thing that maybe changed is SteamCMD.

 

Can you please post your Diagnostics so that I can see on what hardware amd so on you are running unRAID.

 

3 hours ago, DockerBubba said:

This is EXACTLY what is happening to me... 

You said your other containers that use SteamCMD are working fine or am I wrong?

5 hours ago, stryder said:

Getting an issue with my Valheim servers: /opt/scripts/start-server.sh: line 240: /serverdata/serverfiles/valheim_server.x86_64: No such file or directory

Can you verify that in the directory for Valheim is a file called 'valheim_server.x86_64'?

 

5 hours ago, stryder said:

This started a couple weeks ago with servers that were previously working.

Do you run any other game servers, if yes are they working?

 

4 hours ago, stryder said:

I am still on 6.8.3 I should point out

I would strongly recommend to upgrade to 6.9.2 because this can be the root cause for this issue.

 

Please also post your Diagnostics if the upgrade to 6.9.2 won't solve the issue.