I keep getting this error when i try pushing to heroku, i have no idea what it means.
error: unable to rewind rpc post data - try increasing http.postBuffer
error: fatal: WRPC failed; curl 56 SSL read: error:140943FC:SSL routines:ssl3_read_bytes:sslv3 alert bad record mac, errno 0
The remote end hung up unexpectedly
Writing objects: 100% (5327/5327), 44.34 MiB | 4.39 MiB/s, done.
Total 5327 (delta 1360), reused 0 (delta 0)
fatal: The remote end hung up unexpectedly
Everything up-to-date
You might try
git config http.postBuffer 524288000
Related
We are sitting behind a proxy thus git is configured as follows
[http "https://github.com"]
proxy = http://:#webproxy.intra:8080
sslBackend = schannel
sslverify = true
[http "https://gitlab.com"]
proxy = http://:#webproxy.intra:8080
sslBackend = schannel
sslverify = true
Remotes are set as follows
origin https://gitlab.com/papanito/website.git (fetch)
origin https://gitlab.com/papanito/website.git (push)
While pulling mostly worked, since a while I get the following error while fetching or pulling
$ git fetch --all
Fetching origin
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
fatal: error reading section header 'acknowledgments'
error: Could not fetch origin
this is a different issue than Git push failing HTTP 500 curl 22 The requested URL returned error: 500 Internal Server Error
This issue is probably related to the proxy (blocking?). Will further check but maybe somebody of you has some hints.
I could workaround the issue by limiting the depth.
git pull --depth 20
remote: Enumerating objects: 518, done.
remote: Counting objects: 100% (398/398), done.
remote: Compressing objects: 100% (184/184), done.
Rremote: Total 323 (delta 171), reused 237 (delta 110), pack-reused 0
Receiving objects: 100% (323/323), 4.84 MiB | 17.26 MiB/s, done.
Resolving deltas: 100% (171/171), completed with 36 local objects.
From https://gitlab.com/wyssmann/website
While this is not a proper solution, it might help some in meanwhile.
I'm trying to push a dataset of images and masks to the master branch of my GitHub repo and it keeps not working and giving me the below error messages. The size of the dataset is around 5GB. I just want to upload this dataset onto my GitHub repo and was told that bash was the best way to do it, does anyone know how to fix this error, or any other methods I could use to upload my dataset to GitHub?
Edit: Printed error message in text rather than as an image
Error message:
$ git push origin master
Enumerating objects: 1025, done.
Counting objects: 100% (1025/1025), done.
Delta compression using up to 8 threads
Compressing objects: 100% (1020/1020), done.
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
send-pack: unexpected disconnect while reading sideband packet
Writing objects: 100% (1020/1020), 3.02 GiB | 16.00 MiB/s, done.
fatal: the remote end hung up unexpectedly
Everything up-to-date
I have a problem with git push.
Its not working
Counting objects: 143, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (116/116), done.
error: RPC failed; result=22, HTTP code = 504.00 KiB/s
fatal: The remote end hung up unexpectedly| 11.00 KiB/s
Writing objects: 100% (120/120), 207.69 MiB | 7.03 MiB/s, done.
Total 120 (delta 32), reused 0 (delta 0)
fatal: The remote end hung up unexpectedly
Everything up-to-date
It's not working can someone help me in this it took so much time to to push and after that it give me this result.
It looks like your terminal just misprinted some characters. The actual error is:
error: RPC failed; result=22, HTTP code = 504
HTTP 504 means the server timed out. Searching for this should find you better help!
One day, I suddenly just cannot push to one of res (While pulling is fine). This is the error log
Writing objects: 100% (42/42), 11.23 KiB | 0 bytes/s, done.
Total 42 (delta 34), reused 0 (delta 0)
remote: /usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/shared_helpers.rb:2:in `require':
no such file to load-- rubygems (LoadError)
remote: from /usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/shared_helpers.rb:2
remote: from /usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/setup.rb:1:in `require'
remote: from /usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/setup.rb:1
remote: error: hook declined to update refs/heads/master
To http://192.168.1.140:8000/chnn/application2.git
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'http://192.168.1.140:8000/chnn/application2.git'
I can also create a new project and push it to gitlab just fine. Only 1 project has this problem
Ask your git repo admin with this error. It is custom git hook (mean git plugin) crash.
Okay. So in my particular case, no problem is found within the server. We were desperate and tried to push over ssh rather than http and then bam, it works again.
In the end, we do not know why and how. The question still remains:
Why we can push normally over http if create new projects
Why other
do not have this problem
We installed Bonobo Git Server on a webserver using IIS7.
Everything seems to work fine, we create repositories, we clone them, but when we try to push we have this error:
$ git push origin master
Username:
Password:
Counting objects: 3985, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3561/3561), done.
Writing objects: 100% (3984/3984), 24.67 MiB | 7.70 MiB/s, done.
Total 3984 (delta 645), reused 0 (delta 0)
fatal: protocol error: bad line length character: <!DO
fatal: The remote end hung up unexpectedly
fatal: write error: Invalid argument
It happens when we do a big commit, usually our initial commit.
If I commit juste something like readme.txt it works just fine.
Most of our repos are migrations from SVN, we are working with it for about 2 weeks now and everything went great until we started a new project and made a big initial commit.
I did not manage to find anything useful by googling the error.
I also modified my git.config to this:
[http]
postBuffer = 524288000
sslVerify = false
But it does not solve my issue.
Thanks a lot,
Charles
I found the problem...In fact it was in Bonobo Web.config file
I had to add the following line:
<httpRuntime maxRequestLength="2147483647" />
in the node
<system.web>