Clone aborting due to possible repository corruption on the remote side

Hi guys. Last month I was using gitlab-ce-8.11.5 from omnibus package. And 3 times during this period I had strange Gitlab issues. Sometimes some repositories couldn’t be cloned with error

09:34:40 error: pack-objects died of signal 9
09:34:40 error: git upload-pack: git-pack-objects died with error.
09:34:40 fatal: git upload-pack: aborting due to possible repository corruption on the remote side.
09:34:40 remote: aborting due to possible repository corruption on the remote side.
09:34:40 fatal: early EOF
09:34:40 fatal: index-pack failed

I was checked all these repositories on the server side and they are all OK. There is nothing strange in Gitlab logs. And after gitlab-ctl restart all these errors were gone for a while. It was always different repositories. Yesterday I was updated Gitlab to the latest gitlab-ce-8.12.7 and now watching for result. Does anybody seen bug like this?

1 Like

This usually happens because some kind of process monitor has killed the git pack-objects process due to excessive memory usage.

If you are on a shared machine, you need to talk to the host about memory limits. If you run the machine yourself, you should probably already know what to look for.

How big is the repository you are trying to clone, and how much memory does your server have? We had a similar problem with a 150mb repository on a heavily loaded server with only 3.5 GB of RAM. We moved to 8 GB of RAM, and haven’t had the problem since.

1 Like