- I have found evidences of IO issues with the FileSystem where Jenkins Home is hosted.
This article describes how to collect the minimum required information for troubleshooting IO issues.
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 Team (CJT)
- CloudBees Jenkins Platform - Client Master (CJPCM)
- CloudBees Jenkins Platform - Operations Center (CJPOC)
- Operating System: Linux
- Support bundle
- Output of the script
- Description of the File System
- Optional (if an I/O issue is suspected): output of the script listDProcessesNativeStacks.sh
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.
Download the testIO.sh.
The testIO.sh script will need to be made executable by running:
chmod +x testIO.sh.
IOTest.log by running the
testIO.sh script as:
sh testIO.sh <FOLDER> [TIMES] [PERIOD]
As an example:
sh testIO.sh /var/lib/jenkins_home 2
testIO.sh script will execute Write and Write/Read test a number of [TIMES] times every [PERIOD].
To find the expected values for this script, see: IO Troubleshooting on Linux.
- Output from
df -Hfor the Host File System.
- In the case your
JENKINS_HOMEis mounted on a Share File System, please let as know its technology (NFS, EFS, etc.) and it version (NFSv3, etc.).