“GitLab 没有响应."启动服务器后 Ubuntu 14.04 上的 502 [英] "GitLab is not responding." 502 on Ubuntu 14.04 after starting server

问题描述

我刚刚在一个全新的 Ubuntu 14.04 64 位服务器上安装了 GitLab.我是使用 ，我尝试了查询状态，结果也是错误:

sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=productionsudo:捆绑:找不到命令

我尝试访问日志，但在系统中找不到 unicorn.stderr.log 文件.

在 Ubuntu 12.04 上有 类似的问题 有同样的错误，解决方案是增加独角兽超时.我已尝试这样做，但错误消息仍然存在.

解决方案

从 gitlab 启动/重启到真正能够处理请求有大约 5 分钟的延迟.以下是日志中的示例:

2015-01-08_09:00:57.37719 [13326] 08 Jan 10:00:57.377 * 服务器现在已准备好接受端口 0 上的连接2015-01-08_09:00:57.37722 [13326] 1 月 8 日 10:00:57.377 * 服务器现在已准备好接受/var/opt/gitlab/redis/redis.socket 的连接[...]==>/var/log/gitlab/unicorn/unicorn_stderr.log <==我，[2015-01-08T10:04:48.676879 #13351] INFO -- : 监听 addr=127.0.0.1:8080 fd=11我，[2015-01-08T10:04:48.677663 #13351] INFO -- : unlinking existing socket=/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket我，[2015-01-08T10:04:48.690283 #13351] INFO -- : 监听 addr=/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket fd=12我，[2015-01-08T10:04:48.716769 #13413] INFO -- : worker=0 spawned pid=13413我，[2015-01-08T10:04:48.735878 #13351] INFO -- : 主进程就绪我，[2015-01-08T10:04:48.846635 #13416] INFO -- : worker=1 spawned pid=13416我，[2015-01-08T10:04:48.837438 #13413] INFO -- : worker=0 准备好了我，[2015-01-08T10:04:48.863110 #13416] INFO -- : worker=1 准备好了

在 Unicorn 报告它在端口 8080 上启动并运行之前，将显示GitLab 没有响应"消息.所以大家要做的就是等待.

I have just installed GitLab on a fresh Ubuntu 14.04 64 bit server. I did so using the Omnibus package as indicated in the download page. There were no error messages during the install and all the remarks from the script were displayed in green.

When I access the server through port 80 I get the following:

Following the Trouble Shooting Guide I tried to query the status, but the result is also an error:

sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
sudo: bundle: command not found

I tried to access the logs but the unicorn.stderr.log file is nowhere to be found in the system.

There is a similar question with the same error on Ubuntu 12.04, to which the solution is to increase the unicorn timeout. I have tried to do so but the error message remains.

解决方案

There is a lag of some 5 minutes from the moment gitlab is started/restarted to the point when it is actually able to process requests. Here is an example from the log:

2015-01-08_09:00:57.37719 [13326] 08 Jan 10:00:57.377 * The server is now ready to accept connections on port 0
2015-01-08_09:00:57.37722 [13326] 08 Jan 10:00:57.377 * The server is now ready to accept connections at /var/opt/gitlab/redis/redis.socket

[...]

==> /var/log/gitlab/unicorn/unicorn_stderr.log <==
I, [2015-01-08T10:04:48.676879 #13351]  INFO -- : listening on addr=127.0.0.1:8080 fd=11
I, [2015-01-08T10:04:48.677663 #13351]  INFO -- : unlinking existing socket=/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket
I, [2015-01-08T10:04:48.690283 #13351]  INFO -- : listening on addr=/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket fd=12
I, [2015-01-08T10:04:48.716769 #13413]  INFO -- : worker=0 spawned pid=13413
I, [2015-01-08T10:04:48.735878 #13351]  INFO -- : master process ready
I, [2015-01-08T10:04:48.846635 #13416]  INFO -- : worker=1 spawned pid=13416
I, [2015-01-08T10:04:48.837438 #13413]  INFO -- : worker=0 ready
I, [2015-01-08T10:04:48.863110 #13416]  INFO -- : worker=1 ready

Before Unicorn reports that it is up and running on port 8080, the "GitLab is not responding" message will be displayed. So all one has to do is wait.

这篇关于“GitLab 没有响应."启动服务器后 Ubuntu 14.04 上的 502的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！