Friday, August 28, 2009

Vsphere server issues and upgrade progress

So I found out that using the host update tool versus Vcenter update manager is much easier and more reliable when moving from ESXi 3.5 to 4.0. Before I was using the update manager and it wasn't working all that reliably. So far I haven't had any issues using the host update tool. I've done many upgrades now, and I only have 4 left, 3 of which I am doing this weekend.

Whenever I speak to vmware they always think I'm using ESX, when I prefer and expect that people should move to the more appliance model of ESXi. With 4.0 they are pretty much on par, and I'm going to stick with ESXi.

On one of my vsphere 4.0 servers (virtualcenter) its doing this annoying thing when I try to use the performance overview:


Perf Charts service experienced and internal error.



Report application initialization is not completed successfully. Retry in 60 seconds.


In my stats.log I see this.


[28 Aug 09, 22:28:07] [ERROR] com.vmware.vim.stats.webui.startup.StatsApplicationLauncher : Task execution produced an error. Re-initialization attempt #26 will startup after 60 seconds...

java.util.concurrent.ExecutionException: java.lang.IllegalStateException: com.vmware.vim.stats.webui.StatsReportException: Unable to open VC DataSource.

    at java.util.concurrent.FutureTask$Sync.innerGet(

    at java.util.concurrent.FutureTask.get(

    at com.vmware.vim.stats.webui.startup.StatsApplicationLauncher$ Source)


Caused by: java.lang.IllegalStateException: com.vmware.vim.stats.webui.StatsReportException: Unable to open VC DataSource.

    at com.vmware.vim.stats.webui.startup.StatsApplicationLauncher$1$ Source)

    at java.util.concurrent.Executors$

    at java.util.concurrent.FutureTask$Sync.innerRun(


    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(

    at java.util.concurrent.ScheduledThreadPoolExecutor$

    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(

    at java.util.concurrent.ThreadPoolExecutor$

    ... 1 more

Caused by: com.vmware.vim.stats.webui.StatsReportException: Unable to open VC DataSource.

    at com.vmware.vim.stats.webui.startup.VcDataSourceInitializer.init(Unknown Source)

    at com.vmware.vim.stats.webui.startup.StatsReportInitializer.createInitializers(Unknown Source)

    at com.vmware.vim.stats.webui.startup.StatsReportInitializer.init(Unknown Source)

    ... 9 more

Caused by: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (The connection to the named instance has failed. Error: Receive timed out.)

    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(

    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(

    at com.vmware.vim.stats.webui.startup.VcDataSourceInitializer.openVcDataSource(Unknown Source)

    ... 12 more

Caused by: The connection to the named instance has failed. Error: Receive timed out.

    at Source)

    at Source)

    at Source)

    at Source)

    at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(

    at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(

    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(

    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(

    ... 14 more


I have an open case with vmware right now. See if I can get it fixed.


akoj said...

Hi, what is your SQL setup? Is it local or on separate server? Does it use JDBC? Apparently this is what you need to have set up on the sql box to have proper stats genarated.

jkowall said...

Was on the same server, as the default vsphere server install. We have moved it since then to another server as well.

vsphere server only runs using ODBC, they use a bridge to JDBC internally, but it uses a ODBC datasource.

Luis F. said...


Did you get any solution from VMWare?

jkowall said...
This comment has been removed by the author.
Luis F. said...

I have that issue in a new instalation with a external Oracle 11g over linux and a clean database. Tomorrow I am going to open a support ticket.

jkowall said...

Actually i was confusing two different issues. This one wasn't related to the last thing I typed.

This one was fixed by editing a tomcat configuration file, which was using a hostname, and needed an ip address. This is supposed to be fixed in 4.0 rollup 1. Did you install that release or are you using 4.0?

I haven't upgraded to rollup 1 yet, not sure if/when I will.

Luis F. said...

We are developing a new environment with vsphere and we upgraded from 4.0 to 4.1 yesterday to try it and make all tests with a dummy but it fails... by the moment. I ll keep you up to day.