JNLP agent startup not working after upgrade from 2.4x to 2.89.4

30 views
Skip to first unread message

Dan zaWhite

unread,
Mar 5, 2018, 4:00:47 AM3/5/18
to Jenkins Users
This is what i did:

1. Upgrade jenkins to latest and greatest
2. Upgrade plugins
3. Sanitize a windows 2012 R2 slave from the old jenkins slave installation
4. Upgrade java jre to java 8 on the slave
4. Trying to connect the same slave again via the slave-agent.jnlp file

The slave does not start at all :(

Anyone had this issue ?
Did i forgot to do something?

Thank you,
Dan 


Victor Martinez

unread,
Mar 5, 2018, 5:00:10 AM3/5/18
to Jenkins Users

https://jenkins.io/doc/upgrade-guide/ might help you out regarding what changes were published between 2.4X and 2.89.4


Ivan Fernandez Calvo

unread,
Mar 5, 2018, 2:53:10 PM3/5/18
to Jenkins Users
Did you replace the slave.jar?
Did you try to uninstall the service and install it again?


Also take a look at this page https://github.com/jenkinsci/windows-slave-installer-module/blob/master/README.md

Dan zaWhite

unread,
Mar 6, 2018, 1:52:48 AM3/6/18
to Jenkins Users
I sanitized the machine completely.

I was expecting that the java webapp will launch with no problems.
Will test also today with a fresh windows machine and see if i can reproduce the issue.

For now i just updated manually the ws installer and config file and reinstalled the jenkins service for the production machines.

Dan zaWhite

unread,
Mar 6, 2018, 6:10:29 AM3/6/18
to Jenkins Users
I managed to reproduce the problem.

Take a brand new windows 2012 machine and install java jre 8u161 on it.
Run the jnlp file and it will not run...

Other slaves that got upgraded to java 8 don't reproduce.

Is this a regression on the jenkins side maybe?

Dan zaWhite

unread,
Mar 6, 2018, 10:08:23 AM3/6/18
to Jenkins Users
Ok found the issue.

NOTE: For anyone else having issues similar to this...triple check the version of java to be 64 bit...not 32 bit, also never reuse legacy machines....
Reply all
Reply to author
Forward
0 new messages