Posts Tagged ‘Log’

VMware: Service ´VMware Kdc Service’ (VMwareKdcService) failed to start

August 13th, 2014 No comments

Last week I upgraded VMware vCenter server from version 5.0 to 5.5 Update 1c, during installation of vCenter Single Sign-On 5.5 I received this warning message:

Service ‘VMware Kdc Service’ (VMwareKdcService) failed to start. Verify that you have sufficient privileges to start system services



The service account which I´m using for the upgrade is Domain Administrator, I tied to start the service manually but the service won’t start. The Windows Event log was clean, but in the vmkdcd.log file (located at: C:\ProgramData\VMware\CIS\logs\vmkdcd) I found this error logs:

20140812092452.000:t@0:TRACE: Vmkdcd: stop
20140812092458.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp called…
20140812092458.000:t@0:TRACE: dwError=87 errno=17
20140812092458.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp done.
20140812092458.000:t@0:TRACE: ERROR: vmkdc VmKdcInit failed (87)

20140812092458.000:t@0:TRACE: Vmkdcd: stop
20140812092503.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp called…
20140812092503.000:t@0:TRACE: dwError=87 errno=17
20140812092503.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp done.
20140812092503.000:t@0:TRACE: ERROR: vmkdc VmKdcInit failed (87)
20140812092503.000:t@0:TRACE: Vmkdcd: stop



To resolve this issue, ensure port 88 is available for use by the VMware Kdc Service:

  1. Use netstat from an elevated command prompt on the Windows host system to confirm port 88 is not in use. For more information on using the netstat command, see Determining if a port is in use (1003971).
  2. If another application is using port 88, reconfigure or disable the application to open port 88 for use with the VMware Kdc Service.

In my case VMware Converter Standalone Server was running and configured at port 88, I removed the installation and restarted the Single Sign-On setup.

More information: VMware

VMware: System logs on host [hostname] are stored on non-persistent storage

April 7th, 2014 1 comment

Last week I installed some new vSphere hosts with flash disk storage. Some hosts has a yellow caution icon and a message stating:

Configuration Issues – System logs on host [hostname] are stored on non-persistent storage.




Verify the location of System logs:

  1. In vSphere Client, select the host in the inventory panel.
  2. Click the Configuration tab, then click Advanced Settings under Software.
  3. Ensure that points to a persistent location.

    The directory should be specified as [datastorename] path_to_file where the path is relative to the datastore. For example, [datastore1] /systemlogs.

  4. If the field is empty or explicitly points to a scratch partition, make sure that the field ScratchConfig.CurrentScratchLocation shows a location on persistent storage.



After a few minutes the logs are stored at the new location (in this case I used central storage):

More information: VMware

VMware: Cannot delete virtual machine from disk with more then 100 active snapshots

March 19th, 2013 1 comment

Today I tried to delete a virtual machine with more then 100 (damn Backup Exec) snapshots, in the vSphere Client I selected in the inventory:  “Delete from disk”  , few seconds later I received this error message:

Cannot complete the operation due to an incorrect request to the server


Events directly at the vSphere 5.0 host:

Warning message from ESXHOST: This virtual machine has more than 100 redo logs in a single branch of its snapshot tree. Deleting some of the snapshots or consolidating the redo logs will improve performance. The maximum number of redo logs supported is 255.

Virtual machine disks consolidation failed.


With this simple PowerCLI command I was able to remove the virtual machine include all active snapshots

Remove-VM "VM" -DeletePermanently -Confirm:$false


VMware: Xtravirt vLogView

January 21st, 2010 No comments

Xtravirt published vLogView, with this tool you can view/search easy in VMware ESX events, by connecting vCenter server you can add multiple hosts and download the logfiles for some troubleshooting.

Read more…