[JIRA] (JENKINS-51670) java.io.IOException: Failed to connect to 18.218.111.188:33083

[gsambasiva161@gmail.com (JIRA)]

sambasiva rao created an issue

Jenkins / JENKINS-51670 java.io.IOException: Failed to connect to 18.218.111.188:33083 Issue Type: Bug Assignee: Giuseppe Landolfi Components: jenkins-tag-cloud, slave-setup-plugin Created: 2018-06-03 19:06 Environment: jenkins Priority: Minor Reporter: sambasiva rao sudo java -jar agent.jar -jnlpUrl http://18.218.111.188:8080/computer/slave/slave-agent.jnlp -secret 5f919a663ea1bae3240635681a222f3f3113580a1c63dff7900553d7a21868fd -workDir "jenkins/workspace" Jun 03, 2018 6:56:50 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using jenkins/workspace/remoting as a remoting work directory Both error and output logs will be printed to jenkins/workspace/remoting Jun 03, 2018 6:56:50 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: slave Jun 03, 2018 6:56:50 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Jun 03, 2018 6:56:50 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /home/ubuntu/jenkins/workspace/remoting as a remoting work directory Jun 03, 2018 6:56:50 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://18.218.111.188:8080/ Jun 03, 2018 6:56:50 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Jun 03, 2018 6:56:50 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: 18.218.111.188 Agent port: 33083 Identity: 2d:7c:59:2f:61:7d:d0:15:a2:89:6f:e1:e5:6f:e3:d9 Jun 03, 2018 6:56:50 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Jun 03, 2018 6:56:50 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to 18.218.111.188:33083 Jun 03, 2018 6:59:07 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to 18.218.111.188:33083 (retrying:2) java.io.IOException: Failed to connect to 18.218.111.188:33083 at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:242) at hudson.remoting.Engine.connect(Engine.java:686) at hudson.remoting.Engine.innerRun(Engine.java:547) at hudson.remoting.Engine.run(Engine.java:469) Caused by: java.net.ConnectException: Connection timed out at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Net.java:454) at sun.nio.ch.Net.connect(Net.java:446) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648) at java.nio.channels.SocketChannel.open(SocketChannel.java:189) at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:203) ... 3 more Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[gsambasiva161@gmail.com (JIRA)]

sambasiva rao updated an issue

Jenkins / JENKINS-51670 java.io.IOException: Failed to connect to 18.218.111.188:33083

Change By: sambasiva rao Labels: JNLP connect fail slave to

Add Comment

[gsambasiva161@gmail.com (JIRA)]

sambasiva rao updated an issue

Jenkins / JENKINS-51670 java.io.IOException: Failed to connect to 18.218.111.188:33083

Change By: sambasiva rao Priority: Minor Critical

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-51670 java.io.IOException: Failed to connect to 18.218.111.188:33083

Change By: Oleg Nenashev Component/s: _unsorted Component/s: jenkins-tag-cloud Component/s: slave-setup-plugin

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev assigned an issue to Unassigned

Jenkins / JENKINS-51670 java.io.IOException: Failed to connect to 18.218.111.188:33083

Change By: Oleg Nenashev Assignee: Giuseppe Landolfi

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev commented on JENKINS-51670

Re: java.io.IOException: Failed to connect to 18.218.111.188:33083 So what's the problem here. IIUC Master's TcpAgent listener port is just inacessible from the agent machine. Check your network settings as a first step

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated JENKINS-51670

No response from the requester

Jenkins / JENKINS-51670

java.io.IOException: Failed to connect to 18.218.111.188:33083

Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Incomplete

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated JENKINS-51670

Jenkins / JENKINS-51670 java.io.IOException: Failed to connect to 18.218.111.188:33083

Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved

Add Comment

[groverprateek07@gmail.com (JIRA)]

Prateek Grov commented on JENKINS-51670

Re: java.io.IOException: Failed to connect to 18.218.111.188:33083 Well I have similar problem. My slave sends has a SYN_SENT status and while my Master is listening on the correct port, I cant seem to connect(Master doesnt send ACK) . I am using EC2 for both master and slave and I have opened all ports on slave for master's subnet and yet the connection times out.

Add Comment

[guptapraveen12@gmail.com (JIRA)]

PRAVEEN GUPTA commented on JENKINS-51670

Re: java.io.IOException: Failed to connect to 18.218.111.188:33083

Will there be a new release for this issue. I updated to 2.121.3 recently and started getting this issue. Reverting back to older version also didn't help. I tried changing the port and then connection timed out problem got resolved but java.io.IOException: Failed to connect to xxxxxxxxxxxx:port is coming now.

Add Comment

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

[guptapraveen12@gmail.com (JIRA)]

PRAVEEN GUPTA reopened an issue

Jenkins / JENKINS-51670

java.io.IOException: Failed to connect to 18.218.111.188:33083

Change By: PRAVEEN GUPTA Resolution: Incomplete Status: Resolved Reopened

Add Comment

[shraddha.magar5@gmail.com (JIRA)]

shraddha Magar commented on JENKINS-51670

Re: java.io.IOException: Failed to connect to 18.218.111.188:33083 Hello, I am using Jenkins version 2.105 and JRE 1.8. I am using master as Linux and windows as agent. I have restarted Jenkins instance then agent which is configured on windows with JNLP got offline and its not coming online, its showing below error. Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://x.x.x.x:x/jenkins/ Aug 29, 2018 1:43:04 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve

INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]

Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful   Agent address: x.x.x.x   Agent port:    37091   Identity:      51:a8:0d:a8:18:dd:db:d8:ea:18:b7:98:da:76:b2:ae Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to x.x.x.x:37091 Aug 29, 2018 1:43:35 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to x.x.x.x:37091 (retrying:2) java.io.IOException: Failed to connect to x.x.x.x:37091

at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:242)  at hudson.remoting.Engine.connect(Engine.java:686)  at hudson.remoting.Engine.innerRun(Engine.java:547)  at hudson.remoting.Engine.run(Engine.java:469)

Caused by: java.net.ConnectException: Connection timed out: connect  at sun.nio.ch.Net.connect0(Native Method)  at sun.nio.ch.Net.connect(Unknown Source)  at sun.nio.ch.Net.connect(Unknown Source)  at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)  at java.nio.channels.SocketChannel.open(Unknown Source)

at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:203)  ... 3 more

Could you please help me out here?

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite closed an issue as Not A Defect

This is a configuration error in the user installation, not a Jenkins issue.

Jenkins / JENKINS-51670

java.io.IOException: Failed to connect to 18.218.111.188:33083

Change By: Mark Waite Status: Reopened Closed Resolution: Not A Defect

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)