Issue connecting slave on aws EC2 using JNLP4 to on-premise master

103 views
Skip to first unread message

Ahmed Hosni

unread,
Jul 3, 2017, 4:21:02 PM7/3/17
to Jenkins Users, kad....@gmail.com
Hi all,

I've just spin up an EC2 on aws running ubuntu 14 with openjdk 1.8, and i'm trying to connect it to a master hosted within internal network running V2.46.1 without any clue:

i've downloaded the slave.jar to my ec2 the ran the following command:

java -jar slave.jar -jnlpUrl <master_url>/computer/<agent_name>/slave-agent.jnlp

The slave can communicate with the master and get the right TCP port already configured in the master but it just hangs in the trying connect JNLP

I was able to to do the same and connect an ubuntu box with the same configuration to the same master but this slave was hosted in our data center and not in aws 
and i configured the command to run on startup as a service 

i've also checked the security groups for the EC2 instance and made sure it's accepting traffic from our subnet  

Here's the output that i get when i try to connect EC2 to the master hosted in our data center using JNLP. this times out after 2 minute with no useful stack trace :
Jul 03, 2017 6:40:15 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up slave: testNode
Jul 03, 2017 6:40:15 PM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Jul 03, 2017 6:40:15 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [<Master_URL>/, http://<IP>:<PORT>/]
Jul 03, 2017 6:40:16 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, CLI2-connect, JNLP-connect, Ping, CLI-connect, JNLP2-connect]
Jul 03, 2017 6:40:16 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: <IP>
  Agent port:    59625
  Identity:      7c:f3:ad:89:af:2a:bf:e5:66:59:43:15:c2:ce:fe:44
Jul 03, 2017 6:40:16 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jul 03, 2017 6:40:16 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to 10.89.234.43:59625
Jul 03, 2017 6:40:16 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jul 03, 2017 6:40:16 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: 7c:f3:ad:89:af:2a:bf:e5:66:59:43:15:c2:ce:fe:44


 
 
Reply all
Reply to author
Forward
0 new messages