Resolve Gitlab The remote end hung up unexpectedly error

The Gitlab server environment is centos7+gitlab7.2.1, and it is reported that the following error occurred when using git pull to update the file on the development machine.

Fatal:the remote end hung up unexpectedlyfatal:early eoffatal:unpack-objects failed

Using Git clone to re-checkout the source is also affected, long time checkout not come out,

Google has not found a good way for half a day, and finally check the error log to locate the problem

In/var/log/gitlab/unicorn/unicorn_stderr.log, the following error message is found

E, [2014-12-06t09:13:10.319216 #11074] ERROR--: worker=0 pid:11091 timeout (31s > 30s), Killinge, [2014-12-06t09:13:1 0.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 was mistaken for a timeout interruption. The solution is to increase the timeout value of the unicorn.

Modify the/VAR/OPT/GITLAB/GITLAB-RAILS/ETC/UNICORN.RB to

# What's the timeout for killing busy workers are, in Secondstimeout 30

Switch

# What's the timeout for killing busy workers are, in Secondstimeout 60

Finally, run

Restart Gitlab.

After that, the client will be able to git pull or clone.

Resolve Gitlab The remote end hung up unexpectedly error