Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

2020-02-19 Thread Sat 
Hi,
The issue has been resolved now, thanks.


On Monday, February 17, 2020 at 6:11:27 PM UTC, Sat wrote:
>
> hi,
> Thanks for reply.
> I am using an EC2 machine as master and spin up a fargate instance as 
> slave.
> Both are in same VPC and subntes.
>
> The error I am seeing when I try to run from command line.
> Let me know if you need any more details, thanks.
>
>
>
> On Monday, February 17, 2020 at 5:25:10 PM UTC, Jeff Thompson wrote:
>>
>> 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 pkRUdAH07VFHhSWb9RAQCRFdWP7j0eIx9jfhRhj5  
>> jenkins-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 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 jenkins...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/c8dde335-05be-4c94-a365-beea095be132%40googlegroups.com
>>  
>> 
>> .
>>
>>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1707af86-abe1-43fc-abf3-612eee7bdae7%40googlegroups.com.

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

2020-02-17 Thread Sat 
hi,
Thanks for reply.
I am using an EC2 machine as master and spin up a fargate instance as slave.
Both are in same VPC and subntes.

The error I am seeing when I try to run from command line.
Let me know if you need any more details, thanks.



On Monday, February 17, 2020 at 5:25:10 PM UTC, Jeff Thompson wrote:
>
> 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 pkRUdAH07VFHhSWb9RAQCRFdWP7j0eIx9jfhRhj5  
> jenkins-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 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 jenkins...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/c8dde335-05be-4c94-a365-beea095be132%40googlegroups.com
>  
> 
> .
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4cb60c42-0b6e-4bf9-a4ea-97d02d8c31bb%40googlegroups.com.

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

2020-02-17 Thread Jeff Thompson 
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
 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 jenkinsci-users+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c8dde335-05be-4c94-a365-beea095be132%40googlegroups.com 
.


--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9c2154a9-b49d-4423-8358-baa19fb8469d%40cloudbees.com.

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

2020-02-17 Thread Sat 
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 pkRUdAH07VFHhSWb9RAQCRFdWP7j0eIx9jfhRhj5  
jenkins-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 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c8dde335-05be-4c94-a365-beea095be132%40googlegroups.com.

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

2018-04-11 Thread Daniel Beck 

> On 11. Apr 2018, at 17:36, john.peterson  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 jenkinsci-users+unsubscr...@googlegroups.com.
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.

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

2018-04-11 Thread 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
>
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
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.

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

2018-04-11 Thread Daniel Beck 
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  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 jenkinsci-users+unsubscr...@googlegroups.com.
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
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.

Re: Slave cannot connect to Jenkins via tcpSlaveAgentListener

2018-04-11 Thread 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
>
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
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.

Slave cannot connect to Jenkins via tcpSlaveAgentListener

2018-04-11 Thread 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 jenkinsci-users+unsubscr...@googlegroups.com.
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.