JDMils_Interact
Enthusiast
Enthusiast

vCenter server is dead- Emergency Mode

I'm not sure what's happened, but I may have had power issues and I think my vCenter VCSA server has corrupted drive(s). This website shows exactly what happened to me and after implementing the suggestions, the vCenter server now boots to the logon prompt. When I log in using the root credentials, I get this:

[ERROR] Failed to connect to service.

Use service-control command to manage applmgmt service.

...

...

...

I have tried the suggestions on this website https://tsmith.co/2016/vcsa-wont-boot-fsck-failed/  and it still does not boot. Here is a screenshot of my VCSA:

2018-10-27_2-48-08.png

2018-10-27_3-03-08.png

2018-10-27_3-04-20.png

What can I do to fix this?

0 Kudos
2 Replies
Vijay2027
Expert
Expert

Can you check or attach vpxd.log file to this thread.

Location: /var/log/vmware/vpxd

0 Kudos
Dave_the_Wave
Hot Shot
Hot Shot

It is my understanding that vCenter doesn't really store much or anything (other than pool licenses together). It's like a giant "client" for ESXi hosts.

Wouldn't it be faster to just re-create a new vCenter?

Hosts can be removed from the Datacenter back with their own licenses.

Once a new vCenter is up, add the hosts back into Inventory.

Might have to recreate some backup jobs from VM Explorer/Veeam/Vertias, but at least all that can be done in an hour or so.

0 Kudos