[JIRA] (JENKINS-58220) eks slave provided port:5000 is not reachable

0 views
Skip to first unread message

ranibob.rb@gmail.com (JIRA)

unread,
Jun 26, 2019, 3:18:02 PM6/26/19
to jenkinsc...@googlegroups.com
bob james created an issue
 
Jenkins / Bug JENKINS-58220
eks slave provided port:5000 is not reachable
Issue Type: Bug Bug
Assignee: Carlos Sanchez
Attachments: image-2019-06-26-21-13-51-122.png, image-2019-06-26-21-13-59-228.png
Components: kubernetes-plugin
Created: 2019-06-26 19:17
Priority: Blocker Blocker
Reporter: bob james

Jenkins Master: 2.164.1
kubernetes-plugin: 1.16.1

Jenkins master is running outside of Kubernetes and i'm trying to get my Jenkins slaves to run on my EKS worker nodes

 

Jenkins slave pod error message:

INFO: Locating server among [https://my-jenkins-url.com]                                                     
Jun 26, 2019 6:37:59 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve                         
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]                                    
Jun 26, 2019 6:38:04 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible                   
WARNING: connect timed out                                                                                      
Jun 26, 2019 6:38:04 PM hudson.remoting.jnlp.Main$CuiListener error                                             
SEVERE: https://my-jenkins-url.com provided port:5000 is not reachable                                       
java.io.IOException: https://my-jenkins-url.com provided port:5000 is not reachable                          
    at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:287)      
    at hudson.remoting.Engine.innerRun(Engine.java:523)                                                         
    at hudson.remoting.Engine.run(Engine.java:474)                                                              

How can I override this "port:5000" default setting?

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

ranibob.rb@gmail.com (JIRA)

unread,
Jun 26, 2019, 3:18:02 PM6/26/19
to jenkinsc...@googlegroups.com
bob james updated an issue
Change By: bob james
Jenkins Master: 2.164.1
kubernetes-plugin: 1.16.1

Jenkins master is running *outside* of Kubernetes and i'm trying to get my Jenkins slaves to run on my EKS worker nodes


 

Jenkins slave pod error message:
{code:java}

INFO: Locating server among [https://my-jenkins-url.com]                    
Jun 26, 2019 6:37:59 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve                    
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]                    
Jun 26, 2019 6:38:04 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible                   
WARNING: connect timed out                    
Jun 26, 2019 6:38:04 PM hudson.remoting.jnlp.Main$CuiListener error                    
SEVERE: https://my-jenkins-url.com provided port:5000 is not reachable                    
java.io.IOException: https://my-jenkins-url.com provided port:5000 is not reachable                    
    at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:287)      
    at hudson.remoting.Engine.innerRun(Engine.java:523)                    
    at hudson.remoting.Engine.run(Engine.java:474)                    
{code}

How can I override this "port:5000" default setting?

!image-2019-06-26-21-13-59-228.png!!image-2019-06-26-21-13-51-122.png!  

ranibob.rb@gmail.com (JIRA)

unread,
Jun 28, 2019, 10:49:02 AM6/28/19
to jenkinsc...@googlegroups.com
bob james resolved as Fixed
 

The reason I was receiving the error is because my jenkins master was residing behind an ALB which doesn't support TCP listeners as required by JNLP. To work around this, I have created an NLB with a TCP listener and jenkins target group on port 5000. I then proceeded to place the DNS of the NLB in the "Jenkins tunnel" field of the kubernetes-plugin which allowed the agent to establish communication with the master!

Change By: bob james
Status: Open Resolved
Resolution: Fixed
Reply all
Reply to author
Forward
0 new messages