Slave cannot connect to Jenkins via tcpSlaveAgentListener

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Slave cannot connect to Jenkins via tcpSlaveAgentListener

john.peterson
Legacy systems (3+ years) running 2.111

http://jenkins_1:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.
http://jenkins_2:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.
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 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
to
javaws 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/ is invalid: 404 Not Found
java.io.IOException: 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7ebbd44b-36a0-4d6f-ba86-3bcc0159ac00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

john.peterson
Java 1.8 144 by the way which is in use across the board on all systems.



On Wednesday, April 11, 2018 at 11:12:23 AM UTC-4, john.peterson wrote:
Legacy systems (3+ years) running 2.111

<a href="http://jenkins_1:8080/tcpSlaveAgentListener" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_1%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGE7hUAajg6GcvCpnpj9qSIjhiEjQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_1%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGE7hUAajg6GcvCpnpj9qSIjhiEjQ&#39;;return true;">http://jenkins_1:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.
<a href="http://jenkins_2:8080/tcpSlaveAgentListener" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_2%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE883aRC9yP8NQ2ObIXSz77DjmDzw&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_2%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE883aRC9yP8NQ2ObIXSz77DjmDzw&#39;;return true;">http://jenkins_2:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.
<a href="http://jenkins_3:8080/tcpSlaveAgentListener" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_3%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFe5XowkMZ1vxUMq8240e8f5QrGkg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_3%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFe5XowkMZ1vxUMq8240e8f5QrGkg&#39;;return true;">http://jenkins_3:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.

New system running 2.107
<a href="http://jenkins_4:8080/tcpSlaveAgentListener" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEwNbPZo-EGXri2fQt-lUpSw9a5Gg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEwNbPZo-EGXri2fQt-lUpSw9a5Gg&#39;;return true;">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 <a href="http://jenkins_2:8080/computer/VM01_Win7x64/slave-agent.jnlp" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_2%3A8080%2Fcomputer%2FVM01_Win7x64%2Fslave-agent.jnlp\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEHxocE5FF-LKbflNYIh50s3FhxUg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_2%3A8080%2Fcomputer%2FVM01_Win7x64%2Fslave-agent.jnlp\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEHxocE5FF-LKbflNYIh50s3FhxUg&#39;;return true;">http://jenkins_2:8080/computer/VM01_Win7x64/slave-agent.jnlp
to
javaws <a href="http://jenkins_4:8080/computer/VM01_Win7x64/slave-agent.jnlp" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2Fcomputer%2FVM01_Win7x64%2Fslave-agent.jnlp\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEzThwfzY3d2-ydVasuZXejaF4RAg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2Fcomputer%2FVM01_Win7x64%2Fslave-agent.jnlp\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEzThwfzY3d2-ydVasuZXejaF4RAg&#39;;return true;">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: <a href="http://jenkins_4:8080/tcpSlaveAgentListener/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGkgW1wlCO-bJ_MJbVUBt8o2wJUKQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGkgW1wlCO-bJ_MJbVUBt8o2wJUKQ&#39;;return true;">http://jenkins_4:8080/tcpSlaveAgentListener/ is invalid: 404 Not Found
java.io.IOException: <a href="http://jenkins_4:8080/tcpSlaveAgentListener/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGkgW1wlCO-bJ_MJbVUBt8o2wJUKQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGkgW1wlCO-bJ_MJbVUBt8o2wJUKQ&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0db0e619-4ea4-493d-8f2b-64a23363d19c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

Daniel Beck
In reply to this post by john.peterson
Is the TCP agent listener port in the global security config of Jenkins disabled on the fourth system?

> On 11. Apr 2018, at 17:12, john.peterson <[hidden email]> wrote:
>
> Legacy systems (3+ years) running 2.111
>
> http://jenkins_1:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.
> http://jenkins_2:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.
> 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 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
> to
> javaws 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/ is invalid: 404 Not Found
> java.io.IOException: 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7ebbd44b-36a0-4d6f-ba86-3bcc0159ac00%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6DC1B137-2466-4AB1-9F64-E5A19AAC8EB5%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

