[ZBX-20147] git clone fails Created: 2021 Oct 31 Updated: 2022 Feb 19 |
|
Status: | Confirmed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Problem report | Priority: | Trivial |
Reporter: | FP | Assignee: | Alex Kalimulin |
Resolution: | Unresolved | Votes: | 3 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
git clone https://git.zabbix.com/scm/zbx/zabbix.git Cloning into 'zabbix'... remote: Counting objects: 969268, done. remote: Compressing objects: 100% (206013/206013), done. error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated. fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: index-pack failed tested with two different Git versions (2.27.0 and 2.33.1) |
Comments |
Comment by FP [ 2021 Oct 31 ] |
here with Git 2.33.1 Cloning into 'zabbix'... remote: Counting objects: 969282, done. remote: Compressing objects: 100% (206027/206027), done. error: RPC failed; curl 18 transfer closed with outstanding read data remaining fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output |
Comment by Håkon Løvdal [ 2022 Feb 19 ] |
This is still the case, both on Fedora 35 as well as Centos 7: $ git clone https://git.zabbix.com/scm/zbx/zabbix.git Cloning into 'zabbix'... remote: Enumerating objects: 1020305, done. remote: Counting objects: 100% (1020305/1020305), done. remote: Compressing objects: 100% (183478/183478), done. error: RPC failed; result=18, HTTP code = 2000 GiB | 5.30 MiB/s fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed $ git --version git version 1.8.3.1 $ I also attempted to clone from a VPS in Netherlands without success. Cloning https://git.zabbix.com/scm/zbx/zabbix instead of https://git.zabbix.com/scm/zbx/zabbix.git makes no difference. Digging a bit further this problem seems to be network related, possibly some Atlasian Bitbucket specific problem (although similar problems seems to affect github as well). Enabling trace logging like suggested here and here did not reveal anything. Increasing transfer buffers/disabling compression like suggested here, here and here did not help. $ git clone --depth=1 https://git.zabbix.com/scm/zbx/zabbix.git $ cd zabbix/ $ git fetch --unshallow |