Hello,
I am attempting to upgrade Jenkins on one of our sandboxes
to the latest LTS version (2.73.2). The issue I have encountered is after
upgrading, our build agents have all lost their connection to the master. I
tried this a couple different ways to find out when the issue starts.
Attempt #1: 2.24 > 2.73.2
- Replace the jenkins.war with the 2.73.2 jenkins.war
- Edit the jenkins.xml to point to JRE 1.8
- Start the Jenkins service
- Jenkins starts up fine, but our three build agents are
offline.
- Replaced the slave.war on build agent #1.
- Verify in the Jenkins-slave.xml points to JRE 1.8 (It
already was)
- Started the agent service. Still does not go online.
- Try to connect via jnlp, but the connection times out.
- Updated all plugins
- Stop/Start the Jenkins service.
- Stop/Start the Jenkins agent service. Agent still
offline.
- Start via jnlp. Connection times out.
Attempt #2: 2.24 > 2.32.3 > 2.46.3 > 2.60.3
- Revert to the original snapshot
- Upgrade to 2.32.3, then to 2.46.3 (Found no issues)
- Replace the jenkins.war with the 2.60.3 jenkins.war
- Edit the jenkins.xml to point to JRE 1.8
- Start the Jenkins service
- Jenkins starts up fine, but our three build agents are
offline.
- Replaced the slave.war on build agent #1.
- Verify in the Jenkins-slave.xml points to JRE 1.8 (It
already was)
- Started the agent service. Still does not go online.
- Try to connect via jnlp, but the connection times out.
Here is the connection timeout error (Same error in both
attempts):
Some additional information:
Master: Windows Server 2008 R2
Agent 1: Windows Server 2008 R2
- I was thinking the random ports would be an issue, since
the jnlp connects using a random port each time, but this is how our Jenkins
has been configured in previous versions and currently in production.
- The issue occurs starting with the upgrade to 2.60.3. Both
versions 2.32.3 and 2.46.3 work fine.
Any help would be appreciated. I can provide any additional
information as needed.
Thank you,
Eddie