5.8

MAC
CSI_REGISTRY_PATH=/opt/CMAgent DYLD_LIBRARY_
PATH=/opt/CMAgent/CFC/3.0/lib:/opt/CMAgent/ThirdParty/1.0/lib
/opt/CMAgent/CFC/3.0/bin/CSI_ManageCertificateStore –iz –fpath-to-
pem/filename.pem
AIX
CSI_REGISTRY_PATH=/opt/CMAgent
LIBPATH=/opt/CMAgent/CFC/3.0/lib:/opt/CMAgent/ThirdParty/1.0/lib
/opt/CMAgent/CFC/3.0/bin/CSI_ManageCertificateStore –iz –fpath-to-
pem/filename.pem
Because certificate information is maintained in memory while the Agent is running, you must restart the
Agent after you add a certificate. Agents that run in inetd mode periodically stop themselves, but Agents
that run in daemon mode need to be manually restarted.
Patch Assessment
VCM 5.0 and later can do patch assessment inspections. Support for these inspections includes new
metadata in the Collector IMD tables. The new metadata gets replicated to the Agent the same way as
previous metadata—at first communication between Collector and Agent, all metadata is sent in the initial
request, and the Agent stores the metadata on a per-Collector basis in
/opt/CMAgent/data/db/DtmDB/RDM/collector-name. On subsequent requests from the Collector,
only modified metadata is replicated to the Agent.
The files needed for patch assessment are stored in the
/opt/CMAgent/data/db/DtmDB/RDM/collector-name/PatchContent directory. This directory
contains Lumension patch data (PLS files) for each patch to be evaluated.
When patch assessment data exists, the large initial copy operation might be a problem. The size of an
initial request might cause the ListenerWorkerDaemon and Agent processes to grow to over 250MB
each. To protect the Agent machine from excessively large VCM processes, Agents earlier than 5.0 shut
down the processes when they exceed approximately 150MB. In 5.0 and later, Agents allow up to
approximately 380MB before shutting down the processes.
Exploratory UNIX Agent Troubleshooting
Problems with the UNIX Agent might be varied, occur because of factors that are not readily observable,
and be difficult to work around by following tightly constrained instructions. The following sections
explain some of the broad circumstances that might arise and the approaches that you might take to
identify and solve the problem.
Installation Errors
If the UNIX Agent installation reports an error, explore the following.
n Copy /opt/CMAgent/install/DebugEvent_cis.dbe to a Collector, and examine its contents using
the Debug Event Viewer.
n Examine the contents of /opt/CMAgent/install/BootstrapInstall.log using a text editor.
n Examine /opt/CMAgent/install/csi.config using a text editor. The file contains installation
configuration information, including which user account can run the Agent.
n Examine the contents of /opt/CMAgent/install/install.log using a text editor.
VCM UNIX Agent
VMware, Inc.
71