Encountered a problem with a job recently that bears the hallmarks of https://issues.jenkins-ci.org/browse/JENKINS-6565.
What happened: Was alerted to a job that was stuck in limbo with no output, blocking any pending jobs and it wasn't possible to cancel it. My suspicions are that since this job (Job A) uses a lock which prevents it running at the same time as another job (Job B), and since the other job (B) got cancelled, there was a problem with Job A acquiring lock. I did notice that any pending builds of Job B managed to continue running. I ended up restarting Jenkins in order to free up job A so that it could be retriggered. Unfortunately, I didn't manage to glean anything from the limited log output in Jenkins system log page about what happened or what exactly the order of events were. Upon looking on the master I noticed that directory for build number 18 of Job A that is associated with the console output and configuration details for that particular run were all missing. Only the directory was created. https://issues.jenkins-ci.org/browse/JENKINS-6565 is my best guess, but that's really just speculation. Suggestions on how to capture more useful information via jenkins system logs would be welcome. -- Regards, Darragh Bailey
