Olaf Lenz commented on Bug JENKINS-23471

A further observation, which may give an idea: I just saw this happening when starting jenkins. In the jenkins log, I noticed that it tried to start the slave on a node twice. And that was apparently the thread that causes the high load. From the log:

Aug 21, 2014 5:07:27 PM hudson.slaves.SimpleScheduledRetentionStrategy check
INFO: Trying to launch computer cip20 as schedule says it should be on-line at this point in time
...
[clip]
...
Effective SlaveRestarter on master: null
Aug 21, 2014 5:07:29 PM hudson.WebAppMain$3 run
INFO: Jenkins is fully up and running
[08/21/14 17:07:30] SSH Launch of cip12 on cip12 failed in 3,013 ms
...
[clip]
...
INFO: Trying to launch computer cip20 as schedule says it should be on-line at this point in time
Aug 21, 2014 5:08:17 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record <init>
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