gogs: ssh_exchange_identification: read: Connection reset by peer
- Gogs version (or commit ref): Gogs Version: 0.9.132.0201 (gogs/gogs:develop [docker])
- Git version: 2.6.6
- Operating system: Docker on Debian Jessie
- Container network settings: 0.0.0.0:2222->22/tcp, 0.0.0.0:3001->3000/tcp
- Database (use
[x]
):- PostgreSQL
- MySQL
- SQLite
- Can you reproduce the bug at https://try.gogs.io:
- Yes (https://try.gogs.io/s0urce-puppet)
- No
- Not relevant
- Log gist:
Description
Hi I have the following problem:
Sometimes, when cloning or pulling repositories the checkout fails.
I am using myrepos
to checkout or update several repositorys with one command. I also use r10k/g10k in puppet which checks out repositories in order to create the environments. The error occurs with r10k as well.
This problem is kind of difficult to reproduce.
Here is the .mrconfig I use to clone the repositories: https://try.gogs.io/carazzim0/myrepos
So I have 10 repositories and if I check them all out by mr up
sometimes the checkout fails with ssh_exchange_identification: read: Connection reset by peer
This does NOT happen everytime I checkout a repository, only sometimes.
This behaviour occurs on my selfhosted Gogs version as well as on try.gogs.io with different repos everytime it happens.
Example output:
mr up
mr update: /home/dev/gogs_debug/test7
ssh_exchange_identification: read: Connection reset by peer
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
mr update: command failed
mr update: /home/basti/dev/gogs_debug/test1
Already up-to-date.
mr update: /home/basti/dev/gogs_debug/test6
Already up-to-date.
mr update: /home/basti/dev/gogs_debug/test8
Already up-to-date.
mr update: /home/basti/dev/gogs_debug/test5
Already up-to-date.
mr update: /home/basti/dev/gogs_debug/test4
Already up-to-date.
mr update: /home/basti/dev/gogs_debug/test2
Already up-to-date.
mr update: /home/basti/dev/gogs_debug/test10
Already up-to-date.
mr update: /home/basti/dev/gogs_debug/test9
Already up-to-date.
mr update: /home/basti/dev/gogs_debug/test3
Already up-to-date.
mr update: finished (9 ok; 1 failed)
I hope you can help me with this kind of “bug” or whatever causes this.
cheers and thanks, carazzim0 …
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 18 (9 by maintainers)
Commits related to this issue
- Fix #4081 Check for leading / in base before removing it (#4083) — committed to Martchus/gogs by sapk 6 years ago
- Fix #4081 Check for leading / in base before removing it (#4082) — committed to Martchus/gogs by sapk 6 years ago
I updated as well and cannot reproduce this anymore. Thanks alot.
And if @sbrl cannot reproduce this as well, I’ll close this asap.
@Unknwon I’ve just done
git push
in a loop 50 times, and every single one has come back clean. I’ll do some real-world testing - if you don’t hear anything, then it’s all ok 😃Ok I’ve got an update on this. I manually downloaded the go binaries from https://golang.org/dl/ and installed
go version go1.7.5 linux/amd64
on my workstation and recompiled gogs there.When I now run
for i in {1..200}; do git pull > /dev/null; done
there are no errors anymore.So https://github.com/golang/go/issues/18711 seems to be fixed in 1.7.5