Minor I just upgraded to Jenkins 2.77 on our Windows 7 VM. I have a Jenkins slave agent installed on another windows 7 VM. When I upgraded, the Jenkins web config UI also prompted me to disable 2 deprecated jnlp-2 protocols.However, now it is not possible to start the slave agent from a Windows service. I have to start it by clicking the Launch button in the Jenkins web UI.
After I launched the slave from the web UI, I selected the option in the Java window to install the slave agent as a service. However, when I try to start the slave agent from the service, it says it's started but the Jenkins web UI indicates that it is not started.
I've tried running the slave agent launch command from the command line, by using the command given in the Jenkins UI, and I got the errors indicated in the attached screenshot, relating to jnlp-2 protocol connect errors. So there's a mismatch somewhere, if that command is still looking for the jnlp-2 protocol.
I've also attached the slave.exe file.
- links to
[JENKINS-46760] Jenkins slave agent cannot be run as a service
| Labels | New: winsw |
| Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
| Component/s | New: remoting [ 15489 ] |
The nature of this bug is unclear. The message says:
If newer protocol versions are supported by all system components (agents, CLI and other clients), it is highly recommended to disable the deprecated protocols.
This implies that agents may not support newer protocol versions.
As to the followup problems, probably caused by long outdated slave.jar on the agent. VersionColumn Plugin would help understand whether that's the case.
danielbeck It still needs some better UX. I am about pulling in Version Column plugin as Recommended plugin or integrating its features to the new detached Remoting Support plugin after 1.x.
Thanks for your replies, Oleg and Daniel.
I read the Remoting upgrade notice, but it's not clear to me exactly how I upgrade the slave.jar. Please can you advise how I should do it?
I just upgraded to V2.78. Now the Jenkins web UI displays the following command to launch the slave agent from the command line, where it's now looking for a java file named agent.jar instead of slave.jar:
java -jar agent.jar -jnlpUrl http://dslvm006.mul.ie.ibm.com:8080/computer/Curam_DOC_Production_Slave/slave-agent.jnlp -secret fedfd4cae9303a1afbd458f70b511b85bb0968e478a9d63d100ad7c4f2e10a61
But I can't run the command because I cannot find the agent.jar file anywhere. Where can I get it from, please?
Have you upgraded your Remoting (slave.jar) version as it suggested in the Remoting upgrade notice?
https://jenkins.io/blog/2017/08/11/remoting-update/