Looks to me like your git server is simply overloaded. Run a h/top/"vmstat
-n 1" on it in a different window and only retry the push when CPU usage on
the server drops below 50%.

Advertising

If the push never succeeded I would've expected invalid ssh/git
credentials...
You might also want to check your network/firewall settings. If your
network does some ugly form of traffic shaping, it could unexpectedly kill
your TCP connection for git push. Otherwise, you may simply lack the
bandwidth, which may as well be causing your TCP connections to timeout.
Posting the output of the "git remote show origin" command on your system
(not necessarily the full URL paths) could also help someone provide a
better answer than this.
These are just some possibilities, hope you find the true cause by starting
with these...
Ştefan Szabó
marți, 22 mai 2012, 14:17:05 UTC+3, Thorsten Peters a scris:
>
> Any ideas?
>
> We try different things, but nothing works.
> Same push, x times hang up, than it works finde.
>
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/git-users/-/p08wWF1sISYJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/git-users?hl=en.