kenner
Contributor
Contributor

vCenter Service Status error

What does "Cannot access the health service!" mean? Where, precisely does that service run and how can it be restarted?

44 Replies
rriva
Expert
Expert

Maybe I haven't understood the question but :

Vcenter is a standard Windows Server, so you can reach it (for start/stop/restart and check privilege) by running "services.msc" on "Start-->Run"

If you look at your "Event Viewer" you should find more details about your error, and maybe it will be more simple to help you.

Riccardo Riva

VCP,RHCE,FCNSA

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Thank You!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
0 Kudos
kenner
Contributor
Contributor

Maybe I haven't understood the question but :

Vcenter is a standard Windows Server, so you can reach it (for

start/stop/restart and check privilege) by running "services.msc" on

"Start-->Run"

You did misunderstand. I'm asking about the "vCenter Service Status"

(i.e., "vCenter Server Health"), not vCenter itself.

0 Kudos
arindamiitk
Contributor
Contributor

This normally means a permissions issue. The vCenter Service Status pane can only be accessed if the user has the "Global.Health" privlege. Did the client login as Administrator

Also does this happen on every UI client? Sometimes this can happen if a UI client is connected to vCenter before the vCenter Management Webservices is completely started. In such case closing the client and reconnecting it will fix the issue.

0 Kudos
kenner
Contributor
Contributor

This normally means a permissions issue. The vCenter Service Status

pane can only be accessed if the user has the "Global.Health"

privlege. Did the client login as Administrator

Yes.

Also does this happen on every UI client?

Yes.

I also see it if I go directly to:

https://:8443/health-ui/index.html

0 Kudos
arindamiitk
Contributor
Contributor

Hmm... this appears to be more complicated that I thought. We will need to look at the logs to figure out more about the situation. Can you file a SR with the vCenter logs and let me know the SR number? Alternately you can upload the logs (diagnostic bundle) somewhere and I can take a look.

cheers,

Arindam

0 Kudos
kenner
Contributor
Contributor

Hmm... this appears to be more complicated that I thought. We will need

to look at the logs to figure out more about the situation. Can you file

a SR with the vCenter logs and let me know the SR number?

Thanks. I'd already opened the SR shortly after posting this. The number

is 1342032451. I just added the logs to it.

0 Kudos
Crabillon
Contributor
Contributor

Hello

I have the same problem, what is the solution ?

Thank you.

0 Kudos
kenner
Contributor
Contributor

Have you gotten a chance to look at this yet? I keep getting calls (about one per day) from the engineer who the SR was assigned to each time asking me to check something else that I'd already checked before filing the SR ...

0 Kudos
Crabillon
Contributor
Contributor

I have no solutions, i have not found nothing.

I have another bug in vCenter :

The tab Storage View, the search doesn't work....

Can you tell me more when you have more news of support ?

Thank You

0 Kudos
admin
Immortal
Immortal

Hi,

Please try this work around.

1. Stop VC.

2. Delete the "C:\Program Files\VMware\Infrastructure\tomcat\webapps\vws\data" directory (after sending the contents to us for debugging).

3. Unzip the contents of the attached "data.zip" file directly into "C:\Program Files\VMware\Infrastructure\tomcat\webapps\vws". This should create a "data" directory with the following files in it:

xhiveDatabase.bootstrap

log\xhive_0000000000.log

log\xhive_0000000001.log

log\xhive_checkpoint.log

log\xhive_id.log

4. Restart VC.

0 Kudos
arindamiitk
Contributor
Contributor

Hi,

Sorry about the late reply. We looked at the log files

that you uploaded to the SR and it looks like the third-party Xhive component that

we use is not starting up correctly. This will cause client connections to the health and query services to fail. We need some additional files from your setup to further diagnose this. There is also a workaround for the situation. Can you follow the steps in Ranga's message above and let me know if it worked? Please remember to first zip up the "C:\Program Files\VMware\Infrastructure\tomcat\webapps\vws\data" directory in your current setup and send it to us (via the SR), so that we can follow up with the Xhive folks.

Thanks,

Arindam

0 Kudos
kenner
Contributor
Contributor

I uploaded the old contents to the SR, but was quite surprised that the new "data" didn't fix anything. I restarted VC once and Tomcat at least three times. Oddly enough, I didn't see any file in the "data" directory or data\log change its modification date to today.

0 Kudos
arindamiitk
Contributor
Contributor

Hmm... Please hang on. Let me ask the Xhive experts to look at this.

0 Kudos
kenner
Contributor
Contributor

Hmm... Please hang on. Let me ask the Xhive experts to look at this.

OK, thanks. BTW, I'm beginning to think that SR 1354966361, although

a slightly different functionality, is actually the same issue. If

so, can you close that one? There's no point in having both open (and

owned by two different folks).

0 Kudos
arindamiitk
Contributor
Contributor

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.

0 Kudos
kenner
Contributor
Contributor

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.

0 Kudos
arindamiitk
Contributor
Contributor

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?

0 Kudos
kenner
Contributor
Contributor

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.

0 Kudos
arindamiitk
Contributor
Contributor

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.

0 Kudos