Skip to main content

Which ESX log file


Log FileNameDetails
/var/log/vmkernelVmkernelRecords activities related to the virtual machines and ESX host
/var/log/vmkwarningVmkernel WarningsA copy of everything marked as a warning or higher severity from vmkernel log. Easier to look through than vmkernel log
/var/log/vmksummaryVmkernel SummaryUsed for avaialability and uptime statistics. Human-readable summary in vmksummary.txt
/var/log/vmware/hostd.logHost Agent LogContains information on the agent that manages and configures the ESX host and its virtual machines
/var/log/vmware/vpxVirtualCenter AgentContains information on the agent that communicates with VirtualCenter
/var/log/messagesService ConsoleLog from the Linux kernel. Useful for underlying Linux issues. The kernel has no awareness of VMs running on the VMkernel
/var/log/vmware/esxcfg-boot.logESX Boot LogESX Boot log, logs all ESX boot events
/var/log/vmware/webAccessWeb AccessRecords information on Web-based access to ESX Server
/var/log/secureAuthentication LogContains records of connections that require authentication, such as VMware daemons and actions initiated by the xinetd daemon
/var/log/vmware/esxcfg-firewall.logESX Firewall LogContains all firewall rule events
/var/log/vmware/aamHigh Availability LogContains information related to the High Availability (HA) service
/var/log/vmware/esxupdate.logESX Update LogLogs all updates completed using the esxupdate tool
Labels:

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...
Read more

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N...
Read more

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...
Read more