I have a Jenkins job running some JBehave tests. The job fails, but isn't listed in the build queue any more. Unfortunately, it appears to have spawned a thread that is stuck in an infinite loop. It keeps throwing an interrupt exception, printing a stack trace, and then doing it again. The problem is that it's writing the exception and stack trace to a log file in the /tmp directory on the Jenkins master. The /tmp directory on master is on it's own mount point, but when it's full, it does stop Jenkins from performing any builds, since temporary log files are written there.
The only way to recover from this, is to restart the Jenkins service on the master. If I kill the slave the log file stops growing, but it won't release the disk space, even if the file is deleted, until the Jenkins master restarts. Both the master and the slave are running on RHEL6. I'm running Jenkins 1.580.3 LTS. I have the logfilesizechecker plugin installed. But it doesn't catch this log. Has anyone encountered a similar case? I really don't like the idea that one rogue job can bring down the entire system. -- 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/43341ca2-239a-4c9e-8771-16280beed974%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
