I guess the answer to this is that : If SSH isnt set up properly on the machine your trying to SSH into, then the jenkins commands will fail.
To test things : ## become the jenkins user: su jenkins -s /bin/bash ## Now try to ssh into the machine , mimicking the method you configured for the slave: ssh root@my_slave If this fails, then you know that the problem isn't necssarily in jenkins, but either 1) sshd configuration on slave OR 2) ssh configuration on the master In this case i think the solutoin was simply that we had to fiddle to allow password based auth on the slave (etc/ssh/sshd_config) , as well as on the master client (/etc/ssh/ssh_config). On Monday, March 17, 2014 7:37:46 PM UTC-4, Jonathan Cope wrote: > > Hello, > > I'm new to Jenkins have some issue getting my jenkins master to connect to > my slave via SSH. > > My setup: > > 1. AWS EC2 instances ( 2 ) - m1.medium > 2. Fedora-x86_64-20-20131211.1-sda - AMI > 3. Jenkins ver. 1.555 > 4. Passwordless Authentication from master to slave > > When I input the credentials > user: jenkins > credentials: master ~/.ssh OR direct ssh key input > > It fails, with the log producing: > > [03/17/14 23:08:24] [SSH] Opening SSH connection to > ec2-000.00.00.000-us-west-2.compute.amazonaws.com:22 > <http://ec2-54-186-69-58.us-west-2.compute.amazonaws.com:22/>. > [03/17/14 23:08:24] [SSH] Authentication failed. > hudson.AbortException: Authentication failed. > at > hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1143) > at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648) > at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > [03/17/14 23:08:24] [SSH] Connection closed. > [03/17/14 23:08:24] Launch failed - cleaning up connection > > > > > I've been trying to diagnose the problem by running a simple job that passes > to the command line: > > > ssh -Tv [email protected]:22 > <http://ec2-54-186-69-58.us-west-2.compute.amazonaws.com:22/> > > or > > ssh -Tv $username@<PRIVATE-IP> > > > where username= root, jenkins, fedora, or no username > > > This method consistently produces: > > > Started by timer > Building on master in workspace /var/lib/jenkins/jobs/test_jenkins/workspace > [workspace] $ /bin/sh -xe /tmp/hudson5026502830242434855.sh > + ssh -Tv slave ls ### or username@slave > OpenSSH_6.4, OpenSSL 1.0.1e-fips 11 Feb 2013 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 51: Applying options for * > debug1: Connecting to slave [##<PRIVATE-IP>##] port 22. > debug1: Connection established. > debug1: identity file /var/lib/jenkins/.ssh/id_rsa type -1 > debug1: identity file /var/lib/jenkins/.ssh/id_rsa-cert type -1 > debug1: identity file /var/lib/jenkins/.ssh/id_dsa type -1 > debug1: identity file /var/lib/jenkins/.ssh/id_dsa-cert type -1 > debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa type -1 > debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa-cert type -1 > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_6.4 > debug1: Remote protocol version 2.0, remote software version OpenSSH_6.3 > debug1: match: OpenSSH_6.3 pat OpenSSH* > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug1: kex: server->client aes128-ctr [email protected] <javascript:> > none > debug1: kex: client->server aes128-ctr [email protected] <javascript:> > none > debug1: sending SSH2_MSG_KEX_ECDH_INIT > debug1: expecting SSH2_MSG_KEX_ECDH_REPLY > debug1: Server host key: RSA # key valuedebug1: read_passphrase: can't open > /dev/tty: No such device or address > Host key verification failed. > Build step 'Execute shell' marked build as failure > Finished: FAILURE > > > Hours of googling have produced myriad posts about this but I haven't found a > single working solution. > > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
