Problems after updating VCSA 8.0 -> 8.0U1

[Raudi]

Hi,

on thursday evening i updated my VCSA to 8.0U1, i had no problems... Yesterday, 3 days later, i had some maintenance and had to shutdown my complete environment. After startup of the VCSA i was able to login, but there was an error message that i don't remember, i was able to finish the startup of the VM's.

Perhaps 6 hours later i got a notice that the connection from a PCoIP Zero Cleint don't work. 1,5 hours before it was possible.

So i tryed to login to the VCSA, and after login i wasn't able to see something i have no rights to view was the message. And there was an error that he can't access the /sdk page.

When i try to access the /sdk page i get "no healthy upstream" the same when i go to the root of the page.

On SSH i was can see that the services vmware-content-library, vmware-vpxd and a few more are not running. So i was able to start some but some not. They can't be started, because there was no access to the /sdk page.

I made a complete reboot, but the VCSA don't came back. And i didn't found something that was wrong.

All certificates are valid up to next year, i have a fixed IP and DNS is working.

Then i have now deleted that VCSA and restored it from a storage snapshot of thursday morning, some hours before the U1 update.

Now the VCSA is running normal and i will try the update again.

Has someone seen something like that?

Regards
Stefan

[Ajay1988]

Unless logs are looked into ; don't think can comment anything .  vpxd service down is not good. Something could be not right which is why it would have failed. 

Maybe next time you hit the issue ; engage VMware Support or share more details on the issue like which all services r down .

Do a "service-control --start --all" always and never start individual services manually . Then look at the failed service logs . 

[Raudi]

Very strange, i made again the U1 update after my restore and have done a 2 restarts of the vcenter after that within the last days, but i can't reproduce this issue.

The problem last time, i had la few people here, they want to start their view session, so i need  a running vCenter.

And the main reason for this post was, to chek if someone else had a similar experience.

But this problems seems to have no one else and after the second update i havn't this issue again. 

Because this it must bave been a one time issue.