Did you check the same settings as were mentioned earlier in this
discussion?
Otherwise, you would need to provide additional details such as
versions, changes, etc., for anyone to have a chance of helping you.
Jeff
On 2/17/20 7:47 AM, Sat wrote:
I am facing the same issue today.
For Jenkins agent : TCP port for inbound agent. - fixed 8020 port
I used the same like below:
docker run jenkinsci/jnlp-slave -url http://jenkins-master.test:8020
-workDir=/home/jenkins/agent
pkRUdAH07VFHhSWb9RAQCRFdWP7j0eIx9jfhRhj5jenkins-agent
but still seeing issue:
Feb 17, 2020 2:45:58 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: http://jenkins-master.test:8020/tcpSlaveAgentListener/ is
invalid: 404 Not Found
java.io.IOException:
http://jenkins-master.test:8020/tcpSlaveAgentListener/ is invalid: 404
Not Found
Can you let me know how to fix this, thanks.
On Wednesday, April 11, 2018 at 4:12:23 PM UTC+1, john.peterson wrote:
Legacy systems (3+ years) running 2.111
http://jenkins_1:8080/tcpSlaveAgentListener
<http://jenkins_1:8080/tcpSlaveAgentListener> takes us to a page
that simply says Jenkins. This system works.
http://jenkins_2:8080/tcpSlaveAgentListener
<http://jenkins_2:8080/tcpSlaveAgentListener> takes us to a page
that simply says Jenkins. This system works.
http://jenkins_3:8080/tcpSlaveAgentListener
<http://jenkins_3:8080/tcpSlaveAgentListener> takes us to a page
that simply says Jenkins. This system works.
New system running 2.107
http://jenkins_4:8080/tcpSlaveAgentListener
<http://jenkins_4:8080/tcpSlaveAgentListener> says Page Not Found
This is the first time I've had trouble getting a slave to connect.
I've checked to make sure all of the plugins are there and the
same as on the other systems.
My VM is a clone from System2. I updated my "slave launch" batch
file from
javaws
http://jenkins_2:8080/computer/VM01_Win7x64/slave-agent.jnlp
<http://jenkins_2:8080/computer/VM01_Win7x64/slave-agent.jnlp>
to
javaws
http://jenkins_4:8080/computer/VM01_Win7x64/slave-agent.jnlp
<http://jenkins_4:8080/computer/VM01_Win7x64/slave-agent.jnlp>
When I run that command on the slave I get:
Apr 11, 2018 10:13:33 AM hudson.remoting.jnlp.GuiListener$2 run
SEVERE: http://jenkins_4:8080/tcpSlaveAgentListener/
<http://jenkins_4:8080/tcpSlaveAgentListener/> is invalid: 404 Not
Found
java.io.IOException: http://jenkins_4:8080/tcpSlaveAgentListener/
<http://jenkins_4:8080/tcpSlaveAgentListener/> is invalid: 404 Not
Found
at
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:204)
at hudson.remoting.Engine.innerRun(Engine.java:518)
at hudson.remoting.Engine.run(Engine.java:469)
I am the one that set up all 4 systems. Doing side-by-side
comparisons, everything seems the same. I have entered firewall
exceptions (or turned off). I have the same JAVA on all. I have
added exceptions in JAVA as appropriate.
The only diagnostics I can find is from CloudBees and only
semi-applies to what I am trying to diagnose.
--
You received this message because you are subscribed to the Google
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/c8dde335-05be-4c94-a365-beea095be132%40googlegroups.com
<https://groups.google.com/d/msgid/jenkinsci-users/c8dde335-05be-4c94-a365-beea095be132%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/9c2154a9-b49d-4423-8358-baa19fb8469d%40cloudbees.com.
