Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: core
-
Environment:Master is on Debian and slave runs on windows 2008 r2k
-
Similar Issues:
Description
The jenkins slave counld not connect to the master. It was running well before I rebooted the slave. All The Jnlp window states is connecting to master and times out with this error I have attached poping after several retry.
Attachments
Activity
We dont know how or if this is related to Robot Framework plugin. We can reopen this issue if more details are provided.
Jussi Malinen
added a comment - We dont know how or if this is related to Robot Framework plugin. We can reopen this issue if more details are provided. I don't believe this has anything to do with robot. I see this with a linux master and windows slave, after the slave restarted itself. The connection was fine before.
Bullhorn RelEng
added a comment - I don't believe this has anything to do with robot. I see this with a linux master and windows slave, after the slave restarted itself. The connection was fine before. The issue is definitely unrelated to robot-plugin.
Changed the issue's metadata.
@Samuel, If the issue stills open, please provide more info about Jenkins version, etc.
I also fixed my instance of it by opening up access to the master from the slave by adding an iptables rule.
Bullhorn RelEng
added a comment - I also fixed my instance of it by opening up access to the master from the slave by adding an iptables rule. 
Hi, Can you elaborate how this relates to the Robot Framework plugin?