Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vCloud Director fails to start (1028117)

Last Updated: 7/9/2014Categories: TroubleshootingTotal Views: 9478Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

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]

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director

Related Versions:

VMware Cloud Director 5.5.x

VMware Cloud Director 5.1.x

VMware Cloud Director 1.5.x

VMware Cloud Director 1.0.x

Take Our Survey

Support Assistant