Discussion:
[ipxe-devel] Git not working?
John Haxby
2018-11-14 13:13:24 UTC
Permalink
Hello,

The git repo seems to have been down for about a week:

$ git clone git://git.ipxe.org/ipxe.git
Cloning into 'ipxe'...
fatal: read error: Connection reset by peer

I've tried it from a variety of different hosts in different places and I've tried forcing IPv4 instead of IPv6.

Is there something different I should be doing?

jch
Geert Stappers
2018-11-14 13:22:20 UTC
Permalink
Post by John Haxby
Hello,
$ git clone git://git.ipxe.org/ipxe.git
Cloning into 'ipxe'...
fatal: read error: Connection reset by peer
I've tried it from a variety of different hosts in different places and I've tried forcing IPv4 instead of IPv6.
Is there something different I should be doing?
I think John did already good work by reporting that git services was
missing.

Where he got 'Connection reset by peer'
do I get 'fatal: Could not read from remote repository.'

Mostly likely is the repair now work in progress
( I don't know, no inside information )


Cheers
Geert Stappers
--
***@trancilo:~/src
$ cd ipxe/
***@trancilo:~/src/ipxe
$ git config --list
user.email=***@hendrikx-itc.nl
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.url=git://git.ipxe.org/ipxe.git
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.master.remote=origin
branch.master.merge=refs/heads/master
***@trancilo:~/src/ipxe
$ git pull
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
***@trancilo:~/src/ipxe
$
John Haxby
2018-11-14 13:27:03 UTC
Permalink
Post by Geert Stappers
Post by John Haxby
Hello,
$ git clone git://git.ipxe.org/ipxe.git
Cloning into 'ipxe'...
fatal: read error: Connection reset by peer
I've tried it from a variety of different hosts in different places and I've tried forcing IPv4 instead of IPv6.
Is there something different I should be doing?
I think John did already good work by reporting that git services was
missing.
Where he got 'Connection reset by peer'
do I get 'fatal: Could not read from remote repository.'
If you're going through a proxy you'll get that message. I think older versions of git also report that.
Post by Geert Stappers
Mostly likely is the repair now work in progress
( I don't know, no inside information )
That's what I hoped, but it's been a long time now.

jch
Post by Geert Stappers
Cheers
Geert Stappers
--
$ cd ipxe/
$ git config --list
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.url=git://git.ipxe.org/ipxe.git
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.master.remote=origin
branch.master.merge=refs/heads/master
$ git pull
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
$
_______________________________________________
ipxe-devel mailing list
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Michael Brown
2018-11-14 14:28:05 UTC
Permalink
Post by John Haxby
Post by Geert Stappers
Post by John Haxby
$ git clone git://git.ipxe.org/ipxe.git
Cloning into 'ipxe'...
fatal: read error: Connection reset by peer
I've tried it from a variety of different hosts in different places and I've tried forcing IPv4 instead of IPv6.
Mostly likely is the repair now work in progress
( I don't know, no inside information )
That's what I hoped, but it's been a long time now.
Sorry about that. I don't know why it failed, but a "service xinetd
restart" seems to have fixed the problem.

Michael
John Haxby
2018-11-14 14:45:46 UTC
Permalink
Post by John Haxby
Post by Geert Stappers
Post by John Haxby
$ git clone git://git.ipxe.org/ipxe.git
Cloning into 'ipxe'...
fatal: read error: Connection reset by peer
I've tried it from a variety of different hosts in different places and I've tried forcing IPv4 instead of IPv6.
Mostly likely is the repair now work in progress
( I don't know, no inside information )
That's what I hoped, but it's been a long time now.
Sorry about that. I don't know why it failed, but a "service xinetd restart" seems to have fixed the problem.
Cool. Many thanks.

jch
Michael
Loading...