I'm not exactly sure what happened with our Jenkins, but we had a power outage that took the machines down without any chance of graceful shutdown. When we got the systems back up, we started Jenkins up and instead of starting up and just bringing up the few jobs that were scheduled for around the time the machine started up, we had all the Build Executors full (30) and over 120 jobs in the Build Queue, quite a few of which were the same job, so it was firing off jobs as fast as the Build Executors could come free from another job. We were able to then shutdown Jenkins via its interface and after taking away the permissions on the remote systems it runs jobs on, we brought it back up and the Build Queue was empty and the Build Executors were quiet.
Any thoughts on why this might have happened? Jenkins v 1.596 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/FCBFCDE72C66B34C8F7AD8D62D262D4E36432244%40ilsaw05.corp.incentivelogic.com. For more options, visit https://groups.google.com/d/optout.
