Batimius

I searched around online and found this post that had the same issue: https://forum.gitlab.com/t/gitlab-crashing-wih-502-after-a-day/36163 In short, Redis and the database are all in the data directory, so every time the Mover was running, it would try to move files while they were running, causing them to crash. I created a separate share just for Gitlab with no caching and it seemed to have fixed the issue.

Before mover: nas-diagnostics-20250921-2225.zip After clicking on "Move": nas-diagnostics-20250921-2226.zip

Hello there. For quite some time now, I have had issues with my unRAID server and Gitlab CE Docker Container running together. I noticed this issue happens after the mover starts running (I also tested that manually). I am unsure whether this has to do with the CPU or RAM, however, I know that the issue is because of the mover. I did make a support thread in the Gitlab Discord, and they informed me that the issue is due to Postgres crashing and that I should reduce resource usage. With that said, does anyone have Gitlab CE running on their server and have set it up in a specific way? What kind of resources does the mover take up for it to cause a whole container to crash? Is there something I can do to reduce the amount of resources the mover takes up when it moves files? Any and all information is helpful. Thank you for your time and help, it is truly appreciated.