table of Contents
One installation configuration dependencies
Two install Gitlab software package
2 Execute the following command
2. 502 Whoops, GitLab is taking too much time to respond
Foreword:
Gitlab is installed on a virtual machine. The first requirement is that the memory of the virtual machine cannot be less than 2G. When the editor installed 3G, after the installation, the startup is completed, which consumes about 2500M, so it is recommended that you install Gitlab before Set the memory of the virtual machine to 3G or more. If the computer memory is large enough, you can set 4G. Try to ensure that the memory is enough, otherwise there will be some errors after the installation is over.
installation steps:
I use the following visualization tools, and I feel pretty good, recommend them:
Link: https://pan.baidu.com/s/1ZpXxBBFRq35hUiTUhlGy8Q
Extraction code: tzj2
One installation configuration dependencies
sudo yum install -y curl policycoreutils-python openssh-server
sudo systemctl enable sshd
sudo systemctl start sshd
sudo firewall-cmd --permanent --add-service=http
sudo systemctl stop firewalldIt may take a little longer, just be patient
Two install Gitlab software package
1 Upload the gitlib package
Link: https://pan.baidu.com/s/19OL-N3Gz3wqtKxGxOumjaw
Extraction code: 0696
Download the above software package, drag the downloaded software package to the root directory of the visualization file:
2 Execute the following command
rpm -i gitlab-ce-12.10.6-ce.0.el7.x86_64.rpm
(It will take more than 10 seconds to obtain these dozens of seconds, just wait patiently for a while, when the following interface appears, the installation is successful)
3 Initialize Gitlab configuration
(This required event is relatively long, usually 3~5 minutes, or even more than 10 minutes, the editor is relatively poor, and it took 25 minutes)
sudo gitlab-ctl reconfigure
4 Other commands
# Start gitlab service
gitlab-ctl start# Stop gitlab service
gitlab-ctl stop
Three common mistakes
1. An error occurred. Sorry, the page you are looking for is currently unavailable. Please try again
Close nginx and restart gitlab to solve it.
Out of service:
/usr/local/nginx/sbin/nginx -s stop #Stop the service (this address is written according to your installation location)
Restart gitlab:
The editor stops first and then starts
2. 502 Whoops, GitLab is taking too much time to respond
The reason for this exception is due to insufficient memory, but if the memory has been given 3G or 4G or more, you can use free-m to test whether the memory is decreasing. If it is decreasing, it means that Gitlab is starting, but it has not been loaded yet. That's it, wait patiently for a while.
