ucxjlx6s trace files are showing

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

"stale" Active process that may look like a zombie process in Linux agent

root 18723 17564 0 11:02 pts/1 00:00:00 /opt/###/###/automic/v12u/agents/linux/bin/ucxjlx6
v12 18739 1 0 11:03 ? 00:00:00 /opt/###/###/automic/v12u/agents/linux/bin/./ucxjlx6s -s 37249 -u v12 -trc 9 -trcpath /opt/###/###/automic/v12u/agents/linux/temp -maxidle 600
v12 18743 1 0 11:03 ? 00:00:00 /opt/###/###/automic/v12u/agents/linux/bin/./ucxjlx6s -s 25567 -u v12 -trc 9 -trcpath /opt/###/###/automic/v12u/agents/linux/temp -maxidle 600
v12 18747 1 0 11:03 ? 00:00:00 /opt/###/###/automic/v12u/agents/linux/bin/./ucxjlx6s -s 55608 -u v12 -trc 9 -trcpath /opt/###/###/automic/v12u/agents/linux/temp -maxidle 600
v12 19284 17564 0 11:13 pts/1 00:00:00 grep --color=auto /opt/automic/v12u/agents/linux/bin
SFDC Error Message: [v12@<hostname> bin]$ ps -ef|grep $PWD
root 18723 17564 0 11:02 pts/1 00:00:00 /opt/###/###/automic/v12u/agents/linux/bin/ucxjlx6
v12 18739 1 0 11:03 ? 00:00:00 /opt/###/###/automic/v12u/agents/linux/bin/./ucxjlx6s -s 37249 -u v12 -trc 9 -trcpath /opt/###/###/automic/v12u/agents/linux/temp -maxidle 600
v12 18743 1 0 11:03 ? 00:00:00 /opt/###/###/automic/v12u/agents/linux/bin/./ucxjlx6s -s 25567 -u v12 -trc 9 -trcpath /opt/###/###/automic/v12u/agents/linux/temp -maxidle 600
v12 18747 1 0 11:03 ? 00:00:00/opt/###/###/automic/v12u/agents/linux/bin/./ucxjlx6s -s 55608 -u v12 -trc 9 -trcpath /opt/###/###/automic/v12u/agents/linux/temp -maxidle 600
v12 19284 17564 0 11:13 pts/1 00:00:00 grep --color=auto /opt/###/###/automic/v12u/agents/linux/bin

Environment

Release : 12X

Component : AUTOMATION ENGINE

Cause

• By default the spawned io-service process will be alive at least for 10 minutes.
  
  
• Those processes are for file events that use the 'File Stable' or 'File Changed' settings. For each active file event on that agent there's one process on the system (as in that case the agent has to check for the file, not the engine any more ...) This means you just have lots of file events on that agent using that feature. It's not a trace but a start parameter for the sub task.

Resolution

So if you launch events you must wait at least 10 minutes and do not launch any new event that this child processes will disappear.