Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We are using Mercurial over SSH for our development. We use Hudson for continous integration, and have deployed it on Tomcat, running on a Windows 2003 Server using the Local System account. Mercurial is configured to use Putty's plink.exe as its ssh command in Mercurial.ini, together with a private key for SSH authentication.

When Hudson attempts any Mercurial command over SSH, the operation just blocks. I can see the three processes being started: hg.exe, cmd.exe and plink.exe. On the remote machine, I can also see the SSH session being opened and the authentication key being accepted.

After that, nothing appears to happen, and everything just blocks, seemingly forever. (As a side note, subversion/SVN over SSH works from Hudson to the same server, using the same user and authentication key).

A solution would of course be the best, but at least a hint for how I should debug it to get further would be nice, since I'm stuck and haven't even got an error message right now.

share|improve this question

3 Answers 3

Could it be that the key is password protected? Mercuiral's wiki has some suggestions if that is the case. Mainly they suggest either a) using TortoisePlink or b) using pageant

Check out: http://mercurial.selenic.com/wiki/AccessingSshRepositoriesFromWindows

share|improve this answer

If something like that happens, always try it manually with the same user account. Try to keep as much as possible the same compared to what Hudson tries. The output will tell you what is the actual problem. Usually it is something like a certificate that you need to accept. If you need to accept a certificate use Quest's plink which is an extended version of putty plink.

share|improve this answer
    
This is good advice, and basically what we tried. The issue was that the user running Tomcat (and thus also Hudson) hadn't accepted the SSH server fingerprint. Problem was getting Windows to allow us to get a shell to the user in question. We had to use some Windows power tool to get that access. –  Liedman Aug 27 '10 at 11:57

Use psexec from Sysinternals (http://download.sysinternals.com/files/PSTools.zip) to run as System account.

This

psexec -i -s cmd.exe

gives you a cmd shell as the local system user.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.