Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-25704

Scheduled triggering stops working until restart

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • core

      Jobs configured with a periodic trigger stop being triggered after Jenkins has been running for a few days.

      There are no indications of a problem in the log. The last/next run times shown in the configure page look right. Manually triggering the job works, though the periodic trigger doesn't resume until Jenkins is restarted.

      The Jenkins and plugin versions are what is currently installed though we've seen the problem for some months with different recent versions of Jenkins and various plugins. It might be that the problem has not been noticed more often because of more frequent Jenkins restarts.

      I've attached a thread dump taken while periodic triggers haven't been working for over a day.

        1. jenkins thread dumps.txt
          13 kB
        2. threadDump.txt
          38 kB
        3. jenkins_log_threaddump-tom.txt
          65 kB
        4. hudson.triggers-ALL.log
          42 kB
        5. hudson.triggers-ALL.log
          42 kB
        6. thread-dump1.txt
          67 kB

          [JENKINS-25704] Scheduled triggering stops working until restart

          David Resnick created issue -

          Daniel Beck added a comment -

          Could you search the Jenkins log for "Timer task foo failed", foo being the name of a task?

          Daniel Beck added a comment - Could you search the Jenkins log for "Timer task foo failed", foo being the name of a task?

          Daniel Beck added a comment -

          Could you set up a log recorder for the logger hudson.triggers.Trigger on level FINE to see what gets logged?

          https://wiki.jenkins-ci.org/display/JENKINS/Logging

          Daniel Beck added a comment - Could you set up a log recorder for the logger hudson.triggers.Trigger on level FINE to see what gets logged? https://wiki.jenkins-ci.org/display/JENKINS/Logging

          David Resnick added a comment -

          The problem has finally recurred after I configured the logger. The logs show that the trigger just stops at some point.

          This is one of the cron jobs:

          Nov 26, 2014 2:36:00 AM FINE hudson.triggers.Trigger
          cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’
          Nov 26, 2014 2:37:00 AM FINE hudson.triggers.Trigger
          cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’
          Nov 26, 2014 2:38:00 AM FINE hudson.triggers.Trigger
          cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’
          Nov 26, 2014 2:38:00 AM CONFIG hudson.triggers.Trigger
          cron triggered hudson.model.FreeStyleProject@4f4e362a[Reviewbot2]
          Nov 26, 2014 2:39:00 AM FINE hudson.triggers.Trigger
          cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’
          Nov 26, 2014 2:40:00 AM FINE hudson.triggers.Trigger
          cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’
          Nov 26, 2014 2:41:00 AM FINE hudson.triggers.Trigger
          cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’
          

          David Resnick added a comment - The problem has finally recurred after I configured the logger. The logs show that the trigger just stops at some point. This is one of the cron jobs: Nov 26, 2014 2:36:00 AM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’ Nov 26, 2014 2:37:00 AM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’ Nov 26, 2014 2:38:00 AM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’ Nov 26, 2014 2:38:00 AM CONFIG hudson.triggers.Trigger cron triggered hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] Nov 26, 2014 2:39:00 AM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’ Nov 26, 2014 2:40:00 AM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’ Nov 26, 2014 2:41:00 AM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@4f4e362a[Reviewbot2] with spec ‘H/5 * * * *’

          Daniel Beck added a comment -

          Are you changing date/time on the Jenkins master, e.g. during tests?

          Daniel Beck added a comment - Are you changing date/time on the Jenkins master, e.g. during tests?

          David Resnick added a comment - - edited

          No. AFAIK there are no changes taking place in the environment. The last time triggers stopped was in the middle of the night.

          David Resnick added a comment - - edited No. AFAIK there are no changes taking place in the environment. The last time triggers stopped was in the middle of the night.

          David Resnick added a comment - - edited

          No building is done on the master, though a couple jobs do run there (e.g. the Reviewbot2 one in the log above).

          David Resnick added a comment - - edited No building is done on the master, though a couple jobs do run there (e.g. the Reviewbot2 one in the log above).

          Daniel Beck added a comment -

          Are you running an NTP client?

          Daniel Beck added a comment - Are you running an NTP client?

          David Resnick added a comment -

          I'll be able to check tomorrow. I did check some logs on the master today (e.g. cron) and saw that there were no jumps of the date/time. Timestamps in jenkins.log are also predictable, after the triggers stop too.

          David Resnick added a comment - I'll be able to check tomorrow. I did check some logs on the master today (e.g. cron) and saw that there were no jumps of the date/time. Timestamps in jenkins.log are also predictable, after the triggers stop too.

          David Resnick added a comment -

          ntpd is running on the server. It seems to be functioning OK. Time on the server is synced, ntpd hasn't logged anything.

          David Resnick added a comment - ntpd is running on the server. It seems to be functioning OK. Time on the server is synced, ntpd hasn't logged anything.

            Unassigned Unassigned
            david_resnick David Resnick
            Votes:
            13 Vote for this issue
            Watchers:
            25 Start watching this issue

              Created:
              Updated: