Slaves not connecting after recent plugin upgrades (None of the protocols were accepted)

199 views

Skip to first unread message

Steve K

unread,

Jul 15, 2016, 4:40:26 PM7/15/16

to Jenkins Users

Hello,

The Jenkins server is Win 8.1 and one of the slaves having problems is Win 8.1
Jenkins version is 1.625.3
I just upgraded a bunch of plugins, including Windows Slaves Plugin 1.1 (previous 1.0) and SSH Slave plugin 1.11 (previous 1.9).
I upgraded others as well, but those are slave-specific, so they are suspect.

One of the errors we see is "java.lang.Exception: The server rejected the connection: None of the protocols were accepted".

I've tried deleting and re-adding the slave.
I've upgraded Java on the slave to 1.8.0_91 (server uses the jre in the Jenkins dir which is 1.8.0_20-b26).

Does anyone have any ideas? I don't want to resort to backup quite yet.

Thank you.

Steve K.

Steve K

unread,

Jul 18, 2016, 10:41:59 AM7/18/16

to Jenkins Users

Update: After reverting the Windows Slaves Plugin back to v1.0 and SSH Slave plugin back to v1.9, I was able to re-connect
my slaves.
I have a residual problem that, on one of the slaves, I am not able to install it as a service. I'm able to run it from the command line with
`java -jar slave.jar -jnlpUrl http://* `
I suspect that my Java upgrade affected my ability to install as a service. I don't know yet what the complaint is, because, when I click on the slave-agent.jnlp, the command window pops up for a moment, and then disappears.
Any ideas?

On Friday, July 15, 2016 at 4:40:26 PM UTC-4, Steve K wrote: