mathomas3

Yes. I did include a screenshot inside the doc I shared along with the logs. Hmm. Your log and my own seem similar. The difference with my setup is that I changed the ports from 27015 to 27016. I also per your suggestion hard coded the 'serverfiles' path to disk 18

Thank you for the input. I went ahead and tried these settings but without luck. Logs indicate that it seems to load but I cant find the server in game or via the steam Game Server app. Im miffed as to what is going on. Please see the attached. dod.odt

So I cleaned everything out and used a different dir for the steamcmd and I got the following error If this is an issue with the CPU that I am using, Im confused due to CSSource is working fine, but if it matters I have two Intel® Xeon® CPU E5-2640 v4 @ 2.40GHz installed on this system " ---Prepare Server--- mkdir: cannot create directory ‘/serverdata/.steam/sdk32’: No such file or directory cp: target '/serverdata/.steam/sdk32/' is not a directory ---'server.cfg' found... ---Please wait--- ---Server ready--- ---Start Server--- Auto detecting CPU Using default binary: ./srcds_linux Server will auto-restart if there is a crash. Setting breakpad minidump AppID = 232290 Using breakpad crash handler dlopen failed trying to load: /serverdata/.steam/sdk32/steamclient.so with error: /serverdata/.steam/sdk32/steamclient.so: cannot open shared object file: No such file or directory Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit Segmentation fault Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem Sun 24 Mar 2024 03:17:41 PM CDT: Server restart in 10 seconds "

Spoke too soon. Noticed that the download has stopped and I checked the logs again and this is what I found. restarted the server with my Steam credentials and got the same. " Setting breakpad minidump AppID = 232290 Using breakpad crash handler dlopen failed trying to load: /serverdata/.steam/sdk32/steamclient.so with error: /serverdata/.steam/sdk32/steamclient.so: cannot open shared object file: No such file or directory Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit Segmentation fault Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem Sun 24 Mar 2024 03:01:20 PM CDT: Server restart in 10 seconds "

This seems to have done it for me. Is there a note in the docker that I missed? Currently the server is downloading. Thanks!

Hello, I am trying to get DODSource up and running but ran into a brick wall and no amount of googling has yielded anything helpful. Basically I have two errors - ERROR! Failed to install app '232290; (No subscription) - even bought the game for this dedicated account - Prepare Server--- No s'erver.cfg' found, downloading...--- Can't download 'server.cfg', putting server into sleep mode--- Any help would be welcome. Thanks Again, Mat mkdir: cannot create directory ‘/serverdata/.steam/sdk32’: No such file or directory cp: cannot stat '/serverdata/serverfiles/bin/*': No such file or directory /opt/scripts/start-server.sh: line 60: cd: /serverdata/serverfiles/dod/cfg: No such file or directory ---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--- tid(34) burning pthread_key_t == 0 so we never use it Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Logging directory: '/serverdata/Steam/logs' minidumps folder is set to /tmp/dumps [ 0%] Checking for available updates... [----] Verifying installation... UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1709846822 -- type 'quit' to exit -- Loading Steam API...OK Logging in user 'widomakr1' to Steam Public...OK Waiting for client config...OK Waiting for user info...OK ---Update Server--- ---Validating installation--- tid(58) burning pthread_key_t == 0 so we never use it Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Logging directory: '/serverdata/Steam/logs' minidumps folder is set to /tmp/dumps [ 0%] Checking for available updates... [----] Verifying installation... UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1709846822 -- type 'quit' to exit -- Loading Steam API...OK Logging in user 'widomakr1' to Steam Public...OK Waiting for client config...OK Waiting for user info...OK ERROR! Failed to install app '232290' (No subscription) ---Prepare Server--- ---No s'erver.cfg' found, downloading...--- ---Can't download 'server.cfg', putting server into sleep mode---

Anyone have a clue as to what to do?

Hello all, I have been for some time now trying to get direct access to the share via 9p mode without success. Reason being is that I would like to move docker management from unraid to VMs using protainer. The VMs that I am using are base on RH without a GUI. When using different methods that I have found to mount the share I would receive errors such as, need to use method to mount and or the OS would boot into emergency mode due to the share not mounting. I have spent a few days reading and searching but without making much progress... The one method that I found could work is to create a brand new NFS share for a single docker to get it to work... but that is a poor solution IMO... Please advise... Yes I know it's currently commented out... but that's the only way I could get the VM to boot

