Epagent generates a zombie processes in unix

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)

Issue/Introduction

Epagent generates a zombie processes in unix

EPagent is started as below:

-go to /epagent/bin

./EPAgent register

-check for any zombie processes.

# ps auxwww | grep 'Z'

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND

root 20894 0.2 0.0 0 0 ? Z 04:35 0:00 [java] <defunct>

# pstree -p 20891

wrapper-linux-x(20891)─┬─java(20893)─┬─java(20894)

│ ├─{java}(20896)

│ ├─{java}(20897)

│ ├─{java}(20898)

│ ├─{java}(20899)

│ ├─{java}(20901)

│ ├─{java}(20905)

│ ├─{java}(20907)

│ ├─{java}(20908)

│ ├─{java}(20911)

│ ├─{java}(20912)

│ ├─{java}(20913)

│ ├─{java}(20914)

│ ├─{java}(20919)

│ ├─{java}(20921)

│ ├─{java}(20929)

..

Environment

Unix only

Valid for any EPAgent 10.5.1 and onward releases 

Cause

Zombie process is created by Java Service Wrapper whenever we start EPAgent as a service. We are using this third party software to run EPAgent as a deamon service. 

Below property is enabled by default:

    # The Wrapper will print out the exact version of the JVM in console mode only.

    wrapper.java.version.output=TRUE

We are using 3.5.25-pro Java Service Wrapper version, based on tanukisoftware documentation, this issue has been fixed this issue in 3.5.27-pro version. 

From: https://wrapper.tanukisoftware.com/doc/english/release-notes.html 

>> Fix a bug when the child process printing the JVM version became a zombie after completion (problem known on CentOS

    

Resolution

1. stop EPagent service

2. open epagent/conf/EPAService.conf file , set: wrapper.java.version.output=FALSE 

3. start EPagent service again