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

All pages display stack trace to admins when Cron Triggers Monitor enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None
    • CentOS 7
      openjdk-1.8.0_222
      Jenkins 2.190

      We upgraded from Jenkins 1.170 to Jenkins 1.90 yesterday afternoon and initially saw no issues, but this morning found that all admin users were seeing a partial stack track on any Jenkins page they tried to load. This was traced back to the administrative monitors and from there we discovered that disabling the Cron Triggers Monitor (under Configuration -> Administrative monitors configuration) resolves the issue and enabling causes the issue to return. We assume this could be related to the recent issue 54854, resolved in Jenkins 2.189. Attached are both a screenshot of what we saw when this error and a text file containing the full stack trace.

        1. Screen Shot 2019-08-22 at 3.46.38 PM.png
          779 kB
          Samantha Anne Taylor
        2. StackTrace.txt
          36 kB
          Samantha Anne Taylor

            Unassigned Unassigned
            staylor Samantha Anne Taylor
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: