VMware

VMware VirtualCenter 1.3.x Support Documentation


Features | Documentation | Knowledge Base | Discussion Forums

previous Prev   Contents   Last   Next next

Collecting Log Files

There are several files available that might be requested by the VMware technical support to help resolve your problem. The following describes script processes for generating and collecting some of these files.

Setting VirtualCenter Verbose Logging

There are two ways to set verbose logging.

Method one: Set verbose log in the VirtualCenter client.

1. Choose File > VMware VirtualCenter Settings > Advanced.

2. Scroll to the log.verbose parameter.

3. Set the parameter to a value of 1.

4. Click OK.

Method two: Enable logging:

1. Open or create one of the configuration files:

C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\config.ini

or

C:\Documents and Settings\All Users.WINNT\Application Data\VMware\VMware VirtualCenter\config.ini

2. Add the following line:

vpxd.logVerbose = "TRUE"

3. Restart the VirtualCenter service.

Collecting VirtualCenter Settings Information

1. From the VirtualCenter client, open the VMware VirtualCenter Settings and select the Advanced tab.

Select File > VMware VirtualCenter Settings. When the dialog box appears, select the Advanced tab.

2. Record the information in the server.options field. Click OK.

Collecting VirtualCenter Log Files

These files are useful when you submit requests to technical support.

1. Open a command prompt window.

For a VirtualCenter Client — Log onto the machine running VirtualCenter Client, using the same login as the user who encountered the error, and open a command prompt window.

For a VirtualCenter Server — Log onto the machine running VirtualCenter Server, using a local Windows administrator account, and open a command prompt window.

2. Change to the directory where VirtualCenter is installed.

For example, if the default installation directory was used:

cd c:\Program Files\VMware\VMware VirtualCenter\

3. Run the following command to collect the logs:

cscript vclogs.wsf

For example:

cscript vclogs.wsf /n:all /o:vclog.txt

To view help for the command, type:

cscript vclogs.wsf /?

Help content is:

Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

This script collects VMware VirtualCenter log files to help VMware customer support diagnose your problem.

Usage: vclogs.wsf [/?] [/n:value] [/o:value]

Options:
? : Displays this help
n : Number of logfiles to collect, default is 10.
Specify 'all' to get all the logs.
o : Output filename, default is VirtualCenterLogs-username-date.

4. If you are using VirtualCenter version 1.3.0 or older: Locate and provide the VirtualCenter log.

The location of the VirtualCenter log is dependent on the platform it is running on as well as the user it is running as.

Generally, the log is in temp directory. The temp directory for the system user is different on different platforms, but typically it is one of the following:

C:\WINDOWS\Temp (on Windows XP)

C:\WINNT\Temp (on Windows 2000 or Windows 2003).

In either of these directories, there are files named as follows:

vmware-vpxd-SYSTEM-<process_id>.log

5. If you are using VirtualCenter version 1.3.0 or older: Locate and provide the log files: vmmsi.log and vminst.log. They are typically located in:

c:\documents and settings\administrator\local settings\temp\

6. Locate and provide the Event Viewer Log files from the VirtualCenter server.

a. Log on as a user with VirtualCenter Administrator privileges.

b. Export the files in the default event viewer format with .evt extensions.

7. Place all the required files, including the Event Viewer Log files and output directory, into a zip file.

Incorporate a timestamp into the zip file name.

Collecting ESX Server VMkernel Files

If the VMkernel fails, normally an error screen appears for a period of time and then the virtual machine reboots.

If you specified a VMware core dump partition when you configured your virtual machine, the VMkernel also generates a core dump and error log.

More serious problems in the VMkernel can freeze the machine without an error screen or core dump.

Collecting ESX Server Service Console Files

This script collects and packages all relevant ESX Server system and configuration information and ESX Server log files. This information can be used to analyze the problem you are encountering.

1. Run the following script on the service console:

/usr/bin/vm-support

2. Save the resulting file:

esx-<date>-<unique-xnumber>.tgz

Collecting ESX Server Service Log Files

You can enable logging for the VMware Authorization Service (known as vmware-authd on Linux managed hosts) manually.

1. In a text editor, open the following file:

  • On a Windows managed host, edit config.ini, located in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter.
  • On a Linux managed host, edit /etc/vmware/config.

    • 2. Add the following lines to the file:

    vmauthd.logEnabled = TRUE
    log.vmauthdFileName = "vmauthd.log"

    This creates a file called vmauthd.log. On a Windows managed host, this file appears by default in C:\Windows\system32 or C:\WINNT\system32; on a Linux managed host, this file appears by default in /var/log/vmware.

    3. Save and close the configuration file. The log is enabled on a Linux-managed host.

    4. On a Windows-managed host, restart the VMware Authorization Service. Choose Start > Administrative Tools > Services. Right-click VMware Authorization Service and choose Restart. This enables logging.

    Collecting GSX Server Files and Logs Using Scripts

    The GSX Server log files are generated by GSX Server and are collected by the support script as needed. Since there is no support script on a remote GSX Server client, you need to submit a support request at www.vmware.com/requestsupport for any issues you encounter on a client and include the console's log file or its installation log file.

    With GSX Server hosts, you can simplify the process of collecting the needed information by running the support script to collect the appropriate log files and system information. Follow the steps below that apply to your managed host computer.

    Note: The support script runs only on the GSX Server host. If you encounter problems on a remote client, you must supply the log files manually. The two log files you should supply, depending upon the problem you encounter on the client, are the VMware Virtual Machine Console log file and the installation log file. See below for more information about these logs.

    Running GSX Server Scripts for Windows Hosts

    1. Open a command prompt.

    2. Change to the GSX Server program directory.

    C: cd \Program Files\VMware\VMware GSX Server

    If you did not install the program in the default directory, use the appropriate drive letter and substitute the appropriate path in the cd command above.

    3. Run the support script.

    cscript vm-support.vbs

    4. After the script runs, it displays the name of the directory where it has stored its output. Use a file compression utility such as WinZip or PKZIP to zip that directory, then include the zip file with your support request.

    Running GSX Server Scripts for Linux Hosts

    1. Open a terminal.

    2. Run the support script as the user who is running the virtual machine or as root.
    vm-support

    If you are not running the script as root, the script displays messages indicating that it cannot collect some information. This is normal. If the VMware support team needs that information, a support representative may ask you to run the script again as root.

    3. The script creates a compressed .tgz file in the current directory. Include that output file with your support request.

    previous Prev   Contents   Last   Next next