Home > Homelab > Why DNS is important…

Why DNS is important…

I finally managed to actually configure all the shared storage options I needed (and guess the opendedup appliance will need to make way for a less RAM and CPU consuming FreeNAS or homebrew NFS appliance).

VSM setup was extremely straight forward and also the configuration of the first vCloud Director cell looked very promising after I enabled connections from the public network in the Windows firewall on Port 1433…

Still I would only see a blank screen when trying to connect to the vCloud Director landing page.

vcd_failed_start

I never had a look at vCloud Director logs so far but there aren’t that many in the logs directory, so I took an educated guess.

vcloud-container-info.log:
2013-07-16 22:04:25,679 | INFO | pool-inittracker-1-thread-1 | ServiceInitializationTracker | Application initialization detailed status report: 0% complete
com.vmware.vcloud.common-util Subsystem Status: [WAITING]
com.vmware.vcloud.api-framework Subsystem Status: [WAITING]
com.vmware.vcloud.consoleproxy Subsystem Status: [WAITING]
com.vmware.vcloud.common-vmomi Subsystem Status: [WAITING]
com.vmware.vcloud.jax-rs-activator Subsystem Status: [WAITING]
com.vmware.pbm.placementengine Subsystem Status: [WAITING]
com.vmware.vcloud.vim-proxy Subsystem Status: [WAITING]
com.vmware.vcloud.fabric.foundation Subsystem Status: [WAITING]
com.vmware.vcloud.fabric.storage Subsystem Status: [WAITING]
com.vmware.vcloud.fabric.compute Subsystem Status: [WAITING]
com.vmware.vcloud.fabric.net Subsystem Status: [WAITING]
com.vmware.vcloud.backend-core Subsystem Status: [WAITING]
com.vmware.vcloud.ui.configuration Subsystem Status: [WAITING]
com.vmware.vcloud.imagetransfer-server Subsystem Status: [WAITING]
com.vmware.vcloud.rest-api-handlers Subsystem Status: [WAITING]
com.vmware.vcloud.jax-rs-servlet Subsystem Status: [WAITING]
com.vmware.vcloud.ui-vcloud-webapp Subsystem Status: [WAITING]
|
2013-07-16 22:04:32,928 | ERROR | SpringOsgiExtenderThread-3 | StdSchedulerFactory | Couldn’t generate instance Id! |
org.quartz.SchedulerException: Couldn’t get host name! [See nested exception: java.net.UnknownHostException: vcd1.vcloud.lab: vcd1.vcloud.lab]
at org.quartz.simpl.SimpleInstanceIdGenerator.generateInstanceId(SimpleInstanceIdGenerator.java:36)
at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:1167)
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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

[…]

Caused by: 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.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:157)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:570)
… 29 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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:145)
… 30 more

Well looks like we cannot get an instance id which prevents the service from starting up correctly. The reason for failing to get an instance id seems to be that we cannot resolve the hostname vcd1.vcloud.lab. A quick check with nslookup proofs that I obviously forgot to make the entry in the DNS server.

nslookup vcd1.vcloud.lab
Server: 192.168.10.10
Address: 192.168.10.10#53

** server can’t find vcd1.vcloud.lab: NXDOMAIN

After adding the hostname to the DNS server and a quick restart of the service my lab finally seems to be good to go for good now.

vcd_starting

Categories: Homelab Tags:
  1. September 26th, 2013 at 18:29 | #1

    Great post. Wish this would have come up first in my search. Had all my DNS names for the cell except the hostname of the VCD server itself! Doohh!

  2. Edgard
    February 7th, 2014 at 22:11 | #2

    you rock bud! That was definitely my issue! A simple a record on DNS solved it. thanks

  1. No trackbacks yet.