How I revived VCSA 6.0

It all started not so sad, as it happened later. I needed to create one VM. Logging into vCenter created a VM, but when I tried to start it, an error occurred. Two other VMs (vCenter itself and one more) worked without problems. So I decided to overload vCenter, which I actually did. After 10 minutes, when trying to access from the VmWare client in the vCenter, I received an error that the connection could not be established. Oh how ..?! Decided to go through the Web - the same thing - error 503.



Sadness Given that I decided to do this at the end of the working day, fortunately vCenter is not very actively used. And so decided to understand what is happening.



Access Console - asking for username and password. I enter login and password - I get - Login incorrect.



We arrived ... (I tried all the passwords (and even the one that is 100% working) - the result is zero - I can't enter and that's it. Therefore, I decide to reset the password from root. For this, we need to add init = / bin / bash to the kernel boot line - I thought nothing complicated and overloaded vCenter again. I select a line - I press E - nothing happens. We read the text below and see what you need to click on P ... and finds that the password can be the last password from the root - I drive in and hooray - you can edit add init = / bin / bash, next is already a classic and I will not describe.

')

Immediately I check the place - and alas ... in / and / storage / log - there is no free space - I clear the place and reboot in the hope that everything will be OK.



I check the vCenter login in 15 minutes - the result is 0. I log in via ssh to the server and see what services are running and what not. To do this, use the command:

service-control –status –all 

I see the result:

vmware-invsvc (VMware Inventory Service) vmware-rbd-watchdog (VMware vSphere Auto Deploy Waiter) vmware-sps (VMware vSphere Profile-Driven Storage Service) vmware-vdcs (VMware Content Library Service) vmware-vpx-workflow (VMware vCenter Workflow Manager) vmware-vpxd (VMware vCenter Server) vmware-vsan-health (VMware VSAN Health Service) vmware-vsm (VMware vService Manager) vmware-vws (VMware System and Hardware Health Manager) vsphere-client ()

These are services that have not risen. We can say that almost nothing has risen. I'm trying to raise vmware-invsvc:

 service-control –start vmware-invsvc 

In response, I get that the service can not be started. I study logs:

 /var/log/vmware/vmdird/vmdird-syslog.log 

and:

 /storage/log/vmware/invsvc/ inv-svc.log 

At the moment of launching service-control –start vmware-invsvc in the logs I see the following:

2017-07-07T09: 50: 01.022945 + 06: 00 err vmdird t @ 140238302082816: VmDirSendLdapResult: Request (96), Error (49), Message (), (0) socket ([3] ip_server: 636 <-ip_server: 46241)

2017-07-07T09: 50: 01.022955 + 06: 00 err vmdird t @ 140238302082816: Bind Request Failed ([3] ip_server: 636 <-ip_server: 46241) error 49: Protocol version: 3, Bind DN: "cn = accountname , ou = Domain Controllers, dc = vsphere, dc = local ", Method: 128

That says that the problem in the password, a little googling found a solution:

in the vCenter shell, run the commands:

 /usr/lib/vmware-vmdir/bin/vdcadmintool 

After launch, the menu will be on the screen:

==================

Please select:

0. exit

1. Test LDAP connectivity

2. Force start replication cycle

3. Reset account password

4. Set log level and mask

5. Set vmdir state

==================

Choose 3 and specify accountname@vsphere.local , accountname@vsphere.local value - take from /var/log/vmware/vmdird/vmdird-syslog.log , namely from the lines:

2017-07-07T09: 50: 01.022955 + 06: 00 err vmdird t @ 140238302082816: Bind Request Failed ([3] ip_server: 636 <-ip_server: 46241) error 49: Protocol version: 3, Bind DN: "cn = accountname , ou = Domain Controllers, dc = vsphere, dc = local ", Method: 128

The utility will generate a new password for you - write it down.



Now you need to register the received password in the system - for this we run another utility:

 /opt/likewise/bin/lwregshell 

and after: \> we write:

cd HKEY_THIS_MACHINE \ services \ vmdir \ - press Enter

set_value dcAccountPassword "generated password"

quit

Then we overload vCenter.



After 10 minutes of waiting - vCenter started and is stable.