Git致命：远程端挂了

Question

So I thought I had finally got everything setup on Windows ... then ran into this issue.

Current setup

URL: ssh://user@host:port/myapp.git

Already run Putty - and can connect using valid .ppk keys through the ~/.ssh/authorized_keys direct. In Git and TortoiseGIT - I set both to use "plink.exe".

Putty works fine - no issues - but when I run that URL into bash I get for a git clone (url)

fatal: the remote end hung up expectedly

In a cygwin bash terminal - running "ssh user@host" - works no probs at all.

Anyone suggest anything?

Answer 1

I found out that using ssh.exe from the Git package works every time, as opposed to the ssh that comes with cygwin (the default). Using this exported variable seems to help; it's slower (2x or more) but it's more stable. Take it as another workaround.

$ export GIT_SSH=/cygdrive/c/Program\\ Files/Git/bin/ssh.exe

FYI: This version of Msysgit comes with OpenSSH 4.6p1, OpenSSL 0.9.8e. [works] Cygwin's SSH is OpenSSH 5.5p1, OpenSSL 0.9.8n. [doesn't work]

Answer 2

I had the same problem with plink for git under windows.

On run of plink.exe -v xxx@host.com it started to show Pageant is running. Requesting keys. Pageant has 1 SSH-2 keys login as: <<< trouble

Instead of Pageant is running. Requesting keys. Pageant has 1 SSH-2 keys Using user "xxx"

To resolve this problem I cleaned up the putty registry records and sessions by putty.exe -cleanup

After that plink starts afresh and asks to trust and store the host again and it is getting connected with no problem !

Answer 3

Try following steps, maybe something will give you a hint on your problem:
1. Run putty and after setting up server name/user name/keys etc. save those settings.
2. Run plink.exe or plinkw.exe like plink.exe user_name@server , (it'll throw some info at you) just to see if plink can connect to the server.
3. Check again that git knows that it should use plink, I'd say with all VCSs, that's the problem people have most often, apart from their keys not being set up properly.
Normally by now most of your ssh problems would be revealed. Now just fix them. :)

Update:

I think the problem you have is caused by several gits you've got installed. For the msysgit and cygwin git you'd need to set the GIT_SSH variable. That's done via either 'set GIT_SSH=c:\\path\\putty\\plink.exe' or 'export GIT_SSH=/your/path/putty/putty.exe' respectively. If you're also using tortoise git, you'd need to locate 'properties' (or is it settings?) in it's menu, and set the ssh client there.
Apart from all that, when specifying git clone URL, use your login name and the server name in there, eg 'git clone ssh://user@server/your/path/repo.git User and server names should be used by plink, and plink should be able to connect to the server with those arguments, when all of those requirements are met, you'll be all set.

Good luck.

Answer 4

If you want to try the cygwin openssh 5.4p1-1, which does seem to work for this, unlike 5.5 or 5.6, you can use the cygwin time machine mirrors. Start setup.exe with -X and add a mirror Url, such as:

ftp://www.fruitbat.org/pub/cygwin/circa/2010/05/20/230133

Be careful not to install too much, ie base packages, from an older mirror than the rest of your install.

Answer 5

We had same problem and here is solution how we solved the problem:

at first we got:

zajdan@cyberFuture:~$ git clone ssh://nette@19X.16X.14X.7X/~repos/erotika.git/ erotika
Initialized empty Git repository in /home/zajdan/erotika/.git/
Password: 
fatal: '/repos/erotika.git': unable to chdir or not a git archive
fatal: The remote end hung up unexpectedly
zajdan@cyberFuture:~$ 

solution:

zajdan@cyberFuture:~$ git clone ssh://nette@19X.16X.14X.7X/~/repos/erotika.git/ erotika

after tilde there must be a slash !

Answer 6

I have exactly the same issue.

I don't use Putty (just Cygwin). I use Windows 7 Ultimate (fully patched as of this moment). I just installed Cygwin yesterday.

I made sure binary mounts were being used.

If I copy a git repo to the machine (via samba mount), I can clone it, but when I "git diff" after the clone, there are a bunch of "different" files with no diffs. After a "git status" there was no output from "git diff". It seems like a newline thing, but I can't figure out how that would be happening. (I have igncr in SHELLOPTS, but removing that doesn't fix it.)

I'm completely stumped.

Answer 7

Check the openssh version you're using in CygWin. Version 5.5p1-1 (which is the latest at this time) gave me the same error. Downgrading to 5.4p1-1 fixed the problem.

Another solution would be to use putty/plink instead of openssh.

For more details, see this thread: http://www.mail-archive.com/cygwin@cygwin.com/msg103752.html

Answer 8

I get message: "remote end gung-up, unexpected EOFs, index-pack failed" while cloning git repo but was able to workaround this issue with copssh http://sourceforge.net/projects/sereds/files/Copssh

The root cause is Cygwin openssh package.

I removed original openssh from Cygwin, installed copssh and set GIT_SSH variable to point copssh binaries. After this I simply added copssh binaries in the PATH and now I'm using copssh instead of openssh - there is no difference.

Everything works fine and issue does not appear any more.

The other solution is to use mSysGit package.

Answer 9

I believe the real problem is that cygwin's ssh looks for .ssh in /home/ name /.ssh and mingw's git ssh looks for .ssh in c:/user/ name /.ssh

Chances are your keys are in one and only one of these directories.

You can trying telling cygwin's .ssh to use a different identity file using the -i switch, or move the keys into both directories, or create an ssh config file in /home/ name /.ssh/config.

I created a config that contains:

Host github.com
    User jerryasher
    Hostname github.com
    IdentityFile c:/Users/jerry/.ssh/id_rsa

And given that I can use either the mingw git from git bash or cygwin's git from an rxvt to interact with github.

Answer 10

To correct this issue, run "plink -agent github.com" Press y when prompted to cache the key. Login as git. You'll automatically be disconnected. And it sould work.

Source: http://devlicio.us/blogs/sergio_pereira/archive/2009/05/06/git-ssh-putty-github-unfuddle-the-kitchen-sink.aspx

Answer 11

Try to use absolute path to repo in a URL, that worked for me.

Instead of:

git ssh://user@host:port/myapp.git

Write:

git ssh://user@host:port//home/user/repo/myapp.git

Notice the double slash!