Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

git clone "error: RPC failed; curl 56 Failure when receiving data from the peer" #5265

Open
1 task done
Balkoth opened this issue Nov 20, 2024 · 4 comments
Open
1 task done

Comments

@Balkoth
Copy link

Balkoth commented Nov 20, 2024

  • I was not able to find an open or closed issue matching what I'm seeing

Setup

  • Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
$ git --version --build-options

git version 2.47.0.windows.2
cpu: x86_64
built from commit: 1f8a83cba6e88fad4b881885e64cfb89458e3653
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.10.1
OpenSSL: OpenSSL 3.2.3 3 Sep 2024
zlib: 1.3.1
  • Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver

Microsoft Windows [Version 10.0.19045.5011]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
  • What options did you set as part of the installation? Or did you choose the
    defaults?
# One of the following:
> type "C:\Program Files\Git\etc\install-options.txt"
> type "C:\Program Files (x86)\Git\etc\install-options.txt"
> type "%USERPROFILE%\AppData\Local\Programs\Git\etc\install-options.txt"
> type "$env:USERPROFILE\AppData\Local\Programs\Git\etc\install-options.txt"
$ cat /etc/install-options.txt

Editor Option: VisualStudioCode
Custom Editor Path: 
Default Branch Option:  
Path Option: Cmd
SSH Option: OpenSSH
Tortoise Option: false
CURL Option: WinSSL
CRLF Option: CRLFCommitAsIs
Bash Terminal Option: ConHost
Git Pull Behavior Option: Merge
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Enabled
Enable FSMonitor: Disabled
  • Any other interesting things about your environment that might be related
    to the issue you're seeing?

Repository is hosted on a Server with git-http-backend.exe

Details

  • Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other

Bash/CMD

git clone https://server.company.de/Repository.git
  • What did you expect to occur after running these commands?

Cloning without errors.

  • What actually happened instead?
Cloning into 'Repository'...
remote: Enumerating objects: 19174, done.
remote: Counting objects: 100% (19174/19174), done.
remote: Compressing objects: 100% (2168/2168), done.
error: RPC failed; curl 56 Failure when receiving data from the peer
remote: Total 19174 (delta 18267), reused 17491 (delta 16998), pack-reused 0 (from 0)
Receiving objects: 100% (19174/19174), 6.83 MiB | 4.74 MiB/s, done.
Resolving deltas: 100% (18267/18267), done.
Updating files: 100% (2589/2589), done.

I don't know where to start because the error message is unhelpful.

Randomly setting

   [http]
       postBuffer = 524288000

on the client and server has had no effect.

Setting GIT_HTTP_MAX_REQUEST_BUFFER to 100M from default 10M has no effect.

GIT_CURL_VERBOSE=1 does not reveal any helpful information to me.

A shallow clone works without error:

$ git clone --depth=1 https://server.company.de/Repository.git
Cloning into 'Repository'...
remote: Enumerating objects: 2630, done.
remote: Counting objects: 100% (2630/2630), done.
remote: Compressing objects: 100% (2294/2294), done.
remote: Total 2630 (delta 2369), reused 388 (delta 334), pack-reused 0 (from 0)
Receiving objects: 100% (2630/2630), 1.48 MiB | 21.72 MiB/s, done.
Resolving deltas: 100% (2369/2369), done.
Updating files: 100% (2589/2589), done.
@jblaine
Copy link

jblaine commented Nov 20, 2024

We are seeing the same thing:

$ git clone https://github.com/google/googletest.git/
Cloning into 'googletest'...
remote: Enumerating objects: 27711, done.
remote: Counting objects: 100% (60/60), done.
remote: Compressing objects: 100% (43/43), done.
error: RPC failed; curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0
remote: Total 27711 (delta 24), reused 32 (delta 12), pack-reused 27651 (from 1)
Receiving objects: 100% (27711/27711), 13.04 MiB | 6.50 MiB/s, done.
Resolving deltas: 100% (20568/20568), done.

