[JIRA] [remoting] (JENKINS-26559) EC2 slaves not connecting

[st...@donie.us (JIRA)]

Steve Donie commented on JENKINS-26559 EC2 slaves not connecting I manually SSH'd to the slave machine, changed to the root directory, and then listed the files there. There was no slave.jar listed. I then ran this command in the root dir: wget http://mybuildserver/jnlpJars/slave.jar which downloaded the jar as expected. Finally I went back to the build server web UI, selected the node in Build Executor status, and selected 'Launch slave agent' - success! ... java full version "1.7.0_51-b13" Copying slave.jar Launching slave agent: java -jar /slave.jar <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.49 This is a Unix slave Evacuated stdout Slave successfully connected and online So it appears that the location the slave.jar is copied and the location that is used to launch it are not the same, and it appears to be launching it expecting it to be in the root.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.