The Jenkins process crashes
This article describes how to collect the minimum required information for crash 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 Master (CM)
- Operating System: Linux
[ ] approximate time frame of the issue
[ ] hs_err_pidXXXX.log (where XXXX is the pid of the process that crashed)
[ ] /var/log/messages
[ ] /var/log/syslog
[ ] /var/log/dmesg
The Java Virtual Machine (JVM) will generate a hs_err_pidXXXX.log file and a Java Core Dump file
in the event of a an actual JVM crash. The hs_err_pidXXXX.log file is normally written to the
working directory of the process or in the temporary directory for the operating system.
The Java Core Dump file requires the ulimit -c setting to be set to unlimited for it to be
generated, the ulimit -f should also be set to unlimited so it will not be truncated.
You will need to check the following locations for the Java Core Dump File:
working directory of the process
temporary directory for the operating system
the location returned after running:
The recommended ulimit settings are documented in Prepare Jenkins For Support.
Please upload all of the files listed under the Required Data check list for review.
Please note that it is recommended to keep the version of Java 8 used by Jenkins at the most recent version
available to take advantage of the fixes it contains, which includes fixes for crashes in Java.