Adding --depth=1 causes the failure to go away.

Install options

Editor Option: VIM
Custom Editor Path:
Default Branch Option: main
Path Option: Cmd
SSH Option: ExternalOpenSSH
Tortoise Option: false
CURL Option: WinSSL
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Git Pull Behavior Option: Merge
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Disabled
Enable Pseudo Console Support: Disabled
Enable FSMonitor: Disabled
$ git --version --build-options
git version 2.45.1.windows.1
cpu: x86_64
built from commit: 965b16798dab6962ada5b0d8cf0dca68f385c448
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
Microsoft Windows [Version 10.0.19045.5131]
(c) Microsoft Corporation. All rights reserved.

@dscho
Copy link
Member

dscho commented Nov 21, 2024

error: RPC failed; curl 56 Failure when receiving data from the peer

This error looks a bit different than

error: RPC failed; curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0

though.

In any case, maybe switching to the Secure Channel backend via git config http.sslBackend schannel helps?

@Balkoth
Copy link
Author

Balkoth commented Nov 21, 2024

On my client and server this is already in the C:\Program Files\Git\etc\gitconfig:

Client:

[diff "astextplain"]
	textconv = astextplain
[filter "lfs"]
	clean = git-lfs clean -- %f
	smudge = git-lfs smudge -- %f
	process = git-lfs filter-process
	required = true
[http]
	sslBackend = schannel
[core]
	autocrlf = false
	fscache = true
	symlinks = true
	pager = tr -d '\\r' | less -REX
	editor = \"C:\\\\Program Files\\\\Microsoft VS Code\\\\bin\\\\code\" --wait
[pull]
	rebase = false
[credential]
	helper = manager
[credential "https://dev.azure.com"]
	useHttpPath = true
[init]
	defaultBranch = master
[safe]
	directory = *

Server:

[diff "astextplain"]
	textconv = astextplain
[filter "lfs"]
	clean = git-lfs clean -- %f
	smudge = git-lfs smudge -- %f
	process = git-lfs filter-process
	required = true
[http]
	sslBackend = schannel
[core]
	autocrlf = false
	fscache = true
	symlinks = false
	editor = \"C:\\\\Program Files\\\\Microsoft VS Code\\\\bin\\\\code\" --wait
[pull]
	rebase = false
[credential]
	helper = manager
[credential "https://dev.azure.com"]
	useHttpPath = true
[init]
	defaultBranch = master
[safe]
	directory = *

@paulvxx
Copy link

paulvxx commented Nov 21, 2024

Oddly enough, I was having the same Issue when I need to clone "googletest" as part of my make file build. (cmake ..)

Failed to clone 'third-party/google-test'. Retry scheduled
Cloning into '/home/user/openfhe-development/third-party/google-test'...
error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated.

Attempting to install the submodule with

git submodule update --init --depth=1

seems to work (bypass the GnuTLS error), yet when I proceed onwards to actually building the program files, I now obtain a sort of error (see openfheorg/openfhe-development#409) which I would have not got if everything ran smoothly from the start (I verified this by attempting to set up the program files on a different machine)

$ make
Scanning dependencies of target third-party
-- Copied demoData files
[  0%] Built target third-party
Scanning dependencies of target coreobj
[  1%] Building CXX object src/core/CMakeFiles/coreobj.dir/lib/lattice/constants-lattice-impl.cpp.o
[  1%] Building CXX object src/core/CMakeFiles/coreobj.dir/lib/lattice/lattice.cpp.o
In file included from /home/user/openfhe-development-full/src/core/include/math/hal/bigintdyn/ubintdyn.h:51,
                 ...
/home/user/openfhe-development-full/src/core/include/utils/serializable.h:60:10: fatal error: cereal/cereal.hpp: No such file or directory
   60 | #include "cereal/cereal.hpp"
      |          ^~~~~~~~~~~~~~~~~~~

[See the Linux installation instructions of https://github.com/openfheorg/openfhe-development --- to attempt to replicate the exact issue]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants