Log Locations of all VMware Products
In this post I tried consolidating all the VMware product’s log location for handy use.
- vCenter
- vCenter 6.0
- vSphere Profile-Driven Storage
- Inventory service
- vSphere Web Client service
- vCenter Single Sign-On 5.1
- vCenter Single Sign-On 5.5
- VMware Converter
- vCloud Director
- vShield Manager
- vShield Edge
- vCloud Usage Meter
- vCloud Connector
- vCenter Operations
- vRealize Automation Suite 6.x
- vCenter Orchestrator
vCenter
The vCenter Server logs are placed in a different directory on disk depending on vCenter Server version and the deployed platform:
vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%Application DataVMwareVMware VirtualCenterLogs
vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:ProgramDataVMwareVMware VirtualCenterLogs
vCenter Server 5.x Linux Virtual Appliance: /var/log/vmware/vpx/
vCenter Server 5.x Linux Virtual Appliance UI: /var/log/vmware/vami
Note: If the service is running under a specific user, the logs may be located in the profile directory of that user instead of %ALLUSERSPROFILE%.
| Usage | Log File Name |
| The main vCenter Server logs, consisting of all vSphere Client and WebServices connections, internal tasks and events, and communication with the vCenter Server Agent (vpxa) on managed ESX/ESXi hosts. | vpxd.log |
Profiled metrics for operations performed in vCenter Server. Used by the VPX Operational Dashboard (VOD) accessible at https://VCHostnameOrIPAddress/vod/index.html. |
vpxd-profiler.log, profiler.log |
| Non-fatal information logged about the vpxd process. | vpxd-alert.log |
| Common Information Model monitoring information, including communication between vCenter Server and managed hosts’ CIM interface | cim-diag.log and vws.log |
| Actions proposed and taken by VMware Distributed Resource Scheduler (DRS), grouped by the DRS-enabled cluster managed by vCenter Server. These logs are compressed. | drmdump: |
| Health reports for the Licensing Services extension, connectivity logs to vCenter Server. | ls.log |
| Dump of string used during the installation of vCenter Server with hashed information for DNS, username and output for JDBC creation. | vimtool.log |
| Provides information about the historical performance data collection from the ESXi/ESX hosts | stats.log |
| Health reports for the Storage Monitoring Service extension, connectivity logs to vCenter Server, the vCenter Server database and the xDB for vCenter Inventory Service. | sms.log |
| Health reports for the ESX Agent Monitor extension, connectivity logs to vCenter Server. | eam.log |
| Connectivity information and status of the VMware Webmanagement Services. | catalina..log and localhost..log |
| Health status of the VMwareVCMSDS service and individual ADAM database objects, internal tasks and events, and replication logs between linked-mode vCenter Servers. | jointool.log |
vCenter 6.0
The VMware vCenter Server 6.0 logs are located in the %ALLUSERSPROFILE%VMWarevCenterServerlogs folder.
The VMware vCenter Server Appliance 6.0 logs are located in the /var/log/vmware/ folder.
vCenter Server logs are grouped by component and purpose in these sub-directories:
|
vCenter Server
|
vCenter Server Appliance
|
Description
|
|
vmware-vpxvpxd.log
|
vpxd/vpxd.log
|
The main vCenter Serverlog
|
|
vmware-vpxvpxd-profiler.log
|
vpxd/vpxd-profiler.log
|
Profile metrics for operations performed in vCenter Server
|
|
vmware-vpxvpxd-alert.log
|
vpxd/vpxd-alert.log
|
Non-fatal information logged about the vpxd process
|
|
perfchartsstats.log
|
perfcharts/stats.log
|
VMware Performance Charts
|
|
eameam.log
|
eam/eam.log
|
VMware ESX Agent Manager
|
|
invsvc
|
invsvc
|
VMware Inventory Service
|
|
netdump
|
netdumper
|
VMware vSphere ESXi Dump Collector
|
| vapi | vapi | VMware vAPI Endpoint |
| vmdird |
vmdird |
VMware Directory Service daemon |
| vmsyslogcollector |
syslog |
vSphere Syslog Collector |
| vmware-spssps.log |
vmware-sps/sps.log |
VMware vSphere Profile-Driven Storage Service |
| vpostgres |
vpostgres |
vFabric Postgres database service |
| vsphere-client |
vsphere-client |
VMware vSphere Web Client |
| vws |
vws |
VMware System and Hardware Health Manager |
|
workflow
|
workflow |
VMware vCenter Workflow Manger |
| SSO | SSO | VMware Single Sign-On |
vSphere Profile-Driven Storage log files
The vSphere Profile-Driven Storage logs are placed in a different directory on disk depending on the vCenter Server version and the deployed platform:
- vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%Application DataVMwareInfrastructureProfile-Driven StorageLogs
- vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:ProgramDataVMwareInfrastructureProfile-Driven StorageLogs
- vCenter Server 5.x Linux Virtual Appliance: /var/log/vmware/vpx/spsNote: If the service is running under a specific user, the logs may be located in the profile directory of that user instead of%ALLUSERSPROFILE%.
| Usage | Log |
| The main Profile-Driven Storage logs, consisting of all vCenter Server and Management Webservices connections, internal tasks and events, and information about the storage profile integrity. | sps.log |
| This file consists of information about the installation of Profile-Driven Storage including computer name, operating system revision, the date of installation and the number of revisions that have been installed or upgraded on the system. | vim-sps-install.log |
| This file provides information about the state of the Java runtime environment. | wrapper.log |
vSphere Web Client service logs
For vSphere 5.0, all the logs for the vSphere Web Client service are located at:
- Windows: C:Program FilesVMwareInfrastructurevSphere Web ClientDMServerserviceability
- Linux: /usr/lib/vmware-vsphere-client/server/serviceability/
For vSphere 5.1, all the logs for the vSphere Web Client service are located at:
- Windows: C:ProgramDataVMwarevSphere Web Clientserviceability
- Linux: /var/log/vmware/vsphere-client/serviceability/
For vSphere 5.5, all the logs for the vSphere Web Client service are located at:
- Windows: C:ProgramDataVMwarevSphere Web Clientserviceability
- Linux: /var/log/vmware/vsphere-client/
| Usage | Log |
| The main vSphere Web Client log, consisting of all communication between underlying Flex endpoint connections, internal tasks and events | logsvsphere_client_virgo.log |
| Individual HTTP requests from the Web browser | logsaccesslocalhost_access_log..txt |
| Information about plug-in bundle communication | logsvirgo-serverlog.log |
| Time stamps of startup and shutdown of the vSphere Web Client service | eventlogs/eventlog.log |
vCenter Single Sign-On
The SSO logs are placed in a different directory on disk depending on the vSphere version and the deployed platform:
vSphere 5.1 using vCenter Single Sign-On 5.1:
vCenter Server 5.1.x on Windows Server 2003 – C:Program FilesVMwareInfrastructureSSOServerlogs
vCenter Server 5.1.x on Windows Server 2008/2012 – C:Program FilesVMwareInfrastructureSSOServerlogs
vCenter Server Virtual Appliance 5.1.x – /var/log/vmware/sso/
vSphere 5.5 using vCenter Single Sign-On 5.5:
vCenter Server 5.5.x on 2003 – %ALLUSERSPROFILE%Application DataCISlogs
vCenter Server 5.5.x and 2008, 2012 – C:ProgramDataVMwareCISlogs
vCenter Server Virtual Appliance 5.5.x – /var/log/vmware/sso/
Note: If the service is running under a specific user, the logs may be located in the profile directory of that user instead of %ALLUSERSPROFILE%.
Back to top
SSO 5.1
| Usage | Log |
| SSO installer log | Vminst.log |
| SSO Lookup Service log | vm_vim_ls.log |
| MSI installer for SSO installation log – verbose | vim-sso-msi.log |
| SSO database operations | vim-sso-javalib.log |
| Standard Tomcat logs | catalina.date.log |
| RSA’s Castle logs | imsTrace.log and imsSystem.log |
| SSO admin serve | ssoAdminServer.log |
| Lookup server log | lookupServer.log |
| Replication | replicationTransport.log |
SSO 5.5
| Usage | Log |
| SSO installer log | Vminst.log |
| MSI installer for SSO installation log – verbose | vim-sso-msi.log |
| SSO Service log | vim_ssoreg.log |
| Endpoint information about each of the SSO Solution Users and identity sources extracted from previous vCenter Single Sign On 5.1.0 instance | exported_sso.properties |
| MSI installer verbose log for OpenSSL installation | vim-openssl-msi.log |
| MSI installer verbose log for Python installation | vim-python-msi.log |
| MSI installer verbose log for MIT Kerberos installation | vim-kfw-msi.log |
| Promotion and demotion operation information for the SSO instance when joined or removed from a linked configurations | vmdirdvdcpromo.log |
| VMware Directory Service setup post-installation log containing information about the localhost | vmdirdvdcsetupIdu.log |
| Health reports for the VMware Directory Service (VMDir) service and the VMDir database | vmdirdvmdir.log |
| Key Distribution Center (kdc) run-time log, reports ports conflicts preventing the service from starting | vmkdcdvmkdcd.log |
| VMware Identity Management service run-time logs, time-stamped records of user attempts when accessing SSO for administrative purposes | vmware-ssovmware-sts-idmd.log |
| VMware Identity Management service performance counter logs | vmware-ssovmware-sts.ldmd-perf.log |
| Commons Daemon log once the Identity Management Service has started | vmware-ssoVMwareIdentityMgmtService. date.log |
vCenter Inventory Service
The vCenter Inventory Service logs are placed in a different directory on disk depending on the vCenter Server version and the deployed platform:
- vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%Application DataVMwareInfrastructureInventory ServiceLogs
- vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008:C:ProgramDataVMwareInfrastructureInventory ServiceLogs
- vCenter Server 5.x Linux Virtual Appliance: /var/log/vmware/vpx/inventoryserviceNote: If the vCenter Inventory Service is running under a specific user, the logs may be located in the profile directory of that user instead of %ALLUSERSPROFILE%.
| Usage | Log |
| The main vCenter Inventory Service logs, consisting of all vCenter Server and Single Sign-On connections, internal tasks and events, and information about the xDB. | ds.log |
| This file contains information about the installation of Inventory Service including computer name, operating system revision, the date of installation and the number of revisions that have been installed or upgraded on the system. | vim-is-install.log |
| This file provides information about the status of the Java runtime environment. | wrapper.log |
VMware Converter logs
There are also several ways to diagnose issues by viewing the VMware Converter logs. The logs can contain information that is not apparent from error messages. In newer versions of VMware Converter, you can use the Export Log Data button. Otherwise, logs are typically stored in these directories:
- Windows NT, 2000, XP, and 2003:
C:Documents and SettingsAll UsersApplication DataVMwareVMware Converter EnterpriseLogsC:WINDOWSTempvmware-converterC:WINDOWSTempvmware-temp
- Windows Vista, 7, and 2008:
C:UsersAll UsersApplication DataVMwareVMware Converter EnterpriseLogs
- Windows 8 and Windows 2012:
C:ProgramDataVMwareVMware vCenter Converter Standalonelogs-
- Note: In order to access this location in Windows Vista, 7, or 2008, you may need to go into the folder options and ensure thatShow Hidden Files is enabled and that Hide Protected Operating System Files is disabled.
C:WINDOWSTempvmware-converterC:WINDOWSTempvmware-temp
- Windows NT and 2000:
C:WINNTTempvmware-converterC:WINNTTempvmware-temp
- Linux:
$HOME/.vmware/VMware vCenter Converter Standalone/Logs/var/log/vmware-vcenter-converter-standalone
vCloud Director
| Component | Path |
| Cell Startup log. | $VCLOUD_HOME/logs/cell.log |
| Debugging log messages from the cell | $VCLOUD_HOME/logs/vcloud-container-debug.log |
| Warnings or errors in the cell | $VCLOUD_HOME/logs/vcloud-container-info.log |
| Log of the Watchdog service – which restarts the vCD service if it hangs or stops | $VCLOUD_HOME/logs/vmware-vcd-watchdog.log |
vShield Manager
vSM is a hardened Linux Appliance so use below commands in the vSM to view the logs
| Component | Commands |
| vShield Manager Log | Show logShow manager logShow manager log followShow manager log last |
vShield Edge logs
| vShield Edge log | Show log Show log follow |
vCloud Usage Meter
| Usage Meter Log | /var/log/usgmtr/um.log |
vCloud Connector logs
| Usage | Log |
| vCloud Connector Server Log | /opt/vmware/hcagent/logs/hcs.log |
| vCloud Connector Node Log | /opt/vmware/hcagent/logs/hca.log |
vCenter Operations
| Component | VM | Path |
| Admin UI | UI | /var/log/vmware/admin.log |
| vSphere UI | UI | $ALIVE_BASE/user/log/web_std.log |
| Custom UI | UI | $ALIVE_BASE/user/log/web.log |
| CapIQ | UI | /var/log/vmware/ciq.log |
| Upgrades | UI | /var/log/vmware/upgradecoordinator.log |
| ActiveMQ | AL | $ALIVE_BASE/user/log/activemq.log |
| Analytics | AL | $ALIVE_BASE/user/log/analytics.log |
| Collector | AL | $ALIVE_BASE/user/log/collector.log |
| Adapter | AL | $ALIVE_BASE/user/log/adapters//_.log |
vRealize Automation Suite 6.x
| vRealize Automation Virtual Appliance Locations |
Description
|
|
/var/log/vcac/catalina.out
|
tc Server Runtime logs, vRealize Automation webapp logs
|
|
/var/log/vco/app-server/catalina.out
|
vRealize Automation’s built-in vRealize Orchectrator logs
|
|
/var/log/apache2/access_log
|
Apache Access logs
|
|
/var/log/apache2/error_log
|
Apache GET/POST Error logs
|
|
/var/log/apache2/ssl_request_log
|
Apache SSL troubleshooting logs
|
| vRealize Automation Infrastructure as a Service Locations |
Description
|
|
C:Program Files (x86)VMwarevCACAgentsagent_namelogsfile
|
Plug-in logs example: CPI61, nsx, VC50, VC51Agent, VC51TPM, vc51withTPM, VC55Agent, vc55u, VDIAgent
|
| C:Program Files (x86)VMwarevCACDistributed Execution ManagerDEMORLogsDEMOR_All | Distributed Execution Manager logs |
| C:Program Files (x86)VMwarevCACDistributed Execution ManagerDEMWRLogsDEMWR_All | Distributed Execution Worker logs |
| C:Program Files (x86)VMwarevCACServerLogs | Manager Service logs |
| C:Program Files (x86)VMwarevCACServerConfigToolLogvCACConfiguration-date | Repository Configuration logs |
| C:Program Files (x86)VMwarevCACServerModel Manager DataLogsnothing_today | IIS Access logs (usually empty, but can be expected) |
| C:Program Files (x86)VMwarevCACServerModel Manager WebLogsRepository | Repository logs |
| C:Program Files (x86)VMwarevCACServerWebsiteLogsWeb_Admin_All | Web Admin logs |
| C:inetpublogs | IIS logs |
| Identity Virtual Appliance Locations | Description |
| /var/log/vmware/sso/catalina.out | ID VA tc Server Runtime logs |
| /var/log/vmware/sso/ssoAdminServer.log |
SSO Admin Server logsNote: Not applicable to vRealize Automation.
|
| /var/log/vmware/sso/vmware-identity-sts-perf.log | STS performance logs |
| /var/log/vmware/sso/vmware-identity-sts.log | STS logs |
| /var/log/vmware/sso/vmware-sts-idmd-perf.log | Identity service performance logs |
| /var/log/vmware/sso/vmware-sts-idmd.err | Identity service error logs |
| /var/log/vmware/sso/vmware-sts-idmd.log | Identity service logs |
| /var/log/vmware/vmafd/vmafdd.log | Identity VA logs |
| /var/log/vmware/vmdir/vdcsetupldu.log | Initial setup logs |
| /var/log/vmware/vmdir/vmafdvmdirclient.log | VMware SSO LDAP initial configuration logs |
| /var/log/vmware/vmkdc/vmkdcd.log | VMware SSO LDAP initial configuration logs |
| vRealize Application Services Location | Description |
| /home/darwin/tcserver/darwin/logs/catalina.out | Application Services tc Server Runtime logs |
| vMware vRealize Business Standard | Description |
| /usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/catalina.out | vRealize Business Advanced and Enterprise tc Server Runtime logs |
| /usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/auditFile.log | REST API requests |
| /usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/itfm-external-api.log | API logs |
| /usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/itfm-reflib-update.log | vRealize Business standard reference library related changes. |
| /usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/itfm-vc-dc.log | Data collector logs |
| /usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/itfm.log | vRealize Business Advanced and Enterprise logs |
| vCenter Server Appliance (VCSA) 5.5.x Locations | Description |
| /var/log/vmware/vpx/vpxd.log | vCenter VPXD logs |
| /var/log/vmware/vpx/vpxd-alert.log | vCenter VPXD alert logs |
| /var/log/vmware/vpx/vws.log | Management Web Service logs |
| /var/log/vmware/vpx/vmware-vpxd.log | vCenter VPXD status change logs |
| /var/log/vmware/vpx/inventoryservice/ds.log | vCenter Inventory Service logs |
| /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log | vSphere Client logs |
| /var/log/vmware/vsphere-client/logs/virgo-server/log.log | vSphere Client logs |
| /var/log/vmware/vsphere-client/eventlogs/eventlog.log | vSphere Client event logs |
| vCenter SSO Locations | Description |
| /var/log/vmware/sso/catalina.out | SSO tc Server Runtime logs |
| /var/log/vmware/sso/ssoAdminServer.log | SSO Admin Server logs (only in 5.5.x version) |
| /var/log/vmware/sso/vmware-identity-sts-perf.log | STS performance logs |
| /var/log/vmware/sso/vmware-identity-sts.log | STS logs |
| /var/log/vmware/sso/vmware-sts-idmd-perf.log | Identity service performance logs |
vCenter Orchestrator
Each VMware vCenter Orchestrator log file serves a different purpose. Review the following to understand what each log file does.
Notes:
- If you installed Orchestrator standalone, the default installation path is C:Program FilesVMwareOrchestrator.
- If you installed Orchestrator with the vCenter Server installer, the default installation path is C:Program FilesVMwareInfrastructureOrchestrator.
- Log file paths listed are relative to the default installation path.
| File | Default Location | Explanation |
| boot.log | app-serverservervmolog | In this log you find details on the JBOSS boot, but nothing related to the vCO server. It might be useful in cases where a file from JBOSS is missing or the install is corrupted. This kind of issue is very rare. |
| boot-state.log | app-serverservervmolog | In this log you will find the boot state of the vCO server. If the server booted properly it writes an entry together with the vCO version. This file can be useful as a summary of the boot of vCO server. This is included by default in server.log. |
| scripts-log.log | app-serverservervmolog | This file contains the thread from all the executions of workflows and actions. It lets you isolate these executions from normal vCO operations. You can find the same information in server.log. If you need to know which workflow was executed you need to look at server.log instead. |
| server.log | app-serverservervmolog |
This is the main log of vCO server. It contains the same information as boot-state.log,scripts-log.log in addition to more data. Everything that happens on the vCO server is seen here. When debugging vCO or any application running on vCO (such as LCM), this is the first log you should open.
|
| vmo-configuration.log | configurationjettylogs | In this log you find the configuration and validation of each component of vCO. This is the jetty service running on the vCO server. The file request.log, in the same directory, might be more useful if you want just a history of actions taken during configuration. |
| vmware_orchestrator_installer_output.txt |
C:tmp
Note: This path is not relative.
|
This is the log file containing all the information about the installation of vCO. It shows if vCO was silently installed by vCenter or if it was an independent install. It also indicates if the configuration service was started at install or if it was left stopped for security reasons. This file is the only way to detect an issue during an installation. |
| vso.log | apps | This is the client log. It is mainly interesting for connection issues with the server and events on the client side. |
| yyyy-mm-dd.request.log | configurationjettylogs | This log shows all the elements that were needed to load and display the pages of the configurator. It keeps a history of which actions were taken for the configuration of vCO and when they were done. This might be very useful to identify a change in the behavior of the vCO server after a restart. However, it does not display the value of changed parameters, only that they were changed. |
| wrapper.log | app-serverbin |
The wrapper log contains some information that is also found in the server.log. However this is the only place you will be able to know if the VMware vCenter Orchestrator Server service was restarted by the wrapper or by a user.
|
| vCenter_Orchestrator_InstallLog.log | On the desktop of the user who installed Orchestrator. | This file is created if you abort an installation or the installation fails. |
Back to top
Please comment if you need any additional products.
History:
22-June-2015 – Added vCenter 6.0
Tech Tip : Did you know now you can access your VMware workstation from anywhere on any device to remotely monitor virtual servers and machines using windows virtual desktop from www.CloudDesktopOnline.com. If you prefer a server, Rent a server with 24*7 impeccable tech-support from Apps4Rent.
Thanks Karthic………….. This is very useful and handy.
Appreciate your efforts on putting this detailed information.
Thank you for your feedback
An other example showing that Internet is not only a basket of crabs infested by hackers, phishers, and other thieves. Some blessed souls like you still exist ! Thanks a lot for a such effort. You rock !
Great concise information…Thank you..
Thanks buddy… Was at a customer site and this was very helpful because I had only mobile access and you have segregated things so nicely.
Thank you everyone for your feedback. it definitely motivates me to share more.
Please let me know if additional products needs to be added.
Updated with more products
Thanks for the detailed explanation of logs. Hope to have 6.0 logs soon.
Hello Karamjot,
vSphere 6.0 logs are updated