search cancel

AWA: Solaris / HP-UX Agent listener process appears different then Linux

book

Article ID: 189370

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

When installing an Agent on Solaris, if you review the running processes, the format appears different than on Linux variants. The following is output from a 'ps -ef | grep ucx' command:


Solaris:

uc4     19755 19014  0 16:59:01 pts/4 0:01 /apps/uc4/agents/bin/ucxju64
nobody4 19891 19755 0 16:59:02 pts/4 0:00 /apps/uc4/agents/bin/ucxju64

HP-UX:

 65534 22865 22852  0  Jun  8  ?         0:25 /apps/UC4/agent_WO122_v123/bin/ucxjhi6
 uc4 22852 22814  0  Jun  8  ?         0:53 /apps/UC4/agent_WO122_v123/bin/ucxjhi6

Linux:

root     22219 20212 0 2019 ? 00:02:58 /opt/Automic/Automation.Platform/ServiceManager/bin/./../../Agents/unix/bin/ucxjlx6
nfsnobo+ 22227 22219 0 2019 ? 00:02:13 ucxjlx6-listener

This could lead an administrator to believe that Solaris/HP-UX is running two processes for the Agent, when not expected.

 

Cause

This is due to the Solaris/HP-UX implementation of the ps command.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

For Solaris:

If you use the pargs -a command, you will see the correct information. Here is an example of the listener process:

[email protected]:/#pargs -a 19891
19891:  /apps/uc4/agents/bin/ucxju64
argv[0]: ucxju64-listener

For HP-UX:

Unfortunately, relation between the agent process and listener can only been seen from their PID/PPID