Table of Contents
Advertisement
It is important to remember that the debug logs produced by VCM were never designed for the average
user. The messages contained in the logs have been specifically created to help developers understand
why VCM is operating the way it is. Always review the debug logs yourself and when necessary, forward
the log in its entirety on to VMware Customer Support for analysis. A sample debug log is provided
below.
It is not necessary for any support technician to be familiar with every message produced in a debug log,
but it is extremely helpful to know what the different types of errors logged in the debug log can mean
when determining the cause for a specific behavior. There are four major categories of error messages:
Info messages
n
Warning messages
n
Error messages
n
Exception messages
n
Info Messages
Info messages are the most common message category that you will find if VCM is configured to save
them. By default, Info messages are discarded by VCM when writing to the debug logs because the
volume of information produced by VCM under normal circumstances will make these log files grow
substantially. If, however, Info messages are enabled under the Administration slider, nearly every action
VCM performs will be logged in the various debug logs. Info messages are critical when diagnosing an
undesired behavior because it gives the developers a context surrounding the behavior.
Warning Messages
Warning messages are the next most common message category you will find in debug logs. Warnings
indicate a point in the process where an unexpected situation arose, but do not necessarily identify a
problem with VCM, as many common situations such as network timeouts or authentication problems
will produce a warning. Also, warning messages should not stop VCM from executing normal processes,
but they are intended to alert the developers of a possible problem.
VMware, Inc.
General Troubleshooting Guidelines
11
Advertisement
Table of Contents
Troubleshooting
