go-gitea / gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
https://gitea.com
MIT License
44.6k stars 5.45k forks source link

error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1) #10838

Closed ghost closed 4 years ago

ghost commented 4 years ago

Hi,

After transferring a repo to another organisation, our server started throwing some errors when pushing:

error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

Infos

Description

When trying to push on a repo the CPU is heavily solicited, here is a log from the client:

% git push -v                                                                                                                                                                         [26/03/20 15:43]
Pushing to https://REDACTED/REDACTED/clic.email.git
Enumerating objects: 9, done.
Counting objects: 100% (9/9), done.
Delta compression using up to 4 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (5/5), 155.49 KiB | 12.96 MiB/s, done.
Total 5 (delta 1), reused 0 (delta 0)
POST git-receive-pack (159394 bytes)
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date

Thanks in advance for your help.

ghost commented 4 years ago

I found the source of this problem, a file I was trying to upload was too large for the server. I reduced the weight of this one, pushed again and it went through!