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
libScriptChangeStateMachineJob.so
-r-xr-x--- 1 root cfgsoft 171456 Oct 31 15:01 libXpChangeDriverState.so
/opt/CMAgent/ECMu/1.0/registration:
-rw-r----- 1 root cfgsoft 622 Oct 31 15:01 cmagent.deb
-rw-r----- 1 root cfgsoft 2117 Oct 31 15:01 CMAgent.rpm
-r-xr-x--- 1 root cfgsoft 2299 Oct 31 15:01 RegisterAgent.sh
-r-xr-x--- 1 root cfgsoft 1044 Oct 31 15:01 UnregisterAgent.sh
/opt/CMAgent/ECMu/x.x/bin
There are three files in the bin directory that are used when you run inspections and remote commands.
n RunHigh. Runs privileged inspections, which is possible because it is owned by root and has the suid
permission set as seen with the r-s in the permissions.
n RunLow. Runs unprivileged inspections, which is possible because it is owned by the primary group (a
nobody group) of the user that the Agent runs as and has the sgid permission set.
When this program runs, it switches to the nobody group and cannot run commands that require root
privilege.
n RunRemote. Runs privileged remote commands and operates in the same manner as RunHigh.
/opt/CMAgent/ECMu/1.0/bin:
-r-xr-x--- 1 root cfgsoft 68697 Oct 31 15:01 Agent
-r-xr-x--- 1 root cfgsoft 53341 Oct 31 15:01 cabextract
-r-xr-x--- 1 root cfgsoft 111995 Oct 31 15:01 csipccli
-r-sr-x--- 1 root cfgsoft 11192 Oct 31 15:01 RunHigh
-r-xr-s--- 1 csi_acct csi_acct 11253 Oct 31 15:01 RunLow
-r-sr-x--- 1 root cfgsoft 9686 Oct 31 15:01 RunRemote
-r-xr-x--- 1 root cfgsoft 124059 Oct 31 15:01 TestMetadata
If these executable files fail, they log errors as described in"Run Executable Logging" on page 77.
/opt/CMAgent/ECMu/x.x/scripts
The scripts directory contains scripts that run with the Agent. The csi-agent file is a copy of the details
installed to the (x)inetd configuration. The inetd-agent is the script that (x)inetd runs when an attempt is
made to contact the Agent.
The stopagent.sh script stops all of the Agent processes in a clean manner.
/opt/CMAgent/ECMu/1.0/scripts:
-r-xr-x--- 1 root cfgsoft 351 Oct 31 15:01 boot-init.sh
-r--r----- 1 root cfgsoft 1279 Oct 31 15:01 boot-init.sh.lsb
-r--r----- 1 root cfgsoft 1439 Oct 31 15:01 boot-init.sh.RH
-r--r----- 1 root cfgsoft 3375 Oct 31 15:01 boot-init.sh.SuSE
-r--r----- 1 root cfgsoft 75 Oct 31 15:01 csi-agent
-r--r----- 1 root cfgsoft 249 Oct 31 15:01 csi-agent-xinetd
-r-xr-x--- 1 root cfgsoft 265 Oct 31 15:01 inetd-agent
-r-xr-x--- 1 root cfgsoft 4163 Oct 31 15:01 KillAgent.sh
-r-xr-x--- 1 root cfgsoft 1130 Oct 31 15:01 killprocs.sh
-r-xr-x--- 1 root cfgsoft 231 Oct 31 15:01 SrfHapErrorTemplate.xml
-r-xr-x--- 1 root cfgsoft 743 Oct 31 15:01 stopagent.sh
VCM UNIX Agent
VMware, Inc.
65