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

0 Kudos
1 Solution

Accepted Solutions
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/

View solution in original post

0 Kudos
31 Replies
birend1988
Hot Shot
Hot Shot
Jump to solution

Please refer the below DOC. You need to follow the patch sequence as per the mentioned in DOC.

Patch a vCenter High Availability Environment

VCIX, NCAP
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

HI,

HA cannot be put into maintenance mode...it can be enabled or disabled. Only Esxi hosts enter maintenance mode.

The message returns to you because you have to deactivate HA.

Best regards,

Alessandro Romeo

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

Guys

I tried both method

1. first I am unable to ssh into the witness but I logged onto the console

ran software-packages -install --url

it failed

software-packages -install --iso

that failed also no cd roms to not have a valid patch iso

I took the Ha out of maint mode and disabled the vcenter HA   still get same message Ha needs to be in maint mode

My options and status

pastedImage_0.png

Any ideas?

0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

0 Kudos
insearchof
Expert
Expert
Jump to solution

Hello

Thank you for the link  only problem it is in Spanish and I need English version.

From what I can see from the images I need to mount the iso on the cd

but I do not know where that is kept on the system.

All my VM's including the VSCA primary peer and witness run on a NFS shared storage device,

Any ideas?

0 Kudos
insearchof
Expert
Expert
Jump to solution

I was able to download the patch from my vmware site.

Created a patches folder and mount fhe ISO on the CD Rom of the witness VCSA

pastedImage_0.png

From the console I ran this

pastedImage_1.png

The iso in patches

pastedImage_2.png

Any ideas

Thank you

0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

Do you have a VCSA on Windows or VCSA appliance? Because from the name of the ISO file you have downloaded the update for VCSA on Windows.

https://my.vmware.com/group/vmware/patch#search

pastedImage_0.png

If you have a VCSA Appliance you must download:

Alessandro Romeo

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

I downloaded the wrong file

I was successful updating the witness

got this error on the peer

pastedImage_0.png

Any ideas?

0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

Well!

This error seems to be a problem of steps. Make sure you have done exactly the steps in the attached document:

Make sure that the commands you run are exactly the ones in the document.

Alessandro Romeo

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

I had to initialize failover per instructions.

Then I was able to update the peer VCHA

Now all three Passive Peer and Witness are at the same patch level.

Problem now is I can not access  my vcenter at all

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x00007f1d14027430] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

I can access each ESXI host all VMs are running including the VCHA VMs.

Any ideas?

Thanks

0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

This error probably comes because the space occupied is 100%.

Follow the instructions in these links:

Lorenzo Moglie - Notes: VCSA: 503 Service Unavailable Error Fixed

Alessandro Romeo

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

I ran DF -h on all three machines

pastedImage_0.png

Last thing I did was start failover and then updated the peer server.

Also the HA is in maint mode still

Should I restart them all?   if so which order?     passive peer witness???

0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

Reboot All vCenter HA Nodes

If you have to shut down and reboot all nodes in the cluster, you must follow a specific shutdown order to prevent the Passive node from assuming the role of Active node.

Procedure

  1. Shut down the nodes in this order.
    • Passive node
    • Active node
    • Witness node
  2. Restart each node. You can restart nodes in any order.
  3. Verify that all nodes join the cluster successfully, and that the previous Active node resumes that role.

Alesandro Romeo

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

If vCenter does not come back up how can I verify that.

I just shutdown all the HA Nodes

Started the passive node first

Peer node was the active node prior to the failure.

Is there powershell commands to check this?

I hope the vcenter comes backup after restarting these

0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

To view the current status of the vCenter Server Appliance services, type the command:

service-control --status

https://www.vladan.fr/vmware-vcsa-check-running-services/

VMware Knowledge Base

Alessandro Romeo

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

After restarting all the nodes.

Still get the same error unable to open vcenter at all

This is very frustrating  at a dead in the water place now

Any ideas?

0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Restart vpxd

service-control --stop --all

service-control --start --all

try to connect to the vcenter with FQDN and then with the IP, tell me if the result does not change.

you can send me the log file

/var/log/vmware/vpxd/vpxd.log

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

Passive

pastedImage_0.png

Peer

pastedImage_1.png

Witness

pastedImage_2.png

Going to stop and start all services next will post results

0 Kudos
insearchof
Expert
Expert
Jump to solution

stopped all services then started all services       NO CHANGE

I always use FQDN

I used ip address and got same results

The vpxd.log is too large to attach to the message can I email it to you?

vcenter is still down.

0 Kudos