Enabling esxupdate logging on ESXi 4.x

Purpose

This article provides steps to configure esxupdate to produce persistent logs on ESXi. This information is useful when troubleshooting issues related to installing patches and updates on the ESXi host. By Default ESXi 4.1 is configured to use syslog for the esxupdate.log to conserve disk space.

Note: The steps in this article are only necessary for ESXi 4.x. On ESX 4.x, esxupdate logs persistently to/var/log/vmware/esxupdate.log.

Resolution

To configure the ESXi host's esxupdate utility to capture persistent logs:

  1. Open a console to the ESXi host. For more information, see Using Tech Support Mode in ESXi 4.1 (1017910).
  2. Make the configuration file /etc/vmware/esxupdate/esxupdate.conf writable using the command:

    chmod +w /etc/vmware/esxupdate/esxupdate.conf

  3. Open the configuration file /etc/vmware/esxupdate/esxupdate.conf in the vi text editor. For more information, seeEditing files on an ESX host using vi or nano (1020302).
  4. Change the file entry under the [log] section to the absolute path:

    [log]
    level = DEBUG
    file = /locker/db/esxupdate.log
    size = 1024000


  5. Save the file. The next time you run esxupdate, the specified log file is created.

    Note: The /locker/db/esxupdate.log log file persists across reboots and is included in a vm-support log bundle.

Purpose

This article provides steps to configure esxupdate to produce persistent logs on ESXi. This information is useful when troubleshooting issues related to installing patches and updates on the ESXi host. By Default ESXi 4.1 is configured to use syslog for the esxupdate.log to conserve disk space.

Note: The steps in this article are only necessary for ESXi 4.x. On ESX 4.x, esxupdate logs persistently to/var/log/vmware/esxupdate.log.

Resolution

To configure the ESXi host's esxupdate utility to capture persistent logs:

  1. Open a console to the ESXi host. For more information, see Using Tech Support Mode in ESXi 4.1 (1017910).
  2. Make the configuration file /etc/vmware/esxupdate/esxupdate.conf writable using the command:

    chmod +w /etc/vmware/esxupdate/esxupdate.conf

  3. Open the configuration file /etc/vmware/esxupdate/esxupdate.conf in the vi text editor. For more information, seeEditing files on an ESX host using vi or nano (1020302).
  4. Change the file entry under the [log] section to the absolute path:

    [log]
    level = DEBUG
    file = /locker/db/esxupdate.log
    size = 1024000


  5. Save the file. The next time you run esxupdate, the specified log file is created.

    Note: The /locker/db/esxupdate.log log file persists across reboots and is included in a vm-support log bundle.

Purpose

This article provides steps to configure esxupdate to produce persistent logs on ESXi. This information is useful when troubleshooting issues related to installing patches and updates on the ESXi host. By Default ESXi 4.1 is configured to use syslog for the esxupdate.log to conserve disk space.

Note: The steps in this article are only necessary for ESXi 4.x. On ESX 4.x, esxupdate logs persistently to/var/log/vmware/esxupdate.log.

Resolution

To configure the ESXi host's esxupdate utility to capture persistent logs:

  1. Open a console to the ESXi host. For more information, see Using Tech Support Mode in ESXi 4.1 (1017910).
  2. Make the configuration file /etc/vmware/esxupdate/esxupdate.conf writable using the command:

    chmod +w /etc/vmware/esxupdate/esxupdate.conf

  3. Open the configuration file /etc/vmware/esxupdate/esxupdate.conf in the vi text editor. For more information, seeEditing files on an ESX host using vi or nano (1020302).
  4. Change the file entry under the [log] section to the absolute path:

    [log]
    level = DEBUG
    file = /locker/db/esxupdate.log
    size = 1024000


  5. Save the file. The next time you run esxupdate, the specified log file is created.

    Note: The /locker/db/esxupdate.log log file persists across reboots and is included in a vm-support log bundle.
Based on VMware KB 1034329
  • 0 Kasutajad peavad seda kasulikuks
Kas see vastus oli kasulik?

Seotud artiklid

Hardware and firmware requirements for 64-bit guest operating systems

PurposeThis article explains the host machine hardware and firmware requirements for installing...

Logging in to the vCenter Server 5.0 Web Client fails with the error: unable to connect to vCenter Inventory Service

DetailsAfter upgrading from vCenter Server 4.1 to 5.0, you experience these symptoms:Cannot log...

Multiple network entries in vCenter Server 5.0.x after migrating virtual machines from a virtual switch to a virtual distributed switch

SymptomsAfter migrating virtual machines from a virtual switch to a virtual Distributed...

Minimum requirements for the VMware vCenter Server 5.x Appliance

PurposeIf you are using the VMware vCenter Server Appliance, beginning with vSphere 5.0 you can...