In case anyone comes across this in web searches, I've tried many different 
things, and now suspect that using an OSX master with ssh slaves may simply not 
be a workable configuration, for unknown reasons. I've seen plenty of reports 
that it does work well with a Linux master, so that is my intent, and my 
suggestion to anyone in my situation.

--
Todd

From: Todd Greer
Sent: Friday, May 17, 2013 2:48 PM
To: 'jenkinsci-users@googlegroups.com'
Subject: Unable to start ssh slave from OSX master

I'm trying to use the ssh slave plugin (v.21) from OSX, and have been unable to 
get it to initiate the ssh connection. The node is configured with the username 
and password, using the default port (which is correct). From a manual 
connection, there is an entry for the slave node in ~/.ssh/known_hosts.

Other types of slave nodes are fine.

When I try to start the node, or to look at the node's logs, I just get a 
spinner. In Jenkins's logs, I see "Excess workload 1.0 detected. (planned 
capacity=0.0,Qlen=0.99999976,idle=0.0&0,total=0m,=0.5)". In system.log, I see 
"Attempting to reconnect <node-name>". Other than that, I see no signs of 
activity, including in the slave node's auth log.

Can anyone provide me with guidance on where to look next?

Thank you,
Todd

--
Todd Greer
Principal Scientist, Affinegy, Inc.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to