Solve The remote end hung up unexpectedly error of Gitlab, gitlabunexpectedly

Solve The remote end hung up unexpectedly error of Gitlab, gitlabunexpectedly

The Gitlab server environment is CentOS7 + Gitlab7.2.1. Recently, the following error is reported when you use git pull on the development machine to update files.

fatal: The remote end hung up unexpectedlyfatal: early EOFfatal: unpack-objects failed

The use of git clone to re-checkout source is also affected and cannot be checked out for a long time,

Google hasn't found a good solution after half a day, and finally found the error log to locate the problem.

The following error message is found in/var/log/gitlab/unicorn/unicorn_stderr.log:

E, [2014-12-06T09:13:10.319216 #11074] ERROR -- : worker=0 PID:11091 timeout (31s > 30s), killingE, [2014-12-06T09:13:10.336186 #11074] ERROR -- : reaped #<Process::Status: pid 11091 SIGKILL (signal 9)> worker=0I, [2014-12-06T09:13:10.340379 #11183]  INFO -- : worker=0 spawned pid=11183I, [2014-12-06T09:13:10.340848 #11183]  INFO -- : worker=0 read

It seems that Ruby mistakenly believes that timeout is interrupted. The solution is to increase the timeout value of unicorn.

Modify/var/opt/gitlab-rails/etc/unicorn. rb and set

# What the timeout for killing busy workers is, in secondstimeout 30

Change

# What the timeout for killing busy workers is, in secondstimeout 60

Finally, run

sudo systemctl restart gitlab-runsvdir.service 

Restart Gitlab.

Then the client will be able to run Git pull or clone normally.