VMware Cloud Community
insearchof
Expert
Expert
Jump to solution

Patching/Updating a VCHA not updating

VMware 6.5 U2

Trying to update my VCSA  6.5.0.12000 Build Number 7119157

When I click on install updates the bar displays then goes to 100% given this message

      vCenter HA should be in the maintenance mode to apply an update.

I went to my vCenter configuration  vcenter HA selected Edit and placed it into maintenance mode

tried install updates again and get the same message.

update is  6.5.0.30000 Build Number 14020092

any ideas?

Thank you

Tom

Reply
0 Kudos
31 Replies
Alex_Romeo
Leadership
Leadership
Jump to solution

yes, send my address: info@aleadmin.it

Blog: https://www.aleadmin.it/
Reply
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

some important services to start the vcenter are stopped.

  • Vmware-vpxd
  • Vmware-client
  • VMware-rhttpproxy

VMware Knowledge Base

the others see them later.

If these services do not start, error 503 is corrected

Alessandro Romeo

Blog: https://www.aleadmin.it/
Reply
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

These are the possible causes that lead to that kind of error:

"503 Service Unavailable" error on the vSphere Web Client when logging in or accessing the vCenter Server (67818)

https://kb.vmware.com/s/article/67818

Firstboot Failed during Install, Deployment, Upgrade, or Migration in vCenter Server and vCenter Server Appliance

https://kb.vmware.com/s/article/55746

How to Stop, Start or Restart vCenter Server 6.x Services

https://kb.vmware.com/s/article/2109881

Troubleshooting Work-Flow error 503 (attached)

Blog: https://www.aleadmin.it/
Reply
0 Kudos
insearchof
Expert
Expert
Jump to solution

Alessandro

I just sent the email

Reply
0 Kudos
insearchof
Expert
Expert
Jump to solution

Yes I have been trying to start those services and they fail to start.

On the PEER Node which was the last Active I remember

pastedImage_0.png

On the passive it just sits there trying to start and then times out

Reply
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

The problem with error 503 is precisely this service that does not start. I received the log now checking it.

Blog: https://www.aleadmin.it/
Reply
0 Kudos
insearchof
Expert
Expert
Jump to solution

Yes I agree the services not starting are the issue

Thank you

Hope you find something in the log

Tom

Reply
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

I would say that the problem is reading the certificate.

In the log file I found this error that causes the others and does not start the service

2019-08-28T23:33:36.405Z info vpxd[7F3675823800] [Originator@6876 sub=vpxCrypt] Failed to read X509 cert; err: 151441516

pastedImage_1.png

proceed as in the link:

VMware Knowledge Base

If it doesn't work, we need to recreate the certificate

Blog: https://www.aleadmin.it/
Reply
0 Kudos
insearchof
Expert
Expert
Jump to solution

following the instructions in the link you  provided

~ ]# vcenter-restore

Please enter SSO Admin username: administrator@vsphere.local

Please enter SSO Admin Password:

Restore of embedded node is only supported via this script in case of embedded linked mode setup.

Any ideas?

Should I do this on the Peer? this was done on the passive

Update

Tried on peer same results

Reply
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

I waited a while to answer because I checked everything again.

The log file has password and certificate errors. This can happen during updates.

The first may be the consequence of the second error.

We begin to reset the password with this procedure:

before proceeding with the password reset, go to this verification:

VMware Knowledge Base

  Cause

The /etc/hosts file was missing the IPV4 loopback address and localhost entries which caused the services to fail.

$ cat /etc/hosts
# Begin /etc/hosts (network card version)

# End /etc/hosts (network card version)
# VAMI_EDIT_BEGIN
# Generated by Studio VAMI service. Do not modify manually.
192.168.2.11 vc01.test.local vc01
# VAMI_EDIT_END
::1 localhost.localdom localhost

Resolution
Update the /etc/hosts file with the IPV4 loopback address 127.0.0.1 and localhost entries similar to the below.

$ cat etc/hosts
# Begin /etc/hosts (network card version)
127.0.0.1  vc01.test.local vc01 localhost

# End /etc/hosts (network card version)
# VAMI_EDIT_BEGIN
# Generated by Studio VAMI service. Do not modify manually.
192.168.2.11 vc01.test.local vc01
# VAMI_EDIT_END
::1 localhost.localdom localhost

-----------------------------------------------------------------------------------------------------------------------------------------------------

Reset password

VMware Knowledge Base

Resolution

To update the password used by the vCenter Server's Machine Account after a restore, use the vcenter-restore CLI to issue a reset request. For more information, see the Restore the Failed vCenter Server Virtual Machine With the Direct-to-Host Emergency Restore Operation section in the vSphere Installation and Setup Guide.

For vCenter Server Appliance


  Login to vCenter Server via SSH as the root user

  1. Run this command to switch to BASH

    shell
  2. Run this command to Stop all of the vCenter Server services:

    service-control --stop --all
  3. Run this command:

    vcenter-restore -u administrator -p <administrator@vsphere.local password>

    For example:

    vcenter-restore -u administrator -p VMware1!

    Note: This CLI can be executed without either option, and the user will be prompted to provide the administrator and administrator@vsphere.local password.
  4. Run this command to confirm that all services are now started:

    service-control --status --all

---------------------------

OR this procedure:

---------------------------

Related Information

To manually invoke an update of vCenter Server's Machine Account password, use the dir-cli computer password-reset CLI to issue a reset request.

For vCenter Server Appliance

  1. Login to the vCenter Server via SSH as the root user
  2. Run this command to switch to BASH

    shell
  3. Run this command:

    /usr/lib/vmware-vmafd/bin/dir-cli computer password-reset --login administrator --live-dc-hostname <Platform Services Controller FQDN> --password <administrator@vsphere.local password>

    For example:

    /usr/lib/vmware-vmafd/bin/dir-cli computer password-reset --login administrator --live-dc-hostname mgmt01psc01.sfo01.rainpole.local --password 'VMware1!'

    A successful password reset will output:

    Password for machine account reset.

    Note: If you are using a PSC HA configuration using a Load Balancer, execute this command against one of the backing PSC members and wait 30 seconds for the VMware Directory Service replication cycle to push this update to all nodes.
  4. Run these commands to Start the vCenter Server services:

    service-control --stop --all
    service-control --start --all

-------------------------------------------------

The DB has no duplication. Disk space is not 100%....we have excluded these possibilities.

Alessandro Romeo

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

Blog: https://www.aleadmin.it/
Reply
0 Kudos
johncol
VMware Employee
VMware Employee
Jump to solution

Do you have a support contract, I'd advise opening an SR for this, They will probably advise destroying vcha properly and getting back to one node for troubleshooting. Personally I would always destroy vcha before patching/upgrading etc. Then snapshot ( with no vcha its supported ) - Its so easy to reconfigure vcha after the update that way once all is verified as working ok. Do you have a file/VAMI  back up worst case scenario?

Reply
0 Kudos
insearchof
Expert
Expert
Jump to solution

To All,

Thank you for all your help.

I decided to rebuild my VCenter.

Installed new VCSA  applied updates and added all hosts from the HA configuration.

Next time I will make a snapshot of the VCSA

Again thank you for all the help

Reply
0 Kudos