5.8

running. When a collection occurs, a second lm appears for the Collector-specific data model (DtmDB).
To list all Collector directories, with the most recently collected directory at the top, type find
/opt/CMAgent/data -name Master | xargs ls -ldt
Monitor Processes with the top Utility
If the top utility is installed and available, you can use it to monitor processes.
Procedure
1. Start the top utility.
2. Type u.
3. At the Which User (Blank for All): prompt, type the user account that the Agent is installed as.
4. Type s.
5. At the Delay between updates: prompt, type 1.
Agent Was Reinstalled
The first collection after reinstalling the Agent always fails, and returns an error stating that the replication
timestamp is out of sync.
Performing a second collection forces the Collector to re-replicate the data model to the Agent.
Monitoring Collections
At the first collection, the following directory appears when the Agent starts to process the replicated data
model.
/opt/CMAgent/data/db/DtmDB/RDM/collector-name
Next, the following directory appears when the Agent begins to process the inspection request.
/opt/CMAgent/data/collector-name
On subsequent collections, an additional directory appears when the Agent begins to process the
inspection request. The request ID format is similar to a Windows GUID.
/opt/CMAgent/data/collector-name/request-ID
The request ID directory contains files downloaded for remote commands, and a Results directory to
hold files that will be returned. To monitor the Results directory, do the following.
n To see HDS files being created for each individual data class, type ls –lt
The most recently inspected data class appears at the top of the list. If the Agent seems to have stopped,
the list shows which data class it was processing at the time.
Typing ps –ef | grep gawk | grep –v grep shows if the Agent is actively inspecting the data class and
might show if the gawk script has hung. For example, gawk hangs when trying to perform a checksum
on a pipe file.
n To report the number of files in the directory, type ls | wc –l
A collection of all data classes generally creates about 40 files in the Results directory, including HDS
files and FileUpload* files. It might also create a debug event (DBE) file.
After inspection finishes, the contents of the Results directory are zipped and stored as follows, and the
Results directory is deleted.
/opt/CMAgent/data/collector-name/Package/request-ID.zrp
VCM Troubleshooting Guide
74
VMware, Inc.