qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Eduardo A. Bustamante López" <dualbus@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Unable to clone git repository from git.qemu.org
Date: Sun, 22 Oct 2017 11:13:12 -0500	[thread overview]
Message-ID: <20171022161312.4xlitnw2bknvv7ml@ubuntu> (raw)

[-- Attachment #1: Type: text/plain, Size: 4829 bytes --]

(please keep me CC'ed, I'm not subscribed)

Hi,

I apologize if this is not the right mailing list for this report. I'm unable to clone the git repository from
git://git.qemu.org/qemu.git (which is listed on https://www.qemu.org/contribute/).

I'm getting TCP RST's when I try to clone it, as indicated by the packet capture:

  dualbus@ubuntu:~/src/qemu$ git clone git://git.qemu.org/qemu.git
  Cloning into 'qemu'...
  fatal: read error: Connection reset by peer

  dualbus@ubuntu:~/src/qemu$ git clone git://git.qemu.org/qemu.git
  Cloning into 'qemu'...
  fatal: Could not read from remote repository.
  
  Please make sure you have the correct access rights
  and the repository exists.

  ---

  dualbus@ubuntu:~$ sudo tcpdump -n 'host git.qemu.org'
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes
  10:29:34.459497 IP 192.168.1.108.43168 > 172.99.69.163.9418: Flags [S], seq 1870728944, win 29200, options [mss 1460,sackOK,TS val 500213983 ecr 0,nop,wscale 7], length 0
  10:29:35.487129 IP 192.168.1.108.43168 > 172.99.69.163.9418: Flags [S], seq 1870728944, win 29200, options [mss 1460,sackOK,TS val 500214240 ecr 0,nop,wscale 7], length 0
  10:29:35.487854 IP 172.99.69.163.9418 > 192.168.1.108.43168: Flags [S.], seq 1436706601, ack 1870728945, win 28960, options [mss 1380,sackOK,TS val 3511630652 ecr 500213983,nop,wscale 10], length 0
  10:29:35.487949 IP 192.168.1.108.43168 > 172.99.69.163.9418: Flags [.], ack 1, win 229, options [nop,nop,TS val 500214240 ecr 3511630652], length 0
  10:29:35.488077 IP 192.168.1.108.43168 > 172.99.69.163.9418: Flags [P.], seq 1:49, ack 1, win 229, options [nop,nop,TS val 500214240 ecr 3511630652], length 48
  10:29:36.604320 IP 172.99.69.163.9418 > 192.168.1.108.43168: Flags [S.], seq 1436706601, ack 1870728945, win 28960, options [mss 1380,sackOK,TS val 3511631678 ecr 500213983,nop,wscale 10], length 0
  10:29:36.604378 IP 192.168.1.108.43168 > 172.99.69.163.9418: Flags [.], ack 1, win 229, options [nop,nop,TS val 500214519 ecr 3511630652], length 0
  10:29:36.608418 IP 172.99.69.163.9418 > 192.168.1.108.43168: Flags [.], ack 49, win 29, options [nop,nop,TS val 3511631682 ecr 500214240], length 0
  10:29:36.608943 IP 172.99.69.163.9418 > 192.168.1.108.43168: Flags [R.], seq 1, ack 49, win 29, options [nop,nop,TS val 0 ecr 500214240], length 0
  10:29:37.553793 IP 172.99.69.163.9418 > 192.168.1.108.43168: Flags [R.], seq 1, ack 49, win 229, length 0
  10:29:40.037068 IP 192.168.1.108.43170 > 172.99.69.163.9418: Flags [S], seq 4085609936, win 29200, options [mss 1460,sackOK,TS val 500215377 ecr 0,nop,wscale 7], length 0
  10:29:41.038109 IP 172.99.69.163.9418 > 192.168.1.108.43170: Flags [S.], seq 1040747289, ack 4085609937, win 28960, options [mss 1380,sackOK,TS val 3511636236 ecr 500215377,nop,wscale 10], length 0
  10:29:41.038218 IP 192.168.1.108.43170 > 172.99.69.163.9418: Flags [.], ack 1, win 229, options [nop,nop,TS val 500215627 ecr 3511636236], length 0
  10:29:41.038398 IP 192.168.1.108.43170 > 172.99.69.163.9418: Flags [P.], seq 1:49, ack 1, win 229, options [nop,nop,TS val 500215627 ecr 3511636236], length 48
  10:29:42.111622 IP 172.99.69.163.9418 > 192.168.1.108.43170: Flags [F.], seq 1, ack 1, win 29, options [nop,nop,TS val 3511637236 ecr 500215627], length 0
  10:29:42.113384 IP 192.168.1.108.43170 > 172.99.69.163.9418: Flags [F.], seq 49, ack 2, win 229, options [nop,nop,TS val 500215896 ecr 3511637236], length 0
  10:29:42.121555 IP 172.99.69.163.9418 > 192.168.1.108.43170: Flags [R], seq 1040747290, win 0, length 0
  10:29:43.121773 IP 172.99.69.163.9418 > 192.168.1.108.43170: Flags [R.], seq 2, ack 50, win 229, length 0
  ^C
  18 packets captured
  27 packets received by filter
  0 packets dropped by kernel


I was able to clone it via HTTPS, but now I'm having issues updating the git submodules

  dualbus@ubuntu:~/src/qemu/qemu$ git submodule update ui/keycodemapdb
  Cloning into '/home/dualbus/src/qemu/qemu/ui/keycodemapdb'...
  fatal: Could not read from remote repository.
  
  Please make sure you have the correct access rights
  and the repository exists.
  fatal: clone of 'git://git.qemu.org/keycodemapdb.git' into submodule path '/home/dualbus/src/qemu/qemu/ui/keycodemapdb'
  failed
  Failed to clone 'ui/keycodemapdb'. Retry scheduled
  Cloning into '/home/dualbus/src/qemu/qemu/ui/keycodemapdb'...
  fatal: Could not read from remote repository.
  
  Please make sure you have the correct access rights
  and the repository exists.
  fatal: clone of 'git://git.qemu.org/keycodemapdb.git' into submodule path '/home/dualbus/src/qemu/qemu/ui/keycodemapdb'
  failed
  Failed to clone 'ui/keycodemapdb' a second time, aborting

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

             reply	other threads:[~2017-10-22 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22 16:13 Eduardo A. Bustamante López [this message]
2017-10-23  1:15 ` [Qemu-devel] Unable to clone git repository from git.qemu.org Paolo Bonzini
2017-10-23 16:10 ` Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171022161312.4xlitnw2bknvv7ml@ubuntu \
    --to=dualbus@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).