vCloud Director fails to start
search cancel

vCloud Director fails to start

book

Article ID: 342281

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:
  • VMware vCloud Director takes a long time to start.
  • vCloud Director fails during startup.
  • The vCloud web portal fails to load.
  • The services are slow to start.
  • In the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log file, you see entries similar to:

    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jobScheduler' defined in URL [bundleentry://159/META-INF/spring/common-concurrent-bundle-context.x
    ml]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public static org.quartz.Scheduler com.vmware.vcloud.scheduler
    .impl.QuartzSchedulerFactory.createScheduler(com.vmware.vcloud.common.configuration.ConfigurationService) throws org.quartz.SchedulerException] threw exception; nested exception is java.lang.IllegalStateException: Cannot run without an instance id.
    at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:444)
    org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:435)
    ... 35 more
    Caused by: java.lang.IllegalStateException: Cannot run without an instance id.
    at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:1172)
    at org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.java:1451)
    at com.vmware.vcloud.scheduler.impl.QuartzSchedulerFactory.createInContext(QuartzSchedulerFactory.java:91)
    at com.vmware.vcloud.scheduler.impl.QuartzSchedulerFactory.createScheduler(QuartzSchedulerFactory.java:76)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    .....
    | ERROR | SpringOsgiExtenderThread-2 | ContextLoaderListener | Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.vmware.vcloud.common-util, config=osgibundle:/META-INF/spring/*.xml)) | org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jobSchedulerStarter' defined in URL [bundleentry://169.fwk590956692/META-INF/spring/common-concurrent-bundle-context.xml]: Cannot resolve reference to bean 'jobScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jobScheduler' defined in URL [bundleentry://169.fwk590956692/META-INF/spring/common-concurrent-bundle-context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public static org.quartz.Scheduler com.vmware.vcloud.scheduler.impl.QuartzSchedulerFactory.createScheduler(com.vmware.vcloud.common.configuration.ConfigurationService) throws org.quartz.SchedulerException] threw exception; nested exception is java.lang.IllegalStateException: Cannot run without an instance id.

  • You may also see this message in the log files:

    org.quartz.SchedulerException: Couldn't get host name! [See nested exception: java.net.UnknownHostException: vCloudDirector: vCloudDirector]


Environment

VMware Cloud Director 1.5.x
VMware Cloud Director 5.5.x
VMware Cloud Director 1.0.x
VMware Cloud Director 5.1.x

Cause

This issue may occur due to DNS failure.
The error UnknownHostException: vCloudDirector: vCloudDirector indicates that the specific vCloud Cell does not have a DNS entry for the hostname vCloudDirector. In this case, the DNS resolution fails and vCloud Director is not able to lookup or resolve the hostname for the Cell.

Resolution

To work around this issue, add a DNS entry to the /etc/hosts file in the system in which vCloud Director is installed. This resolves the hostname for the vCloud Cell.
For more information, see the Network Requirements section of the Cloud Director Installation and Configuration Guide.
To resolve this issue, ensure that the DNS setup is correct for all machines in the environment, including vCenter Server, the system hosting the Oracle database, other vCloud Cells, and the ESX hosts.