Another update. and I got Good News and Bad News.
Good News: The original Merge Requester decided to do the following:
- Re-pull
master(he was about 17 commits behind) - Re-add the files to the Project he plans to branch
- Create a New Branch with his changes
- Pushed changes to the New Branch
- Created a New Merge Request
Now, at first the New Merge Request had the Checking if merge request can be merged… up for awhile … but after a few mins, that stopped and we have the green Merge button (no merge conflicts!). There really isn’t any new changes, but clearly the Merge Requester being behind master was a real problem.
The Merge Request hasn’t been merged yet though, so we don’t know if there will be any problems.
Bad News: The same Merge Requester is setting up a new Merge Request from another Branch … and now every time he tries to create a merge request, he gets a 500 Error page in GitLab.
Now Server-wise (we host our GitLab on a Private Server VM): no disk space issues, CPU Usage is low, Memory Usage is only at 50%, so not any issues there. crond (and all the previous errors I shared) are still all there, but clearly this 500 Error page is brand new.
Could it be that merging the previous Merge Request, and then him re-creating a Merge Request with his new changes, may fix things? No idea.
Once the previous Merge Request is merged (and assuming no issues there), I’m going to suggest the Merge Requester to try re-creating his content after another master pull, new branch, push content and then try creating a Merge Request. If that doesn’t resolve the issue, I’m going to backup and restart GitLab. Not sure what else to do.