Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-51670

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

      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

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

          sambasiva rao created issue -
          sambasiva rao made changes -
          Labels New: JNLP connect fail slave to
          sambasiva rao made changes -
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]
          Oleg Nenashev made changes -
          Component/s New: _unsorted [ 19622 ]
          Component/s Original: jenkins-tag-cloud [ 17484 ]
          Component/s Original: slave-setup-plugin [ 15929 ]
          Oleg Nenashev made changes -
          Assignee Original: Giuseppe Landolfi [ peppe ]

          Oleg Nenashev added a comment -

          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

          Oleg Nenashev added a comment - 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

          Oleg Nenashev added a comment -

          No response from the requester

          Oleg Nenashev added a comment - No response from the requester
          Oleg Nenashev made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Fixed but Unreleased [ 10203 ]
          Oleg Nenashev made changes -
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]

          Prateek Grov added a comment -

          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.

          Prateek Grov added a comment - 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.

            Unassigned Unassigned
            samba161 sambasiva rao
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: