Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 244595

Re: Storage providers error

$
0
0

Thanks for replying.  Yes have tried restart, but still problem as soon as click Storage Providers get that error.  No providers are defined yet.

 

Add, remove etc are all greyed and and not selectable.

 

I have errors in the vws.log which I think are all related to this problem:

[2013-02-08 14:59:36,218 Thread-38  ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health document because of null http client for component D6D0DA81-DCB3-42E8-9173-CA9A39DB7C34.visvc
[2013-02-08 14:59:36,218 Thread-38  ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health for XXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.visvc from https://SERVERNAME:18443/vws/Query/Health
[2013-02-08 14:59:36,218 Thread-38  ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health for XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.visvc from any of its health URLs
[2013-02-08 15:00:10,270 Thread-38  ERROR com.vmware.vim.health.impl.ComponentSpec] Error while trying to login to https://SERVERNAME:18443/vws/Login

 

Everything is on the VC, I've tried this url directly without any response.

 

All services start and are running ok.  BUT there is an alert in vcenter status:

vCenter Management WebServices - Unable to retrieve health data from https://SERVERNAME:18443/vws/Query/Health

 

VirtualCenter.VimWebServicesUrl is set to https://SERVERNAME:18443/vws in advanced settings.  I don't know but this isn't the default port, I think it was changed back in the v4.x days.

 

I can't find anything that solves this.

Running v5.1, upgraded from v4.1 with custom certs.

 

Thanks if can help any!


Viewing all articles
Browse latest Browse all 244595

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>