[
https://issues.jenkins-ci.org/browse/JENKINS-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162215#comment-162215
]
Alex Trepca commented on JENKINS-6400:
--------------------------------------
Found the culprit - a combination between the history plugin and a Jenkins
backup job was blocking some of the scheduling.
> schedule triggering not working sometimes
> -----------------------------------------
>
> Key: JENKINS-6400
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6400
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Windows Server
> Reporter: deccico
> Attachments: memory_used.JPG, Thread dump [Hudson].htm
>
>
> Hi, I have a Hudson master with three or four slaves and a bunch of critical
> tasks running nightly.
> Last night any scheduled job was triggered, and triggering of jobs stop
> working at all during the day.
> There was not any error or warning in the logs, and the service was not
> killed or restarted during this problem.
> I tried restarting the Hudson service and see if a job with a "* * * * *"
> scheduling was launched, with no luck.
> Finally I got luck by restarting the machine.
> How can i contribute solving this bug or at least adding logging info?
> thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
