解决GitLab 502

1.查看Nginx日志

fztree@x2:/var/log$ less /var/log/nginx/gitlab_error.log

2015/09/06 03:27:31 [error] 2825#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.1.

git/gitlab/tmp/sockets/gitlab.socket:/users/sign_in", host: "git.x2ray.com"

2.查看Gitlab日志

fztree@x2:/var/log$ grep -i error /home/git/gitlab/log/*

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:07:51.239370 #22645] ERROR -- : worker=1 PID:22654 timeout (31s > 30s), killing

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:07:51.294775 #22645] ERROR -- : reaped #<Process::Status: pid 22654 SIGKILL (signal 9)> worker=1

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:08:13.318498 #22645] ERROR -- : worker=3 PID:22659 timeout (31s > 30s), killing

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:08:13.346099 #22645] ERROR -- : reaped #<Process::Status: pid 22659 SIGKILL (signal 9)> worker=3

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:12:43.073807 #1258] ERROR -- : worker=3 PID:1273 timeout (31s > 30s), killing

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:12:43.108270 #1258] ERROR -- : reaped #<Process::Status: pid 1273 SIGKILL (signal 9)> worker=3

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:13:06.134437 #1258] ERROR -- : worker=2 PID:1270 timeout (31s > 30s), killing

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:13:06.167529 #1258] ERROR -- : reaped #<Process::Status: pid 1270 SIGKILL (signal 9)> worker=2

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:13:32.192052 #1258] ERROR -- : worker=3 PID:1688 timeout (31s > 30s), killing

/home/git/gitlab/log/unicorn.stderr.log:E, [2015-09-06T03:13:32.212659 #1258] ERROR -- : reaped #<Process::Status: pid 1688 SIGKILL (signal 9)> worker=3

3.OH, forgot

bundle exec rake assets:precompile RAILS_ENV=production

解决GitLab 502相关推荐

GitLab 502问题的解决
问题: 502 Whoops, GitLab is taking too much time to respond. 日志: [root@cs12-66-gitlab ~]# my gitlab-ct ...
解决GitLab中使用SSH的git clone总是提示输入密码且任何密码都不对
解决GitLab中使用SSH的git clone总是提示输入密码且任何密码都不对笔者最近在新 Linux 中安装 GitLab 后,发现一个诡异的事情.当配置完管理员账号.SSH 密钥之后.开启 ...
解决gitlab关闭登录选项问题
解决gitlab关闭登录选项问题参考文章: (1)解决gitlab关闭登录选项问题 (2)https://www.cnblogs.com/uglyliu/p/7214296.html 备忘一下.
【Git学习】解决GitLab内存消耗大的问题
一.问题描述今天有提示反馈Gitlab服务器push不上去,让我看看是不是Gitlab服务器出了什么问题. 我查看了下gitlab在线的信息这台服务器消耗了31.3GB内存. 然后我11:14分尝 ...
解决nginx 502 bad gateway--团队的力量
nginx 502 bad gateway 可以采取客户端强制刷新的方法,但是真正的解决要么改配置或者放CDN上. 遇到这个问题,首先是有人发现可以加index.html访问,因为我们是线上 ...
【git】解决gitlab ip更改问题
有时候因为部署gitlab虚拟机的ip发生变化,gitlab的clone地址没有同时更新到新的ip, 这导致后续clone报错,解决办法如下: 进入部署gitlab的主机: sudo vim /opt ...
docker 解决php 502,Docker里两个php容器一个正常访问，一个出现502 Bad Gateway nginx/1.17.8。...
问题描述 Docker里两个php容器一个镜像是phpfpm5.6,运行的程序是emlog,正常访问.一个镜像是phpfpm7.3,运行的程序是wordpress,运行的出现502 Bad Gatew ...
解决gitlab限制上传大小文件的问题
2019独角兽企业重金招聘Python工程师标准>>> 简介首先亮出报错关键字 error: RPC failed; result=22, HTTP code = 413 fata ...
解决Gitlab的The remote end hung up unexpectedly错误
这两天使用Git从Gitlab服务器上clone项目到自己电脑的时候出现了错误: fatal: The remote end hung up unexpectedly fatal: early EOF ...

解决GitLab 502

解决GitLab 502相关推荐

最新文章

热门文章