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.
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.
I noticed that one was readonly, but not that all were. OK, I tried both
removing "read-only" and unzipping the new set and did restarts around
everything. Now I DO see files in that directory change. And the
symptom changed as well: now it says "An error occurred, please try again
in another vSphere session.". But it either says this or the original
error from anywhere.
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?
To confirm: You are seeing this new error message even if you open
another UI client?
It's intermittent. Either from a UI client or the direct reference to
the URL from a browser, I either get that new error message or the old
one: I don't see a pattern to which I get.
Can you upload a fresh set of VC diagnostic bundle logs to the SR?
I'm making one, but the support site seems down.
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.
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.
I didn't realize that because I was getting the same result in both.
So I guess I should get very methodical. Here's what I did:
(1) Stopped vCenter and Tomcat.
(2) Replaced the data directory with the one here.
(3) Started vCenter and Tomcat.
(4) Started the UI and selected status.
I got "An error occurred, please try again in another vSphere session."
I zipped up the data directory and will add that and the logs into
the SR once the support portal is back up.
The portal came back up, so I uploaded both files to the SR.
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?
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?
It DID. I started a few clients. But I just did it from a client I started
a couple of hours ago and now it works! And the "Hardware Status" for
hosts work too, confirming they were the same problem.
Maybe I just needed to wait some number of hours after doing that.
So it seems that this workaround does work. I hope you can find what went
wrong from the logs and zip files I sent.
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
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.
I could have sworn I did, a few times, but I guess not. Thanks very
much for your help here. I think the two SRs should be closed to
avoid having the support organization waste more time on this.
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.
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.
If you read the thread carefully, you'll see that one of the versions
of those file was incorrectly set readonly. So either change to read/write
or use the correct version of those files.
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.
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.