Required Data: Hang Issue On Linux


A specific job or your Jenkins environment hangs or responds slowly.

Required Data: Hang Issue On Linux CJP

This article describes how to collect the minimum required information for performance issues on a CJP environment so that it can be efficiently troubleshooted.

If the required data is bigger than 20 MB you will not be able to use ZenDesk to upload all the information. On this case we would like to encourage you to use our upload service in order to attach all the required information.


  • CloudBees Jenkins Platform (CJP)
  • Operations Center (OC)
  • Client Master (CM)

Required Data check list

[ ] Support bundle
[ ] Output of the script
[ ] GC log file for review

Support bundle

A support bundle from the problematic instance ideally when the issue is happening or in the worst case right after the issue is exposed. Please, follow the KB below in case you don’t know how to generate a support bundle.

Output of the script

Download the

The script will need to be made executable by running:
chmod +x .

Ideally, your environment is configured as documented in Prepare Jenkins For Support.

If you are experiencing a hang or a poor performance issue please execute the script while the issue is occurring:

Run the script as the same user that starts Jenkins by running: sudo -u jenkins sh PID (where PID is the PID of the CloudBees Jenkins process).

If CloudBees Jenkins Enterprise or CloudBees Jenkins Operations Center is running on Ubuntu
you will need to confirm the PID via the command line by running
ps -ef | grep jenkins.
This is required because the CloudBees Jenkins PID File contains the PID of the daemon process itself
not the CloudBees Jenkins PID.

The script will collect 1 full thread dump once very 30 seconds
via jstack (jstack is included in the Java JDK only, not the JRE) along with top, vmstat, netstat, and iostat data.

The necessary packages should be installed in your environment for generating top, top dash H, vmstat, netstat, nfsiostat, nfsstat and iostat data.

The script will generate data in the current directory it is run from.

If the script does not run as expected please upload the output the script generates from the terminal window for review.

GC log file for review.

If you followed Prepare Jenkins For Support then the gc logs file should be under -Xloggc:$path/gc-%t.log Note that the slash should be adjusted for your operating system, i.e. Windows uses \

Have more questions? Submit a request


Please sign in to leave a comment.