Difference between revisions of "Git clone"

From wikieduonline
Jump to navigation Jump to search
Line 6: Line 6:
 
  [[GIT_TRACE]]=1 [[GIT_CURL_VERBOSE]]=1 git clone --verbose https://github.com/zabbix/zabbix-docker.git
 
  [[GIT_TRACE]]=1 [[GIT_CURL_VERBOSE]]=1 git clone --verbose https://github.com/zabbix/zabbix-docker.git
  
 +
git clone -c http.[[sslVerify]]=false
  
  

Revision as of 11:39, 29 September 2020

This article is a Draft. Help us to complete it.
git clone -vv https://github.com/zabbix/zabbix-docker.git
Cloning into 'zabbix-docker'...
GIT_TRACE=1 GIT_CURL_VERBOSE=1 git clone --verbose https://github.com/zabbix/zabbix-docker.git
git clone -c http.sslVerify=false


error: git upload-pack: git-pack-objects died with error.
fatal: git upload-pack: aborting due to possible repository corruption on the remote side.
remote: aborting due to possible repository corruption on the remote side.
fatal: protocol error: bad pack header
Solution: review memory usage on git server


With errors

GIT_TRACE=1 GIT_CURL_VERBOSE=1 git clone --verbose https://gitlab.youdomain.com/project1/app.git
15:31:11.872513 exec-cmd.c:139          trace: resolved executable path from Darwin stack: 
/Library/Developer/CommandLineTools/usr/bin/git
15:31:11.873411 exec-cmd.c:236          trace: resolved executable dir: /Library/Developer/CommandLineTools/usr/bin
15:31:11.873488 git.c:418               trace: built-in: git clone --verbose https://gitlab.youdomain.com/project1/app.git
Cloning into 'app'...
15:31:11.896610 run-command.c:643       trace: run_command: git-remote-https origin 
https://gitlab.youdomain.com/project1/app.git
15:31:11.909999 exec-cmd.c:139          trace: resolved executable path from Darwin stack: 
/Library/Developer/CommandLineTools/usr/libexec/git-core/git-remote-https
15:31:11.911055 exec-cmd.c:236          trace: resolved executable dir: /Library/Developer/CommandLineTools/usr/libexec/git-core
* Couldn't find host gitlab.youdomain.com in the .netrc file; using defaults
*   Trying 10.10.110.xx...
* TCP_NODELAY set
* Connected to gitlab.youdomain.com (10.10.xx.xx) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* SSL certificate problem: self signed certificate
* stopped the pause stream!
* Closing connection 0
fatal: unable to access 'https://gitlab.youdomain.com/project1/app.git/': SSL certificate problem: self signed certificate

Related terms

See also

Advertising: