MacGyver33

Got it figured out: https://discourse.cubecoders.com/t/startup-issue-with-satisfactory-access-denied-when-starting-satisfactory/8447 Had to run the following as root: ampinstmgr fixperms Then drilled in to the folder with the executable and run chmod +x UnrealServer-Linux-Shipping to reassign the executable permission

Anyone know how to reset the folder permissions for AMP? I can't get my Satisfactory server to start and getting this error: [05:15:39] [Core Error] : PlatformException [05:15:39] [Core Error] : [0] (PlatformException) : ApplicationName='/home/amp/.ampdata/instances/SatisfactoryServer01/satisfactory/1690800/Engine/Binaries/Linux/UnrealServer-Linux-Shipping', CommandLine='FactoryGame -log -unattended -MultiHome=0.0.0.0 ?listen -Port=7777 -BeaconPort=15000 -ServerQueryPort=15777 ', CurrentDirectory='/home/amp/.ampdata/instances/SatisfactoryServer01/satisfactory/1690800', Native error= Access denied [05:15:39] [Core Error] : at Diagnostics.Process.StartWithCreateProcess (Diagnostics.ProcessStartInfo startInfo) at Diagnostics.Process.Start () at ModuleShared.AMPProcess.Start () at (wrapper remoting-invoke-with-check) ModuleShared.AMPProcess.Start() at GenericModule.GenericApp.DoAppStartup (Boolean IsUpdating) at GenericModule.GenericApp.Start () I ran the Docker Safe New Perms tool the other day in Unraid which I think may have wiped whatever permissions AMP had to the game folders. Odd thing is my Minecraft server instance is starting up just fine and I can browse in the File Manager to all the Satisfactory folders.

I second the interest in updating this for the 3.x bot. Looks like it uses docker-compose and other images for Redis and Postgres. Can the UnRaid docker manager handle multi-image containers like this or would we need to setup additional containers for redis and postgres?

Is there any way to run GitLab-CE with 2GB or less of RAM? I only have 8GB of RAM in my unRAID box right now and if I let GitLab run unrestricted it gobbles up as much RAM as it can. I have tried restricting the docker RAM to 2GB by adding --memory="2g" to the Extra Parameters line but I get a 502 error when launching the WebUI. I am only looking to use GitLab for me and a few friends occasionally (hobbyist programming) but according to the GitLab documention, 4GB is minimum for up to 100 users: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md I don't need anywhere near that capacity and we are only going to be doing small private repos so we won't leverage most of the more advanced features. Is GitLab overkill for small teams? Is there a lighter weight Git hosting server in a Docker container that would work better for small teams?

I've had nearly 4 days of continuous up-time after making this change so I am going to mark this as solved. Thanks for your help!

I hadn't seen this in the release notes and after checking my BIOS settings I found Global C-states set to Auto which likely means it was enabled. I'll try this and see how it goes. Tried another round of Memtest all day today without errors. I'll report back in a few days if this resolved the issue or not. Thanks!

Had another lockup today around 9:20pm. This time I pulled the Unraid USB drive to grab the syslog_tail before reboot. Nothing glaring jumps out at me in looking at the last few entries in the log. Also here is my hardware setup: ASRock AB350 PRO4 ATX Motherboard (Updated BIOS to 4.60) AMD Ryzen 5 1500X CPU Patriot VIPER 4 Series 2400MHz 8GB Dual Channel RAM (2x4GB) SanDisk Ultra Fit 32GB USB 3.0 (Unraid drive) 2x2TB Seagate Desktop HDD 64MB Cache SATA3 (1-Parity, 1-Disk Pool) FCPsyslog_tail.txt fieldsuhs3-diagnostics-20180211-2100.zip

I'm getting random lock ups on a freshly installed Unraid 6.4 build. The system remains stable for anywhere between a few hours to 20-30 hours but then locks up and has to be hard rebooted. I tried the update to 6.4.1 and the problem still appears to be happening. Yesterday I ran Memtest for a few hours and it went through 5 passes on all tests and all CPU cores without errors. I currently have the following dockers running but the lock up issue was happening before these were installed: CrashPlan PlexMediaServer plexpy Netdata GitLab-CE (disabled) FCP only reports a few errors with the port mapping on GitLab-CE but I have currently disabled that docker to work out an issue with it gobbling RAM. I had FCP in Troubleshooting mode but in looking at the FCPsyslog_tail file I see the last entry was at 4:38am this morning but the last diagnostic dump was at 11:09am and then the lockup happened sometime between 11:09-11:30am. I turned Troubleshooting mode on again in FCP and also added the Tips & Tweaks plugin to enable log syslog Archiving and will post an update the next time it happens. See my attached logs from FCP. FCPsyslog_tail.txt fieldsuhs3-diagnostics-20180211-1109.zip