Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Labels:None
-
Environment:Jenkins 2.1.129
-
Similar Issues:
-
Released As:Jenkins 2.130, Remoting 3.23
Description
Jenkins Windows Agent failed to start after upgrade to version 2.1.129: Jenkins is running behind apache reverse proxy on different host that proxy itself. Parameter “tunnel connection through” is set correctly. From the error message we can see that remote agent was trying to connect to reverse proxy host instead of Jenkins master host.
The version 2.1.128 works without issues.
Attachments
Issue Links
- relates to
-
-
- Resolved
-
-
-
- Open
-
- links to
Activity
You do it right, and it works: I found my error and placed the option in front of jenkins.jar. Now Windows slave is accessible again.
Dzianis Mazuronak
added a comment - You do it right, and it works: I found my error and placed the option in front of jenkins.jar. Now Windows slave is accessible again. Agreed. I had to modify the Jenkins startup script for the define (-D) to take effect. It appears you can't use the Jenkins console to make the change, even though it showed up in the Jenkins System Information page.
Since I run on Linux Mint (Ubuntu derivative) I modified the file /etc/defaults/jenkins, JAVA_ARGS line, to add the -D as described above. My final line looks like (the first -D... was already there):
JAVA_ARGS="-Djava.awt.headless=true -Dhudson.TcpSlaveAgentListener.hostName=j-jenkins"
Chris Rule
added a comment - Dzianis Mazuronak :
Agreed. I had to modify the Jenkins startup script for the define (-D) to take effect. It appears you can't use the Jenkins console to make the change, even though it showed up in the Jenkins System Information page.
Since I run on Linux Mint (Ubuntu derivative) I modified the file /etc/defaults/jenkins, JAVA_ARGS line, to add the -D as described above. My final line looks like (the first -D... was already there):
JAVA_ARGS= "-Djava.awt.headless= true -Dhudson.TcpSlaveAgentListener.hostName=j-jenkins"
Remoting 3.23 is out. Created https://github.com/jenkinsci/jenkins/pull/3530
No need to backport the fix, it won't get into LTS
See my comment in https://github.com/jenkinsci/remoting/pull/279 . After the review, this issue happens IFF "-tunnel" is set. I believe that "-tunnel" flag should be deprecated and replaced by offering a custom port in TcpAgentListener response headers like it's already done for hosts
So I propose to just disable checks in that case if Andrei Laptsinski agrees. We could implement a more advanced behavior and checks for tunnel options as a part of JENKINS-52246.