Have you checked with the most recent versions of the git-client-plugin and the git-plugin?

I've not seen any issues with remoting failures using my collection of Debian Linux variants (7.1 x86, Testing x64, 7.1 x64) and Windows (Win 7 x86, Windows Home Server 2011 x86, Windows 8.1 x64). They are all running Java 1.7.0_51 as provided by Oracle, though I don't expect any issues related to the provider of the JDK either.

I'm seeing the same behavior on 1.555 with up to date git plugins as of Mar 17. This was working fine and I kept hitting 'rebuild last', and suddenly I got this error. A regular build does not work either.

I was editing the job, so I expect that somehow introduced this. I've seen job configuration get corrupted in the past after repeated saves.

I am currently running Jenkins 1.537, with the following plugins:
Credentials plugin: 1.9.4
SSH Credentials Plugin: 1.6
SSH Slaves Plugin: 1.5
Strictly speaking, I'm not sure any are required other than "SSH Credentials Plugin".

I see that new version(s) are available, both for Jenkins as well as some of these plugins, so I will update and check. But I am still facing this problem.

The Credentials plugin is required with the git-plugin and the git-client-plugin.

I have seen this when a slave is using two sets of ssh credentials at the same time. In my case it was the ssh-agent plugin and the git plugin conflicting. As soon as I got rid of one of them, everything worked again.
YMMV.

Same issue with swarm slaves, no SSH credentials handled via Jenkins. I can restart the master and it will build successfully. We've also had success building before the restart by removing the wildcards from the branches we want the job to build.

This is kind of a painful one. Is there any other info we could provide that would help find a solution?

Thanks!

blewa have you tried the suggestions listed earlier (confirm you're only using one set of ssh credentials, confirm the slave jar matches your Jenkins version, etc.)?

Swarm slaves may also have an additional complexity because I believe they embed a copy of slave.jar in the swarm jar file. You might do a test drive with one of your swarm slaves and switch it temporarily to use Java web start or ssh to launch the slave. If that shows a different behavior, then your case may indicate that the swarm jar needs an update.

I just upgraded our swarm jar and haven't seen an issue in a few builds, but I'll keep an eye on it. We went from version 1.09 to version 1.20 (didn't realize it'd been updated so much between now and then).

Thanks for the tip!

Since I can't duplicate it and the comments on the bug have been quiet for over a month, I'm closing this bug as "Cannot Reproduce".

I maybe find the reason for this error. In my test bed, I have encounter the same problem that error likes the follows, when I build my jenkins project.

FATAL: java.io.IOException: Remote call on <a-slave-host> failed
hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on <a-slave-host> failed
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:195)
at com.sun.proxy.$Proxy75.addCredentials(Unknown Source)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl.addCredentials(RemoteGitImpl.java:197)
at hudson.plugins.git.GitSCM.createClient(GitSCM.java:662)
at hudson.plugins.git.GitSCM.createClient(GitSCM.java:638)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:978)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1265)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1718)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: java.io.IOException: Remote call on rpmbuild-172.16.102.46 failed
at hudson.remoting.Channel.call(Channel.java:760)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179)
... 14 more

At first, my jenkins project had fill the Git Repository URL with a type of Credentials. And I have put the <a-slave-host>'s id_rsa.pub which location '/root/.ssh/' to my gitlab server with 'Add SSH Key' operation.

So you may known that the real reason. After above build errors, I set the Git Credentials to none by the jenkins server WEBUI for my project configure. Then I build the project successful. Without comment, we can get a conclusion that the multiple credential types for gitlab server is the real reason. So you known how to deal with the problem too.

Thanks all.