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

thread dump via signal not working on master node

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • core
    • None
    • Ubuntu, openjdk-7, Jenkins 1.656

    Description

      Unable to obtain a thread dump when Jenkins is stuck coming up.
      According to https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump
      you should be able to obtain a thread dump by sending SIGQUIT on the master node. While the PID of Jenkins changes (indicating that SIGQUIT was acted upon), no thread dump is observed on stdout/stderr or /var/log/jenkins/jenkins.log.

      Since I am trying to diagnose why the Jenkins takes 2hrs to start up, the /threadDump method in the GUI is not suitable in this case.

      Attachments

        Issue Links

          links to

          Web Link CloudBees Internal CJP-6414

          Activity

            Ascending order - Click to sort in descending order
            alt_jmellor John Mellor created issue -
            scm_issue_link SCM/JIRA link daemon made changes -
            Field Original Value New Value
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            cloudbees CloudBees Inc. made changes -
            Remote Link This issue links to "CloudBees Internal CJP-6414 (Web Link)" [ 19237 ]

            People

              Unassigned Unassigned
              alt_jmellor John Mellor
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: