[JIRA] [ssh-slaves] (JENKINS-13237) Unsuccessful SSH slave start do not timeout and cannot be retry, even manually

Fri, 27 Jun 2014 04:25:23 -0700

I don't think this is related to JENKINS-13131 as the description there indicates the slave connection will be established after 15 to 20 minutes eventually.

We're facing the same issue (as described within here) in our environment:

  • a test node is configured being connected to via SSH (In demand delay: 3, Idle delay: 5),
  • a Job loads a virtual machine snapshot and triggers another Job, which triggers the In demand delay,
  • this leads to the following behavior sometimes:
    • On the slave detail page you see the icon blinking and
    • the message This node is being launched appears, but
    • in reality nothing happens or some kind of endless connection attempt is being made. Logging into the machine via SSH from local workstation works.
    • Clicking on the button Relaunch slave agent in Jenkins doesn't help.
    • Only workaround for us so far: Restarting Jenkins.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to