gitlab报错解决（骗个访问量）_whoops, gitlab is currently unavailable.-CSDN博客

本文分享了一种解决GitLab响应时间过长的问题的方法：通过检查服务器内存负载来定位问题，并给出了具体的内存使用情况示例。

我看我最近写的博客都没人看了，骗个访问量。
gitlab遇到下面错误怎么解决呢
Whoops, GitLab is taking too much time to respond
Whoops, GitLab is taking too much time to respond
Whoops, GitLab is taking too much time to respond
Whoops, GitLab is taking too much time to respond
Whoops, GitLab is taking too much time to respond
Whoops, GitLab is taking too much time to respond
Whoops, GitLab is taking too much time to respond
Whoops, GitLab is taking too much time to respond
Whoops, GitLab is taking too much time to respond
遇到问题不要慌，先看内存负载（我执行了两次查看内存使用情况看到了没，内存不够用啊，加内存立马好使）
教程来了

[root@localhost ~]# free -m
              total        used        free      shared  buff/cache   available
Mem:           2829         683        1584          35         560        1903
Swap:          2047         100        1947
[root@localhost ~]# free -m
              total        used        free      shared  buff/cache   available
Mem:           2829        2023         152          51         653         532
Swap:          2047         100        1947

不信？不信你在访问下看看
https://blog.csdn.net/zeorg/article/details/114633606