5.8
Table Of Contents
- VMware vRealize Configuration Manager Troubleshooting Guide
- Contents
- About This Book
- Troubleshooting Overview
- Types of Problems
- Gathering Diagnostic Information
- What to Send to VMware Technical Support
- Capture a Desktop Image
- Capture a Window Image
- Set the Debug Log to Store all Message Types
- Extract the Debug Log
- Extract SQL Server Logs
- Collect IIS Logs
- Collect ARS Files
- Collect the UNIX Syslog Messages
- Collect Import/Export Tool Logs
- Extract Windows Event Logs
- Extract Windows System Information
- Collect UNIX ETL Logs
- Collect VCM Installation Logs
- Enable VCM Patching Logging
- Collect VCM Patching Logs
- Collect Agent Logging
- Troubleshooting Problems with VCM
- Patch Content Does Not Download for Red Hat and SUSE Machines
- Signed Patch Content Cannot Be Validated
- Mismatched Security Setting for AIX Patch Staging with NFS
- UNIX Patch Deployment Fails
- UNIX Patch Assessment Returns No Results
- Patch Deployment Jobs Might Time Out
- UNIX Bulletins Missing from the Required Location
- Report and Node Summary Errors
- Report Parameter Errors
- Protected Storage Errors
- SSL Becomes Disabled
- Troubleshooting the vSphere Client VCM Plug-In
- vSphere Client VCM Plug-In Is Not Enabled
- Cannot Register the vSphere Client VCM Plug-In
- Invalid Certificate on a vSphere Client
- Collector Not Running
- HTTPS/SSL Is Not Configured on the Collector
- Collection Unsuccessful
- Machines Not Listed in the Collect Available List
- Machines Not Listed in the Available List for Any Action
- ESX Servers Are Not Displayed
- VCM Windows Agent
- Windows Agent Installation Environment
- Windows Agent Installation Process
- Detect Previous Install
- Validate Installation Environment
- Interrogate Target Environment
- Resolve Uninstall Dependencies
- Uninstall Module
- Uninstall Module Installer
- Install Simple Installer
- Install Module Installer
- Resolve All Versions of Modules Based on Highest Version Number
- Install Module
- Fully Release the Synchronization Lock on the Target Machine
- Submit Request to Agent
- Check If Request Is Complete
- Transfer Request Results
- Acknowledge Successful Data Transfer
- Prepare Request Results for Insert
- Insert Data Into Database
- Transform Inserted Data
- Cleanup Machine Data
- Partially Release the Synchronization Lock on the Target Machine
- Cleanup Request Data
- Windows Agent Uninstallation Process
- Detect Previous Install
- Validate Installation Environment
- Interrogate Target Environment
- Resolve Uninstall Dependencies
- Uninstall Module
- Uninstall Module Installer
- Fully Release the Synchronization Lock on the Target Machine
- Partially Release the Synchronization Lock on the Target Machine
- Cleanup Request Data
- Windows Agent Upgrade Process
- Windows Agent Manual Installation Process
- Windows Agent Communication Protocols
- Communication Protocol Change Process
- Detect Previous Install
- Uninstall Agent
- Uninstall Package Installer
- Uninstall Basic Installer
- Validate Installation Environment
- Install Simple Installer
- Store Installation Data in the Database
- Install Module Installer
- Fully Release the Synchronization Lock On the Target Machine
- Submit Request to Agent
- Check If Request Is Complete
- Transfer Request Results
- Acknowledge Successful Data Transfer
- Prepare Request Results For Insert
- Insert Data Into Database
- Transform Inserted Data
- Cleanup Machine Data
- Partially Release the Synchronization Lock on the Target Machine
- Cleanup Request Data
- Debug Window Agent Installations
- VCM UNIX Agent
- UNIX Agent Directory Structure After Installation
- /opt/CMAgent
- /opt/CMAgent/Agent
- /opt/CMAgent/CFC
- /opt/CMAgent/data
- /opt/CMAgent/data/db
- /opt/CMAgent/data/db/DtmDB/RDM
- /opt/CMAgent/data/db/PDS
- /opt/CMAgent/data/db/SM/RDM
- /opt/CMAgent/ECMu
- /opt/CMAgent/ECMu/x.x/bin
- /opt/CMAgent/ECMu/x.x/scripts
- /opt/CMAgent/install
- /opt/CMAgent/Installer
- /opt/CMAgent/ThirdParty
- /opt/CMAgent/ThirdParty/x.x/PatchAssessment
- /opt/CMAgent/uninstall
- Directories Created During an Inspection
- Directory of Executed Scripts and Results
- Collector Certificates
- Patch Assessment
- Exploratory UNIX Agent Troubleshooting
- UNIX Agent Directory Structure After Installation
- Index
If the Results directory is not deleted, look for a DBE file in the directory and copy it to the Collector for
viewing.
To examine the ZRP file on the Agent, capture it when it is created. See "Capture the ZRP on the Agent" on
page 75.
Capture the ZRP on the Agent
The Agent sends the Results.zrp file to the Collector, and deletes it after the Collector acknowledges
receipt of the file. To examine the ZRP file on the Agent, capture a copy when the file is created, before the
Agent deletes it.
Procedure
Enter the following shell command.
until ls *zrp 2>/dev/null; do sleep 1; done; cp *zrp save.zrp
Logging Errors
The following file captures errors reported by the Agent processes that are not specific to a request, such
as when an unauthorized Collector tries to contact the Agent.
(Linux) /var/log/CSI/log/DebugEvent_Default.dbe
(Solaris) /var/adm/CSI/log/DebugEvent_Default.dbe
After the Agent begins processing a request, it switches to capturing errors in a DBE file in the following
directory. The DBE file is eventually returned to the Collector.
/opt/CSI/data/collector-name/request-ID
NOTE Effective DBE interpretation often requires expert knowledge of the Agent software.
The following file captures errors when they occur before the Agent logs to the DebugEvent_
Default.dbe file. You might need to check /etc/syslog.conf to verify that entries are being written
to the messages file.
(Linux) /var/log/messages
(Solaris) /var/adm/messages
To make the Agent log additional entries to the messages file, edit
/opt/CMAgent/ECMu/1.0/scripts/inetd-agent, and add –b immediately before –u. The -b causes
the CsiAgentListener to log information about which user and group it is using, each step as it
daemonizes itself to detach from (x)inetd, and when it exits.
If you suspect a race condition in startup, shutdown, and communication between CsiAgentListener
and Agent or CsiListenerWorkerDaemon, enable informational messages, which reveal each of the
processes starting up, shutting down, checking to see that it is safe to shut down, and determining that the
process is available to be contacted. Edit /opt/CMAgent/ECMu/1.0/scripts/inetd-agent, and add
LOG_INFOS=1 immediately before CSI_REGISTRY_PATH.
Inspections are Failing
The following files capture errors when inspections are failing.
(Linux) /var/log/secure
(Solaris) /var/adm/messages
Look for the following errors in the files.
VCM UNIX Agent
VMware, Inc.
75