Fixing vCenter 5.5 server’s database usage monitoring issue in service health status

12 Feb

Sometimes an upgrade with swanky new features may be the opposite of what you want. A good example is the inclusion of database usage monitoring within vCenter 5.5 server’s service status.

If your SQL database was or is provisioned as usual and you install vCenter 5.5 or upgrade to it, you will see the following amber warning when you check the vCenter service health status:

“Unable to monitor database storage usage. Refer to VMware KB 2078305 for details.”

But when you fire up that KB, it tells you nothing on how to resolve this warning but rather tells you how to manage your database. This feature, it seems was available since vCenter 5.0 but it never showed any warning if you did not configure your database. But with 5.5 (or maybe even 5.1, sorry we skipped that version), you are force to deal with this and cannot ignore it.

The link from tells you that you need to run the following on your SQL database:

grant VIEW SERVER STATE to [vpxuser] --> where vpxuser is the account used to access the vCenter database

However, after making this configuration, the warning never went away and I gave VMware support a call. And it turns out, an additional configuration is required to fix this. So the full configuration is:

 use master
 grant VIEW SERVER STATE to [vpxuser]

However, once database monitoring is enable, the status turns red with the following message:

“Database storage space is critically low and affects vCenter Server functionality. Refer to VMware KB 2078305 for details.”

If you manage a virtualized estate in a big enterprise like I do, you will know that it is highly unlikely that the databases are that full or else the DBAs will be pounding on my door daily!

The VMware support guy pointed me to this link ->

It turns out that with database monitoring turned on, vCenter will alert you on ALL drives space issue on your database server, regardless whether they are used by the database or not. Typically, we have the SQL database running off a Microsoft cluster with a quorum of size 1 GB.

The default threshold alerts is found in vCenter’s advanced settings: value=5000 value=1000

So I must have at least 5 GB of free space in ALL drives to keep it green. This is obviously impossible in a clustered environment using disk quorum. Further, we have a system volume where the application is installed and which doesn’t grow over time and has about 500 MB free space most of the time.

Here is the vpxd-xxx.log capture identify the drives which are below the default threshold

2015-02-05T20:48:30.686-05:00 [09596 info 'utilvpxdVdb'] [VpxdVdb::GetDBSpaceStatus] WarningThreshold(MB): 5000 AlertThreshold(MB): 1000. Updating Health Message Parameter to
 --> Drive: Q, Free Space:479 MB, Used Space: 0 MB
 --> Drive: H, Free Space:454 MB, Used Space: 2320 MB
 --> Drive: I, Free Space:461 MB, Used Space: 0 MB
 --> Drive: C, Free Space:37381 MB, Used Space: 0 MB
 --> Drive: D, Free Space:66157 MB, Used Space: 0 MB
 --> Total Used Space: 2320 MB, Minimum Free Space: 454 MB

My solution is to set the threshold low so that this status is always green. This is not a problem for us because we don’t need to monitor the disk space on the SQL servers, the DBA team does it and will ping us if disk space is low. However, if you are a do-it-all administrator, ensure that you have other disks monitoring tools when doing this. value=200 value=100

This is a case of new features adding more noise of some of us. I hope VMware will update this feature to allow us to selective turn on and off monitoring of each disk and change the threshold for each disk.


Posted by on February 12, 2015 in vmware


Tags: ,

4 responses to “Fixing vCenter 5.5 server’s database usage monitoring issue in service health status

  1. bsobczyk (@bsobczyk)

    February 18, 2015 at 8:18 pm

    thanks a lot, I just resolved my problem

  2. Mark

    February 24, 2015 at 2:45 pm

    Thank you, I just resolved my problem too

  3. Dave

    May 23, 2015 at 4:18 am

    Finally fixed! Thanks!

  4. Sam

    September 20, 2015 at 12:08 am

    Thank you. I thought I was losing it when the DB size was a few MB on a 20GB disk. The issue causing our warning was only 2.5GB free on page file disk.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: