vSphere Web Client or vSphere Client service fails to start with the error: "Kernel failed to start within 600 seconds"
search cancel

vSphere Web Client or vSphere Client service fails to start with the error: "Kernel failed to start within 600 seconds"

book

Article ID: 312207

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • Fail to start the vSphere Web Client or vSphere Client service.
  • In the vsphere_client_virgo.log file, you see entries similar to:
[YYYY-MM-DDTHH:MM:SS.SSS+TT:TT] [ERROR] startup-tracker org.eclipse.virgo.medic.eventlog.default KE0004E Kernel failed to start within 600 seconds. 
[YYYY-MM-DDTHH:MM:SS.SSS+TT:TT] [INFO ] startup-tracker org.eclipse.virgo.medic.eventlog.default KE0011I Immediate shutdown initiated. 


Environment

VMware vCenter Server Appliance 6.7.x
VMware vCenter Server Appliance 6.5.x
VMware vCenter Server 6.5.x
VMware vCenter Server 6.0.x
VMware vCenter Server Appliance 6.0.x
VMware vCenter Server 6.7.x

Resolution

Issue is resolved in vCenter 6.7 U2 HTML client only. (For vSphere Client, we don't have any fix as it is no longer supported)


Workaround:

To work around the issue, restart the vSphere Web Client or vSphere Client service manually.


Additional Information

Appliance log location

  • Web Client: /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log
  • vSphere Client: /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log


Windows log location

  • Web Client: C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs\vsphere_client_virgo.log
  • vSphere Client: C:\ProgramData\VMware\vCenterServer\logs\vsphere-ui\logs\vsphere_client_virgo.log