john.peterson
In reply to this post by john.peterson
&#$% I missed one stupid setting.  All the others are fixed 9192 or something like that.  I set this the same and Voila!

Thanks

Is this a change in setup defaults?

BTW - this system is only showing "stable" updates for Jenkins.  All others are showing ALL updates (which I actually prefer).  Is there a way to change that?

On Wednesday, April 11, 2018 at 11:12:23 AM UTC-4, john.peterson wrote:
Legacy systems (3+ years) running 2.111

<a href="http://jenkins_1:8080/tcpSlaveAgentListener" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_1%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGE7hUAajg6GcvCpnpj9qSIjhiEjQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_1%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGE7hUAajg6GcvCpnpj9qSIjhiEjQ&#39;;return true;">http://jenkins_1:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.
<a href="http://jenkins_2:8080/tcpSlaveAgentListener" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_2%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE883aRC9yP8NQ2ObIXSz77DjmDzw&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_2%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE883aRC9yP8NQ2ObIXSz77DjmDzw&#39;;return true;">http://jenkins_2:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.
<a href="http://jenkins_3:8080/tcpSlaveAgentListener" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_3%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFe5XowkMZ1vxUMq8240e8f5QrGkg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_3%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFe5XowkMZ1vxUMq8240e8f5QrGkg&#39;;return true;">http://jenkins_3:8080/tcpSlaveAgentListener takes us to a page that simply says Jenkins.  This system works.

New system running 2.107
<a href="http://jenkins_4:8080/tcpSlaveAgentListener" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEwNbPZo-EGXri2fQt-lUpSw9a5Gg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEwNbPZo-EGXri2fQt-lUpSw9a5Gg&#39;;return true;">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 <a href="http://jenkins_2:8080/computer/VM01_Win7x64/slave-agent.jnlp" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_2%3A8080%2Fcomputer%2FVM01_Win7x64%2Fslave-agent.jnlp\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEHxocE5FF-LKbflNYIh50s3FhxUg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_2%3A8080%2Fcomputer%2FVM01_Win7x64%2Fslave-agent.jnlp\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEHxocE5FF-LKbflNYIh50s3FhxUg&#39;;return true;">http://jenkins_2:8080/computer/VM01_Win7x64/slave-agent.jnlp
to
javaws <a href="http://jenkins_4:8080/computer/VM01_Win7x64/slave-agent.jnlp" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2Fcomputer%2FVM01_Win7x64%2Fslave-agent.jnlp\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEzThwfzY3d2-ydVasuZXejaF4RAg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2Fcomputer%2FVM01_Win7x64%2Fslave-agent.jnlp\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEzThwfzY3d2-ydVasuZXejaF4RAg&#39;;return true;">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: <a href="http://jenkins_4:8080/tcpSlaveAgentListener/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGkgW1wlCO-bJ_MJbVUBt8o2wJUKQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGkgW1wlCO-bJ_MJbVUBt8o2wJUKQ&#39;;return true;">http://jenkins_4:8080/tcpSlaveAgentListener/ is invalid: 404 Not Found
java.io.IOException: <a href="http://jenkins_4:8080/tcpSlaveAgentListener/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGkgW1wlCO-bJ_MJbVUBt8o2wJUKQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins_4%3A8080%2FtcpSlaveAgentListener%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGkgW1wlCO-bJ_MJbVUBt8o2wJUKQ&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0b116bbf-38e5-436a-b959-8c46c0352b8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

Daniel Beck

> On 11. Apr 2018, at 17:36, john.peterson <[hidden email]> wrote:
>
> Is this a change in setup defaults?

Since Jenkins 2.0 in 2016, and its introduction of the setup wizard.

> BTW - this system is only showing "stable" updates for Jenkins.  All others are showing ALL updates (which I actually prefer).  Is there a way to change that?

Manage Jenkins » Manage Plugins » Advanced, compare URLs there. Change as desired, submit, and 'Check Now' to flush the cache.

You should generally use https://updates.jenkins.io/update-center.json as Jenkins will send its current version, and the update server will forward to the most appropriate update information.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/83AA9E4C-5C3F-4E7E-A699-D36B1830E70E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.