tags:

views:

68

answers:

3
MacMini $ git push origin master
Counting objects: 1916, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (1751/1751), done.
Read from remote host codebasehq.com: Operation timed out   
fatal: The remote end hung up unexpectedly
error: pack-objects died of signal 13
error: pack-objects died with strange error
error: failed to push some refs to '[email protected]:xx/xx/xx.git'
A: 

Have you tried getting to the bottom of :

Read from remote host codebasehq.com: Operation timed out

?

Konrad
A: 

Looks like you have a bad network connection. Can you access codebasehq.com, especially with the network protocol you use. Have you a correct proxy server configuration? Can you pull other projects?

Rudi
Yes. I can push other projects upto codebasehq.com... it's just a few that are causing problems...
Simon
Semms like a timeout or some weired data patterns. Is this always at the same position or at the same time? You might try to look at the data stream with wireshark or tcpdump to see if there is any suspicious.
Rudi
Yes. It always happens at one specific point... is there verbose git command that would identify the rejected file?
Simon
A: 

Contemporary UTM firewalls can mess with outgoing data if they falsely identify traces of malware, packed data, or insecure commands in the stream... and these false alarms happen pretty frequently. Such security devices on your network or the destination side could explain why some projects push up okay and others are dropping the connection.

If that's the case, you may avoid the trigger if you use a different protocol for this connection, e.g. ssh:// or https:// instead of git://.

ewall