Geek Answers Handbook

Jenkins build never finishing

I have a Jenkins master / slave that works quite happily by launching Oracle imports on some Linux boxes.

I just added a new node slave and tried to run our existing database import job in this new node. This work consists of three subprojects; the first launches some execution shells, copies files and changes permissions, and this completes at the moment, the second starts the execution shell, which ends with Oracle impdp. The impdp command exits (db exists, but ps -efimpdp no longer works), but the Jenkins subproject never ends. The user interface just sits there when the watch is torn around.

I tried adding an echo after impdp, and it also does the job correctly, but the subproject is still not ending.

If I add a Post-Build notification, it will not be sent.

A third subproject has never been achieved.

What could be causing this and how am I debugging what is happening?

+4
source share
3 answers

It turned out to be something terrible :-)

After completing the work, Jenkins tries to kill all the processes that he spawned. To identify them, it goes through all the processes in the OS, reads from /proc/<pid>/environ(this is the Linux box), which contains the process environment variables and compares them with the environment that it sets up for Jenkins processes.

, db Oracle, , /proc/pid/environ , - .

, , DBA. , .

+3

": ", 10 20 . , LogRotator.

, . - , , , .

: https://issues.jenkins-ci.org/browse/JENKINS-22607

, , , , .

+4

set +x , , . , , .

0

More articles:


All Articles