Skip navigation
VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
12,285 Views 41 Replies Last post: Mar 27, 2012 7:43 AM by szymonunion RSS
arindamiitk Novice 22 posts since
Apr 15, 2005
Currently Being Moderated
15. Jun 12, 2009 11:56 AM in response to: kenner
Re: vCenter Service Status error

Can you try using the data.zip uploaded with this message? The problem with the previous data.zip was that the files in it were set to "read-only". As a result tomcat could not load them. Can you try with the new zip? Alternately just go to the data folder and remove "read-only" from all files in it.

Attachments:
arindamiitk Novice 22 posts since
Apr 15, 2005
Currently Being Moderated
17. Jun 12, 2009 3:18 PM in response to: kenner
Re: vCenter Service Status error

To confirm: You are seeing this new error message even if you open another UI client? Can you upload a fresh set of VC diagnostic bundle logs to the SR?

arindamiitk Novice 22 posts since
Apr 15, 2005
Currently Being Moderated
19. Jun 12, 2009 5:17 PM in response to: kenner
Re: vCenter Service Status error

Using the URL directly in the browser is actually not meant to work. This is because clients need to authenticate before accessing the data. So simply using the browser will not work. The VI Client does this authentication.

arindamiitk Novice 22 posts since
Apr 15, 2005
Currently Being Moderated
22. Jun 15, 2009 3:52 PM in response to: kenner
Re: vCenter Service Status error

What happens if after Step 4 above, you start a new UI client and select the VC service status? Does it still show the same error?

arindamiitk Novice 22 posts since
Apr 15, 2005
Currently Being Moderated
24. Jun 15, 2009 4:35 PM in response to: kenner
Re: vCenter Service Status error

Cool. Yes, the later problem that you encountered ("An error occurred, please try again in another vSphere session", not the earlier unable to login/Xhive problem) is a known issue which we will fix in an update. The workaround for now is to simply start a new UI client.

 

We are looking at the original problem you had due to Xhive not loading up and this may be due to a bug in the Xhive version that we shipped with. We are still working on that.

 

 

 

cheers, Arindam

Atmos4 Enthusiast 60 posts since
Dec 19, 2008
Currently Being Moderated
26. Jul 1, 2009 5:14 AM in response to: kenner
Re: vCenter Service Status error

I have the same problem, with both vCenter Service Status and vCenter Hardware Status plugins not working. vCenter Service Status also displays "Cannot access the health service!", Hardware Status displays: "Error occured while trying to update the host data".

 

I tried exchanging the data directory and restarting vCenter + Tomcat, but that didn't help. FIles in the data directory do not get updated.

 

I noticed the following error in catalina.log every time I try to show one of the plugins:

Jul 1, 2009 1:37:42 PM org.apache.tomcat.util.http.Parameters processParameters

WARNING: Parameters: Invalid chunk ignored.

 

Though some googling shows, that this warning is probably harmless.

Atmos4 Enthusiast 60 posts since
Dec 19, 2008
Currently Being Moderated
28. Jul 1, 2009 5:39 AM in response to: Atmos4
Re: vCenter Service Status error

I found this additional error in Windows Application log:

 

Re: vCenter Service Status error Initialization error. Could not initialize certficate I/O error: failed to decrypt safe contents entry: javax.crypto.BadPaddingException: Given final block not properly padded

 

I am using a a PKCS12 certificate created by Windows Certificate Signing Authority. I did specify keystorePass in server.xml of Tomcat to the correct password for the rui.pfx, which was required for VMware Management Server (Tomcat) to work. But it seems some other parrt of Tomcat still doesn't like the cert.

 

The keystorePass password specified in server.xml is correct, I could import the rui.pfx into windows keystore by using that password.

Atmos4 Enthusiast 60 posts since
Dec 19, 2008
Currently Being Moderated
29. Jul 1, 2009 6:28 AM in response to: Atmos4
Re: vCenter Service Status error

I tried switching the paths in server.xml, web.xml and config.xml to a backup of the certs that came with vCenter, but this didn't fix the error. I also reset the keystorePass to testpassword, from the key required for my custom cert.

Bookmarked By (0)

Share This Page

Communities