git - 来自 Nginx 的 502 Bad Gateway for large GitLab fork

Question

我正在通过 Nginx 运行 GitLab 6.0.0，并且可以 fork 小型存储库，但是当我尝试 fork 大型存储库 (2GB) 时，大约 502 Bad Gateway 页面出现了 < strong>一分钟。

/var/log/nginx/gitlab_error.log 显示:

2013/08/29 12:21:33 [error] 25098#0: *221 upstream prematurely closed connection while reading response header from upstream, 
  client: 12.34.56.78, 
  server: myserver, 
  request: "POST /mygroup/myproject/fork HTTP/1.1", 
  upstream: "http://unix:/home/git/gitlab/tmp/sockets/gitlab.socket:/mygroup/myproject/fork", 
  host: "myserver", 
  referrer: "http://myserver/mygroup/myproject/fork"

Answer 1

Issue 1527提示存在内存问题(以及 memory requirement in mentioned in the doc )。

也可能是因为初始超时:

I found this error would also occur because the unicorn workers would sometimes take 33 seconds to start and they're configured to timeout after 30 seconds.

你可以修改 unicorn 配置文件 /home/git/gitlab/config/unicorn.rb :

timeout 300

在您的 NGiNX 配置中，您还可以添加:

proxy_connect_timeout 300;
proxy_read_timeout 300;

如果你的 NGiNX 有一个 /etc/nginx/fastcgi_params 文件，你可以添加:

fastcgi_connect_timeout 60;
fastcgi_send_timeout 180;
fastcgi_read_timeout 180;
fastcgi_buffer_size 156 16k;
fastcgi_buffers 256 16k;
fastcgi_busy_buffers_size 256k;
fastcgi_temp_file_write_size 256k;
fastcgi_intercept_errors on;
fastcgi_max_temp_file_size 0

fastcgi_pass            unix:/tmp/fpm.sock;

---

请注意，在出现 502 并进行上述修复后，最好在再次尝试访问 gitlab 之前清除浏览器缓存。