Problem with runnig Jenkins Slave using ssh key

[Stefan Gehrig]

Hi

I can't manage to run a slave jenkins job on SUSE SLES 12. I got the error:

[05/06/16 11:51:12] [SSH] Opening SSH connection to pnsapp01-x:22.
Key exchange was not finished, connection is closed.
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.
java.lang.IllegalStateException: Connection is not established!
	at com.trilead.ssh2.Connection.getRemainingAuthMethods(Connection.java:1030)
	at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.getRemainingAuthMethods(TrileadSSHPublicKeyAuthenticator.java:88)
	at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.canAuthenticate(TrileadSSHPublicKeyAuthenticator.java:80)
	at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:207)
	at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:169)
	at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1212)
	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:711)
	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
[05/06/16 11:51:12] Launch failed - cleaning up connection
[05/06/16 11:51:12] [SSH] Connection closed.

First of all, here what I already did or have:

I got serveral other Slave Jobs to SLES 11, which are working fine. Same ssh key.
I checked the ssh key and it fits (compared to the other running slaves).
I managed to open a ssh connection manually with "ssh user@server" via ssh key to SLES 12. So it rather can't be something in ssh.config or sshd.config, I asume. Also the firewall must be open. Let's say SSH is generally working fine via ssh key.
I "patched" JAVA with "Java Cryptography Extension (JCE) Unlimited Strength" on both, master and slave. Java version is 1.8.0_92. I made a test with TestJCE and got JCE Supported=true on both, master and slave.
Still no success.
I updated all Jenkins Plugins. My Jenkins version is 1.642.3.
I'm really running out of what I can try next.

Does anyone have an idea?

Cheers
Stefan

[Александр Калюжный]

Hello.

I have the same problem(also checked keys/jce), did you find solution?

[sekar]

Hi, Did you find any solution. please share if you have solutions. thank you- chandru

[Björn Pedersen]

Probably you need to generate new ssh keys:
https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#fate-315806

1024bit DSA key are disabled.

Björn

[Vinod Jambhulkar]

I run into a same problem when trying to use VM as a node. I use IP address instead of alias and my node connected and online.

On Friday, May 6, 2016 at 4:10:10 PM UTC+5:30, Stefan Gehrig wrote:

[Vinod Jambhulkar]

can you try mentioning ip address in place of servername. I can across same issue when I was using VM as a node.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/932b978f-e767-4bee-8eb5-31b8cbb9fff9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.