EXTENDED SMART reports are needed... for the two drives

I wouldnt do anything atm... your have 2 failed drives ATM and should anything go wrong... you are going to lose data... I would suggest stopping dockers and limit the disk activity others will be better to advise you... but you can try to rebuild a drive that is still currently connected... but checking SMART reports are needed... please provide those

unless you can get one of those 'failed' disks to function for a parity rebuild... you might be out of luck

Lets not forget to mention that those are some high temps to be running these HHDs at. I would suggest addressing that soon. More heat means that you will have a higher failure rate

What your describing is exactly what is happening to me. Till this is addressed, I am avoiding Disk Pools

When it comes to the dockers... disable the auto start for the dockers... Enable docker... and one by one turn a single docker on, wait and test it out, should everything look fine, repeat it's also not a good idea to do this while a parity check is running due to high disk IO

Maybe I am being a stick in the mud, but if the only thing that is causing the server to hang is a btrfs DP, why would anyone use it? Yes reading data from it is quick, but writing data to it is slow and not to mention the hangups/docker issues. When mover was writing data to the DP, it would only write about 25-50 gigs of data... In my 30 years in IT, I have never seen anything like this It's unacceptable

So it's normal for the system to hang for 2h while mover is running... and when ever a docker wants to write data to a DP? If that's the case I would rather have everything running off of the array because these issues dont exist there Though that wouldnt explain why I am unable to update around 50% of the dockers while they are hosted on the DP. Since moving them off of it, I have been able to update them. There is something wrong with a btrfs DP... Dont know what's going on but... I dont think it would be normal nor acceptable for a CPU to spike/hang a system while writing to a DP

I too have had been fighting this issue for a while now and after alot of time and testing... I have narrowed the issue down to my btrfs DiskPool... I ended up moving everything off of it due to this problem... not happy

I feel as if you have ignored my concerns on this thread... I have posted about this CPU issue a number of times in a number of different topics... Here I am trying to figure out as to why the services DP is causing CPU spikes... I even removed this DP and recreated it... but when mover was writing data to the DP, the cpu again spiked for over an hour... until there is a hint/suggestion as to why this is happening... I will be avoiding a DP in the furture

Could this be a bug of sorts?

Just for grins I recreated the Services DP and invoked mover to move things back

Yes I would like to have everything on the Services disk pool The problem is that I have been receiving errors when trying to update dockers due to a number of errors... cant stop docker, docker with the same name already exists which often times orphaned the docker. I have some dockers that I havent been able to update due to this. After moving everything off of the Services DP, I have been able to update everything. I would also randomly get system hang ups which would cause everything to hang for around 5 min and would happen 5-15 times a day. I highly suspect that these errors was due to the services DP. I think it was you who mentioned a problem with how I upgraded my DP would cause problems later. Ill Cleanup those files now. Thanks

I made a little progress... I after updating a few dockers and noticed that new files were being written to the 'Services' disk pool I changed the share setup from Services>Array to Cache>Array This cleared out around 500mb and what is left is 20mb of data... I might be willing to let this go... there is a DB file that I would like to save Anyway Logs are attached to include the Mover logs tower-diagnostics-20240109-0829.zip

Will do that tonight

Hello, Sorry for the long delay but after reading a number of different comments about dockers being at fault, I decided to play around with them to try and narrow down which one might be at fault. I never did find one to be the cause. As time went on, I began to suspect that my BTRFS share to be at fault. Seemingly any time there were heavy IO to/from that share the CPU would spike. I also had errors when trying to update different dockers, errorring out when it failed to remove the docker and couldnt install due to a docker having the same name already being there. After this the docker would be orphaned and requiring a reinstall. So last night I moved as much as I can with mover to the array after disabling docker and VMs. I have 500mb of files that refuse to move. Any input as to completely move them over would be welcome. My thoughts are to move everything off and completely rebuild this disk pool. I recall a comment years ago that, due to how I upgraded this pool that I would have problems rebuilding? I disk if I had a failure... After moving things around I have been able to update a number of dockers that previously were failing and I havent seen CPU spikes(too early to judge perhaps). Anyways, I look forward to your wise input tower-diagnostics-20240109-0723.zip

any input would be very welcome... my system is getting worse by the hour... I just updated the system and rebooted... now the system is nearly unresponsive even at the physical console... logging into it took 5 mins and every command that I give it take another five eeks!