[
https://issues.jenkins-ci.org/browse/JENKINS-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162168#comment-162168
]
Alex Trepca commented on JENKINS-6400:
--------------------------------------
Hello,
Bringing this back to life. I have the same issue, os: CentOS 5.7, Jenkins:
1.443, master + 3 build slaves (which are shared with another Jenkins instance).
- job is scheduled to run "55 9,11,16 * * *" and last run 'started by timer'
was 'Apr 24, 2012 4:55:55 PM'
- job is scheduled to run "30 8 * * *" and last run 'started by timer' was 'Apr
24, 2012 8:30:56 AM'
I also created a test job which only echoes a text, scheduled to run "*/5 * * *
*" and so far it ran:
#8 Apr 27, 2012 3:30:55 PM
#7 Apr 27, 2012 3:16:48 PM
#6 Apr 27, 2012 3:00:38 PM
#5 Apr 27, 2012 2:53:05 PM
#4 Apr 27, 2012 2:43:07 PM
#3 Apr 27, 2012 2:43:01 PM
#2 Apr 27, 2012 2:31:28 PM
#1 Apr 27, 2012 2:23:06 PM
Which is not */5 at all.
Also, the server has been restarted yesterday evening (because of other
reasons), and the problem persists.
What might be causing this?
Thank you,
Alex
> 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
