[JIRA] [core] (JENKINS-26020) Will not start builds even though there are available slots on executor
Oleg Nenashev commented on JENKINS-26020 Will not start builds even though there are available slots on executor Dec 15, 2014 8:40:10 AM jenkins.slaves.JnlpSlaveHandshake error WARNING: TCP slave agent connection handler #150398 with /10.33.21.14:62740 is aborted: generic_AESL-JENKINS07 is already connected to this master. Rejecting this connection. It seems to be unrelated. Such issue usually happens when you have two jenkins-slave processes. On Windows machines it rarely happens on improper service termination, etc. You can also configure Jenkins slave to have a bigger reconnect attempt interval. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26020) Will not start builds even though there are available slots on executor
Daniel Beck commented on JENKINS-26020 Will not start builds even though there are available slots on executor Any interesting errors getting logged? 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26020) Will not start builds even though there are available slots on executor
Christian Bremer commented on JENKINS-26020 Will not start builds even though there are available slots on executor We get ~5000 JnlpSlaveHandshake errors per hour: Dec 15, 2014 8:40:10 AM jenkins.slaves.JnlpSlaveHandshake error WARNING: TCP slave agent connection handler #150398 with /10.33.21.14:62740 is aborted: generic_AESL-JENKINS07 is already connected to this master. Rejecting this connection. We get these errors at all times, also when we can schedule on all slaves. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26020) Will not start builds even though there are available slots on executor
Christian Bremer commented on JENKINS-26020 Will not start builds even though there are available slots on executor Other than that I see no errors in the log that occurs when it fails to schedule on a node although I might have missed it since our logs are flooded. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26020) Will not start builds even though there are available slots on executor
Christian Bremer commented on JENKINS-26020 Will not start builds even though there are available slots on executor 200$ is up for grabs for this issue at: https://freedomsponsors.org/issue/598/will-not-start-builds-even-though-there-are-available-slots-on-executor 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26020) Will not start builds even though there are available slots on executor
Christian Bremer created JENKINS-26020 Will not start builds even though there are available slots on executor Issue Type: Bug Assignee: Unassigned Attachments: ThreadDump - After doing disconnect and connect.log, ThreadDump - No jobs can be schedule on node.log Components: core Created: 11/Dec/14 3:45 PM Description: Sometimes our nodes won't be able to start new builds even though there are free slots available. A workaround for the slaves is to disconnect/connect the slave and it will start to schedule builds again. I have observed that when this happens for a slave the slave has fewer threads ongoing than an idle slave. Attaching thread dumps when this happens and after doing an disconnect/connect. We have seen this issue both on Windows(jlnp) slaves and linux(ssh) slaves as well as on the master node which is running linux. Environment: LTS 1.580.1 Project: Jenkins Priority: Critical Reporter: Christian Bremer 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.