A specific job or your Jenkins environment is experiencing high CPU.
This article describes how to collect the minimum required information for high CPU issues on a CJP environment so that it can be efficiently troubleshooted.
If the required data is bigger than 50 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. The upload service works best in Chrome or Firefox.
CloudBees Jenkins Platform (CJP)
Operations Center (OC)
Client controller (CM)
Operating System: Windows
[ ] Support Bundle [ ] Output of the script getpslist.bat [ ] GC log file for review
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.
Please enable at minimum the following checks:
controller Log Recorders,
Garbage Collection Logs,
Slow Request Records,
Out Of Memory Errors,
controller Heap Histogram,
Thread dumps of running Pipeline builds,
Thread dumps and
Download the getpslist.bat.
Download the getThreadDumps.bat
Create a folder to put the PsTools.zip in and unzip the contents to that folder.
The screen shot below uses 'C:\Users\Administrator\Downloads\PSTools' as an example, it is not required to save the script there.
Copy the getpslist.bat script to the same folder.
Monitor for the next occurrence of the high CPU issue.
When the high CPU issue occurs open two command windows (one for getpslist.bat and the other for getThreadDumps.bat).
Start the getpslist.bat script by running:
getpslist.bat PID from the location where PsTools.zip was saved and unzipped.
Start the getThreadDumps.bat script by running:
getThreadDumps.bat PID 1 from the directory where getThreadDumps.bat is saved. Have a look at the article Required Data: High CPU On Windows to understand how this script works.
PID is the process id of the Jenkins process. The PID can be determined using the Task Manager as shown in the screen shot below. Note that you have to add the PID column by selecting View->Select Columns->clicking PID(Process Identifer)-> clicking OK
Please note the following requirements for the getpslist.bat script to work as expected:
All scripts MUST be run as a user with Administrator privileges, i.e. from a command window that was opened via Run As Administrator.
Once the scripts complete, please upload the pslistlog.output.PID.zip file, the jstack.PID.zip, the Support Bundle, and verbose gc logs for review.
* The pslistlog.output.PID.zip file will be located in the same directory the getpslist.bat script is ran from.
If you followed Prepare CloudBees CI for Support then the gc logs file should be at
-Xlog:gc[...]:file=<some-log-file>:[...] for JDK 11+ or
-Xloggc:<some-log-file> for JDK 8: