Source based upgrade: "error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 Internal Server Error"

How to Use GitLab Upgrade
1

I’m trying to update our (source based) gitlab installation to the latest version but have some weird issues with git

When trying to fetch the latest version from the gitlab.com server, it takes ages and ends in an error like below:

[git@gitlab ~/gitlab]$ git fetch --all
Fetching origin
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 Internal Server Error
fatal: The remote end hung up unexpectedly
error: Could not fetch origin

the origin is the same since I installed gitlab 8.3, so quite some time ago:

[git@gitlab ~/gitlab]$ git remote show origin

Any ideas what goes wrong here?

2

Also having similar issues, however most of the time it won’t even show the 500 error, but instead stays stuck without output.

# sudo -u git -H git fetch --all -v
Fetching origin
POST git-upload-pack (gzip 6497 to 3328 bytes)
POST git-upload-pack (gzip 6797 to 3475 bytes)
POST git-upload-pack (gzip 7847 to 4003 bytes)
POST git-upload-pack (gzip 10697 to 5430 bytes)
POST git-upload-pack (gzip 15697 to 7930 bytes)

Here is a more verbose output: http://pastebin.com/Xmy4zTBe

I am running git 2.1.4 (latest stable package from Debian 8).

EDIT: checked also with git 2.10.1 with a same result.

3

for the time being, I’ve worked around the issue by cloning gitlab-ce into a new, vanilla directory, add that directory as a new “local” remote for the original gitlab installation and do the git fetch --all from the new “local” remote.

So as it seems, the gitlab.com git service dies for with HTTP/500 under certain, unknown conditions …