[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave

[mohit.saraf@ampf.com (JIRA)]

Mohit Saraf created an issue

Jenkins / JENKINS-55689 Not able to connect to jenkins master from windows slave Issue Type: Bug Assignee: Emilio Escobar Components: windows-slaves-plugin Created: 2019-01-18 21:50 Environment: Jenkins Version: 2.150.1 Master is running in Docker Container in DC/OS (Mesos) environment. web browser: chrome Priority: Critical Reporter: Mohit Saraf Hi Team, we are running jenkins master as docker container in DC/OS environment.  we have two ports available for setting up the configuration.  container port 8080 is mapped to service port 29XXXfor jenkins. container port 50000 is mapped to service port  29XXX for jenkins-agent. I have configured the jenkins-agent port in manage Jenkins->Global Security->TCP port for JNLP agents. and also tried to give the default port and multiple random ports but while running the agent i get the error as port is not reachable. SEVERE: https://develop.qa.ampf.com/jenkins/ provided port:41172 is not reachable java.io.IOException: https://develop.qa.ampf.com/jenkins/ provided port:41172 is not reachable at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474) Suppressed: java.io.IOException: http://develop.qa.ampf.com/jenkins/tcpSlaveAgentListener/ is invalid: 302 Found at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:201) ... 2 more   Any suggestions would be really helpful       Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[mohit.saraf@ampf.com (JIRA)]

Mohit Saraf updated an issue

Jenkins / JENKINS-55689 Not able to connect to jenkins master from windows slave

Change By: Mohit Saraf Attachment: jenkins-error.PNG

Add Comment

[mohit.saraf@ampf.com (JIRA)]

Mohit Saraf commented on JENKINS-55689

Re: Not able to connect to jenkins master from windows slave Hi Team, Any suggestions?

Add Comment

[mohit.saraf@ampf.com (JIRA)]

Mohit Saraf updated an issue

Jenkins / JENKINS-55689

Not able to connect to jenkins master from windows slave

Change By: Mohit Saraf Priority: Critical Blocker

Add Comment

[mohit.saraf@ampf.com (JIRA)]

Mohit Saraf updated an issue

Jenkins / JENKINS-55689 Not able to connect to jenkins master from windows slave Change By: Mohit Saraf

Hi Team, we are running jenkins master as docker container in DC/OS (mesos) environment.  we have two ports available for setting up the configuration.

container port 8080 is mapped to service port 29XXXfor jenkins. container port 50000 is mapped to service port  29XXX for jenkins-agent.

I have configured the jenkins-agent port in manage _Jenkins->Global Security->TCP port for JNLP agents_. and also tried to give the default port and multiple random ports but while running the agent i get the error as port is not reachable. SEVERE: [ https://develop.qa.ampf.com/jenkins/ ] provided port:41172 is not reachable java.io.IOException: [ https://develop.qa.ampf.com/jenkins/ ] provided port:41172 is not reachable

at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474) Suppressed: java.io.IOException:

[ http://develop.qa.ampf.com/jenkins/tcpSlaveAgentListener/ ] is invalid: 302 Found

at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:201) ... 2 more

Any suggestions would be really helpful Do i need to mention anything in the tunnel part?   Thanks, Mohit Saraf

Add Comment

[mohit.saraf@ampf.com (JIRA)]

Mohit Saraf commented on JENKINS-55689

Re: Not able to connect to jenkins master from windows slave Can anyone suggest some solution. it is little urgent and need to be implemented asap.

Add Comment

[mohit.saraf@ampf.com (JIRA)]

Mohit Saraf updated an issue

Jenkins / JENKINS-55689

Not able to connect to jenkins master from windows slave

Change By: Mohit Saraf Comment:

Can anyone suggest some solution. it is little urgent and need to be implemented asap.

Add Comment

[mohit.saraf@ampf.com (JIRA)]

Mohit Saraf commented on JENKINS-55689

Re: Not able to connect to jenkins master from windows slave Hi, Please advise if i need to change anything in the configuration

Add Comment

[escoem@gmail.com (JIRA)]

Emilio Escobar commented on JENKINS-55689

Re: Not able to connect to jenkins master from windows slave

hello Mohit, probably adding the tunnel with ":41172" might be enough. Anyway, this is not a windows-slaves-plugin issue but a question to ask at Jenkins users mailing list.

Add Comment

[escoem@gmail.com (JIRA)]

Emilio Escobar closed an issue as Not A Defect

Jenkins / JENKINS-55689

Not able to connect to jenkins master from windows slave

Change By: Emilio Escobar Status: Open Closed Resolution: Not A Defect

Add Comment

[punith.shetty88@gmail.com (JIRA)]

Punith Shetty reopened an issue

Jenkins / JENKINS-55689 Not able to connect to jenkins master from windows slave

Change By: Punith Shetty Resolution: Not A Defect Status: Closed Reopened

Add Comment

[punith.shetty88@gmail.com (JIRA)]

Punith Shetty commented on JENKINS-55689

Re: Not able to connect to jenkins master from windows slave Hi, Is there a resolution for this issue ? I am seeing the same error for my servers   INFO: Setting up agent: windows_agent Aug 26, 2019 1:10:22 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Aug 26, 2019 1:10:22 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.25 Aug 26, 2019 1:10:22 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using F:\win_jenkins\remoting as a remoting work directory Aug 26, 2019 1:10:22 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among https://myserver/ Aug 26, 2019 1:10:22 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping, Diagnostic-Ping, OperationsCenter2] Aug 26, 2019 1:10:23 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible WARNING: Connection refused: connect Aug 26, 2019 1:10:23 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: https://myserver/ provided port:46080 is not reachable java.io.IOException: https://myserver/ provided port:46080 is not reachable

at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474)

Add Comment

[punith.shetty88@gmail.com (JIRA)]

Punith Shetty assigned an issue to Jeff Thompson

Jenkins / JENKINS-55689

Not able to connect to jenkins master from windows slave

Change By: Punith Shetty Assignee: Emilio  Escobar Jeff Thompson

Add Comment

[jthompson@cloudbees.com (JIRA)]

Jeff Thompson closed an issue as Incomplete

Jenkins / JENKINS-55689 Not able to connect to jenkins master from windows slave

Change By: Jeff Thompson Status: Reopened Closed Resolution: Incomplete

Add Comment

[jthompson@cloudbees.com (JIRA)]

Jeff Thompson commented on JENKINS-55689

Re: Not able to connect to jenkins master from windows slave Have you asked on the Jenkins users email list as suggested? Or the gitter channel? This looks like a usage or configuration question and not a specific defect.

Add Comment

[punith.shetty88@gmail.com (JIRA)]

Punith Shetty commented on JENKINS-55689

Re: Not able to connect to jenkins master from windows slave

Thanks i was able to get this working, the issue was the nodeport. TCP traffic is only served on nodeport on openshift/kubernetes platform.

Add Comment

[punith.shetty88@gmail.com (JIRA)]

Punith Shetty edited a comment on JENKINS-55689

Re: Not able to connect to jenkins master from windows slave

Thanks i was able to get this working, the issue was the nodeport. TCP traffic is only served on nodeport on openshift/kubernetes platform. Once i got the nodeport opened on the platform and created a tunnel for it to route traffic to the slave agent port on jenkins, i was able to make the connection.

Add Comment

[jthompson@cloudbees.com (JIRA)]

Jeff Thompson commented on JENKINS-55689

Re: Not able to connect to jenkins master from windows slave

Punith Shetty, thanks for responding with your success and describing the solution that worked for you. That helps others who might encounter a similar problem.

Add Comment