How I revived VCSA 6.0
It all started not so sadly, as happened later. I needed to create one VM. Having entered vCenter, he created a VM, but when he tried to start, an error occurred. Two other VMs (vCenter itself and one more) worked without problems. Therefore, I decided to reboot vCenter, which I actually did. After 10 minutes, when trying to access from VmWare client to 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. Despite the fact that he decided to do this at the end of the working day, fortunately vCenter is not particularly actively used. And so he decided to understand what was happening.
Access Console - asks for a username and password. I enter the 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 log in and that's it. Therefore, I decide to reset the root password. To do this, we need to add init = / bin / bash to the kernel boot line - I thought nothing complicated and again reloaded vCenter. I select the line - I press E - nothing happens. We read the text below and see what we need to click on P ... I press, oops - asks for a password - standard vmware doesn’t seem like a dock from Google. and finds that the password can be the last password from root - I drive in and cheers - you can edit add init = / bin / bash, then I’m going to go over the classics and I won’t describe it
right there and then 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 login to vCenter after 15 minutes - the result is 0. I go through ssh to the server and see what services are running and what is not. To do this, use the command:
As a result, I see:
These are services that have not risen. We can say that almost nothing has risen. Trying to raise vmware-invsvc:
In response, I get that the service cannot be started. I study logs:
and:
At the time of launch
That says that the problem is in the password, a little google found a solution:
in the vCenter shell we run the commands:
After starting, the menu will appear on the screen:
We select 3 and indicate the
The utility will generate a new password for you - write it down.
Now the received password must be registered in the system - for this we launch another utility:
and after: \> write:
Then we overload vCenter.
After 10 minutes of waiting - vCenter has started and is working stably.
Sadness. Despite the fact that he decided to do this at the end of the working day, fortunately vCenter is not particularly actively used. And so he decided to understand what was happening.
Access Console - asks for a username and password. I enter the 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 log in and that's it. Therefore, I decide to reset the root password. To do this, we need to add init = / bin / bash to the kernel boot line - I thought nothing complicated and again reloaded vCenter. I select the line - I press E - nothing happens. We read the text below and see what we need to click on P ... I press, oops - asks for a password - standard vmware doesn’t seem like a dock from Google. and finds that the password can be the last password from root - I drive in and cheers - you can edit add init = / bin / bash, then I’m going to go over the classics and I won’t describe it
right there and then 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 login to vCenter after 15 minutes - the result is 0. I go through ssh to the server and see what services are running and what is not. To do this, use the command:
service-control –status –allAs a result, I see:
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. Trying to raise vmware-invsvc:
service-control –start vmware-invsvcIn response, I get that the service cannot be started. I study logs:
/var/log/vmware/vmdird/vmdird-syslog.logand:
/storage/log/vmware/invsvc/ inv-svc.logAt the time of launch
service-control –start vmware-invsvc, I see the following in the logs: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 is in the password, a little google found a solution:
in the vCenter shell we run the commands:
/usr/lib/vmware-vmdir/bin/vdcadmintoolAfter starting, the menu will appear 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
===================
We select 3 and indicate the
accountname@vsphere.localvalue of accountname - we 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 the received password must be registered in the system - for this we launch another utility:
/opt/likewise/bin/lwregshelland after: \> 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 has started and is working stably.