Problem scenario
You try to log into GitLab for the first time, but you get this error:
"502 Whoops, GitLab is taking too much time to respond."
What should you do?
Solution
Go to the back end of the server. Run the top command. Is the left most load average above 1 (e.g, 1.08)?
The top line of the results of the top command will look something like this:
load average: 1.08, 1.93, 3.99
The left most number is 1.08. This is above 1.00. GitLab is sensitive to loads. You may need to stop other processes or use a server with more CPUs, faster CPUs, and more memory (RAM). If you are using an AWS server and want to resize your EC-2 instance, you may want to see this posting. If you are using GCP and want to resize your VM, you may want to see this posting.