[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies

2019-08-30 Thread jonastonnyniel...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonas Nielsen commented on  JENKINS-52613  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: cannot relaunch ssh agent, when node dies   
 

  
 
 
 
 

 
 You don't have to change the IP of the agent to an invalid IP and back again. It's sufficient to simply enter the configuration page of the slave and save the already existing configuration. Then you are able to relaunch the agent.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192461.1531857544000.3210.1567165500167%40Atlassian.JIRA.


[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies

2018-08-26 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52613  
 
 
  cannot relaunch ssh agent, when node dies   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 ssh-slaves-1.27  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies

2018-08-12 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo edited a comment on  JENKINS-52613  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: cannot relaunch ssh agent, when node dies   
 

  
 
 
 
 

 
 means that fails to connect, because you do not have retries and timeouts configured, Jenkins will wait about 5 min to retry to connect (retention strategy), if you configure 10 retries, 15 seconds between retries, and a timeout of about 240 seconds you will not have to disconnect an reconnect the agent when it happens, it will reconnect automatically if it is possible, and you will see the reconnections on the log.      The next version will have those values by default to avoid this confused situation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies

2018-08-12 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-52613  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: cannot relaunch ssh agent, when node dies   
 

  
 
 
 
 

 
 means that fails to connect, because you do not have retries and timeouts configured, Jenkins will wait about 5 min to retry to connect (retention strategy), if you configure 10 retries, 15 seconds between retries, and a timeout of about 240 seconds you will not have to disconnect an reconnect the agent when it happens, it will reconnect automatically if it is possible, and you will see the reconnections on the log.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies

2018-08-12 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo started work on  JENKINS-52613  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies

2018-08-09 Thread mh...@tivo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Hall commented on  JENKINS-52613  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: cannot relaunch ssh agent, when node dies   
 

  
 
 
 
 

 
 OK, we applied the workaround you mentioned above, since the issue happened again today and it worked. What does that mean?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.