VMware Cloud Community
CSIEnvironments
Enthusiast
Enthusiast

So it looks like I've crashed my vCD Appliance...

My Lab Setup:

2 Hosts in 1 cluster.

4 nics in each.

Both Esxi 5 hosts have the same 2 test luns presented to them (1TB each).


What I did:

Vmotioned all vm's from ESX1 to ESX2 and put ESX1 into maintenance mode.

Powered off ESX2. Powered it back on.

Connected directly to ESX2 and powered on LAB_VC, VMware vCloud Director and the vShield Manager.

Now the vCloud Director web ui will not work, also cannot telnet to port 1521.

The admin console works (port 5480) and all the ip settings and everything checks out.

Restarted the box a few more times just to check it wasn't some anomaly.

Cleared out the log files, started it up and went through the logs files. The only error I found were in vcloud-container-info.log and vcloud-container-debug.log:

vcloud-container-debug.log:

2012-02-26 20:46:44,555 | INFO     | Start Level Event Dispatcher | ServiceInitializationTracker   | Application startup begins: 2/26/12 8:46 PM |
2012-02-26 20:46:45,549 | DEBUG    | Start Level Event Dispatcher | EncryptionManager              | EncryptionManager configured with system key. |
2012-02-26 20:46:45,578 | DEBUG    | Start Level Event Dispatcher | PassThroughDecrypter           | decrypting |
2012-02-26 20:46:45,938 | DEBUG    | Start Level Event Dispatcher | EncryptionManager              | EncryptionManager has been loaded successfully. |
2012-02-26 20:46:46,671 | DEBUG    | Start Level Event Dispatcher | PooledConnection               | Unable to connect to database. |
java.sql.SQLException: The Network Adapter could not establish the connection
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:412)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:531)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:221)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:503)
    at com.vmware.vcloud.common.jdbcpool.PooledConnection.connectUsingDriver(PooledConnection.java:215)
    at com.vmware.vcloud.common.jdbcpool.PooledConnection.connect(PooledConnection.java:154)
    at com.vmware.vcloud.common.jdbcpool.ConnectionPool.createConnection(ConnectionPool.java:736)
    at com.vmware.vcloud.common.jdbcpool.ConnectionPool.borrowConnection(ConnectionPool.java:662)
    at com.vmware.vcloud.common.jdbcpool.ConnectionPool.init(ConnectionPool.java:514)
    at com.vmware.vcloud.common.jdbcpool.ConnectionPool.<init>(ConnectionPool.java:156)
    at com.vmware.vcloud.common.jdbcpool.DataSourceProxy.createPool(DataSourceProxy.java:95)
    at com.vmware.vcloud.common.jdbcpool.DataSourceProxy.getConnection(DataSourceProxy.java:106)
    at com.vmware.vcloud.common.datasource.OracleWrappedPoolDataSource.getConnection(OracleWrappedPoolDataSource.java:87)
    at org.springframework.orm.hibernate3.LocalDataSourceConnectionProvider.getConnection(LocalDataSourceConnectionProvider.java:81)
    at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:111)
    at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2101)
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1325)

vcloud-container-info.log

