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:
- Open a console to the ESXi host. For more information, see Using Tech Support Mode in ESXi 4.1 (1017910).
- Make the configuration file
/etc/vmware/esxupdate/esxupdate.conf
writable using the command:chmod +w /etc/vmware/esxupdate/esxupdate.conf
- 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). - Change the file entry under the
[log]
section to the absolute path:[log]
level = DEBUG
file = /locker/db/esxupdate.log
size = 1024000 - 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 avm-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:
- Open a console to the ESXi host. For more information, see Using Tech Support Mode in ESXi 4.1 (1017910).
- Make the configuration file
/etc/vmware/esxupdate/esxupdate.conf
writable using the command:chmod +w /etc/vmware/esxupdate/esxupdate.conf
- 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). - Change the file entry under the
[log]
section to the absolute path:[log]
level = DEBUG
file = /locker/db/esxupdate.log
size = 1024000 - 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 avm-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:
- Open a console to the ESXi host. For more information, see Using Tech Support Mode in ESXi 4.1 (1017910).
- Make the configuration file
/etc/vmware/esxupdate/esxupdate.conf
writable using the command:chmod +w /etc/vmware/esxupdate/esxupdate.conf
- 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). - Change the file entry under the
[log]
section to the absolute path:[log]
level = DEBUG
file = /locker/db/esxupdate.log
size = 1024000 - 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 avm-support
log bundle.