Common Jenkins Errors and Step-by-Step Fixes

Every time Jenkins is used, various bugs can appear; this article walks through several common errors and provides concrete fixes.

libXrender.so.1: cannot open shared object file

The missing library can be resolved by installing the required packages one by one.

yum install ksh -y
yum install libXext.so.6 -y
yum install libXtst.so.6 -y
yum install libXt.so.6 -y
yum install libGLU.so.1 --setopt=protected_multilib=false
yum install libelf.so.1 -y
yum install libXrender.so.1 -y
yum install openmotif -y
yum install libXp.so.6 -y
yum install libXrandr.so.2 -y
yum install *xorg* -y
yum install libXp -y
yum install ld-linux.so.2 -y
yum install libstdc++.so.5 -y
yum install -y xterm

SSH: Transferred 0 file(s)

This error can stem from many causes; the most common are path errors and incorrectly parameterized shell commands.

Path error (Source files) – The pattern **/* refers to all files under the job’s workspace. Removing the prefix adjusts the source‑files directory; leaving it empty keeps the default. The remote directory is based on the server path, and the exec command runs on the remote host (e.g., service jenkins restart or /home/xx.sh).

Shell with parameters – The screenshot shows only the highlighted red box, indicating the script did not finish execution. Checking the script for syntax errors or mismatched parameters is necessary.

Further inspection revealed that two parameter names differed between the Jenkins configuration and the shell script, preventing proper execution. Aligning the names allowed the packaging step to complete successfully.

Another pitfall is misspelling a file or directory name, which makes Jenkins unable to locate the JAR or target folder, resulting in the same error. Careful verification of names avoids this issue.

With these adjustments the problems were resolved; the author will update the article with new issues as they arise.