VMware vCloud Director 1.5.0.464915, South Africa Standard Time, 10.1.1.181 (10.1.1.181)
2012-02-26 20:46:44,555 | INFO     | Start Level Event Dispatcher | ServiceInitializationTracker   | Application startup begins: 2/26/12 8:46 PM |
2012-02-26 20:46:46,694 | ERROR    | Start Level Event Dispatcher | JDBCExceptionReporter          | The Network Adapter could not establish the connection |
2012-02-26 20:46:46,882 | INFO     | Start Level Event Dispatcher | StartupUtils                   | Successfully bound network port: 80 on host address: 10.1.1.181 |
2012-02-26 20:46:46,882 | INFO     | Start Level Event Dispatcher | StartupUtils                   | Successfully bound network port: 443 on host address: 10.1.1.181 |
2012-02-26 20:46:47,078 | ERROR    | Start Level Event Dispatcher | JDBCExceptionReporter          | The Network Adapter could not establish the connection |
2012-02-26 20:46:47,079 | ERROR    | Start Level Event Dispatcher | JDBCExceptionReporter          | The Network Adapter could not establish the connection |
2012-02-26 20:46:47,101 | ERROR    | Start Level Event Dispatcher | ContextLoaderListener          | Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.vmware.vcloud.common.core, config=osgibundle:/META-INF/spring/*.xml)) |
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.osgi.service.exporter.support.OsgiServiceFactoryBean#0': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jettyServer': FactoryBean threw exception on object creation; nested exception is com.vmware.vcloud.common.configuration.ConfigurationException: Error getting configuration property vcloud.http.minThreads
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1420)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:563)
    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:69)
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:355)
    at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
    at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)
    at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:48)
    at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageTwo(DependencyWaiterApplicationContextExecutor.java:299)
    at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplicationContextExecutor.java:244)
    at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.refresh(DependencyWaiterApplicationContextExecutor.java:169)
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:175)
    at org.springframework.osgi.extender.internal.activator.ContextLoaderListener$2.run(ContextLoaderListener.java:716)
    at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:48)
    at org.springframework.osgi.extender.internal.activator.ContextLoaderListener.maybeCreateApplicationContextFor(ContextLoaderListener.java:781)
    at org.springframework.osgi.extender.internal.activator.ContextLoaderListener.start(ContextLoaderListener.java:410)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374)
    at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1067)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:561)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:546)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:459)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:440)
    at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
    at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)

I checked the nic on the vCD appliance and it's connected and has the correct IP and like I said the admin console works (port .

Anyone have any Ideas?

0 Kudos
5 Replies
UofS
Enthusiast
Enthusiast

Did you solve this issue? - I am experiencing this also and have restarted everything and still no joy.

dion

0 Kudos
CSIEnvironments
Enthusiast
Enthusiast

Nope. Tried to find answers and later found out that the Appliance is not suitable or supported by VMware in production or dev/test environments. Apparently it's only meant for labs, this is probably why.

I ended up doing the manual install:

- Installed RHEL v5 Update 7 on a VM

- On another VM I Installed Windows 2008 R2 Ent and installed Micrsoft SQL 2008 R2.

Reason I chose MSSQL because it's easier for me to troubleshoot and debug if shit like this happens in the furture.

Good luck!

0 Kudos
MuraliGD
Contributor
Contributor

We just faced same issue and resolved it.

1) Added eth0 ip in /etc/hosts with a host-name ( earlier only localhost entries were present )

and configured the new hostname using "hostname" command

2) Restarted Oracle and VCD Process .. And it worked.

/etc/init.d/oracle-xe start

service vmware-vcd restart

Verified that on 1521 port Oracle is listening now and on

443 java process is listening ( for https to work )

Murali G D

0 Kudos
MuraliGD
Contributor
Contributor

In addition to above steps (1) and (2) do following also in case if it doesn't work

3) add hostname entry added in step 1 to /etc/HOSTNAME, to make it persistent across reboots.

4) vi /u01/app/oracle/product/11.2.0/xe/network/admin/listener.ora

Here delete  .<localdom> after xe in line GLOBAL_DBNAME=xe.<localdom>

finally line should look like

(GLOBAL_DBNAME=xe)))

Now either do

service vmware-vcd stop

/etc/init.d/oracle-xe stop

/etc/init.d/oracle-xe start

service vmware-vcd restart

-OR-

reboot vcd.

Regards,

Murali G D

0 Kudos
pompina
Contributor
Contributor

Hi Murali,

Thanks for the comments. We could proceed ahead with your solution. But we were still stuck with this issue =

vmware-vcd-cell is dead, but pidfile exists

We solved this issue by adding eth1 interface by running the interface configure cli on the vcd console.

And thanks to Preetam also Smiley Happy

Regards,

Pompina.

0 Kudos