5.8

5. To enable VCM Patching debugging, type and run the following query:
update csi_hf_settings set val = '1' where setting = 'debug'
6. In Windows, in the Services Manager, restart the VCM Patch Management service.
What to do Next
Collect the VCM Patching logs.
Collect VCM Patching Logs
For problemswith the VCM Patching process, collect the VCM Patching log files.
Prerequisites
Turn on VCM Patching logging. See "Enable VCM Patching Logging" on page 25.
Procedure
1. With logging on, rerun the patching that produced the unwanted behavior.
2. On the Collector, navigate to the following VCM folder.
The default location is C:\Program Files (x86)\VMware\VCM\SUM\Collector
3. Copy the following TXT files.
CSISUMWorker_SumDBDebug.txt
CSISUMSvc_SumDBDebug.txt
CSISUMSvc_debug.txt
What to do Next
Using "Enable VCM Patching Logging" on page 25 as a guideline, turn VCM Patching logging back off. In
the query, set the value to zero (0).
Collect Agent Logging
To collect Agent logs, modify the logging configuration file on the Agent.
Procedure
1. Locate the following file.
The default location is agent-path\Installers\Providers\Logging.conf
If you are on a Collector, the default path for the same file is:
C:\Program Files (x86)\VMware\VCM\Installer\Providers\Logging.conf
2. Make a copy of Logging.conf so you can restore it later.
3. Open Logging.conf in a text editor.
4. Locate the [handler_fileHandler] section.
5. Change the args setting in that section to the directory where you want to store logs. For example:
args=('C:\tmp\provider.log', 'a')
6. From the Collector, rerun the action that caused the problem.
7. Review the log stored in the directory that you specified.
The directory contains all output generated during precollection, the action itself, and post-collection.
VCM Troubleshooting Guide
26
VMware, Inc.