vCenter

 View Only
  • 1.  Unable to login as root on vCenter after update

    Posted Aug 17, 2018 04:11 PM

    Hi,

    I have updated my appliance today to version 6.7.0.14000 and then I'm unable to login as root on vCenter:

    The password is correct because I can login on the machine (after returning the error: "Failed to connect to service")



  • 2.  RE: Unable to login as root on vCenter after update

    Posted Aug 17, 2018 04:51 PM

    Check if the following VCSA 6.5 fails to start File System Check and Network Service - Nolabnoparty article helps.

    Please consider marking this answer "correct" or "helpful" if you think your question have been answered correctly.



  • 3.  RE: Unable to login as root on vCenter after update
    Best Answer

    Posted Aug 17, 2018 05:07 PM

    diegodco31​,

    Funny, I didn't need to do anything... After a reboot and waiting for a considering amount of time it returned to work.

    Thanks anyway!



  • 4.  RE: Unable to login as root on vCenter after update

    Posted Nov 18, 2019 11:19 PM

    Heads up!

    Same problem here. Upgrading VCSA 6.7.0.41000 from 6.7.0.40000. Everything went as normal except the progress bar got stuck at "Converting Data 80%". When i tried to refresh the page I got kicked out of VCSA appliance login and root did not work as mentioned. The "Unable to login" message is different than the "Access denied" messages most of the articles assume you are getting when you search for VCSA root can't login. Even though you can't login to VCSA you should be able to login to VCenter, open the VCSA console and reboot the appliance. All is well after and upon first login to VCSA appliance interface I got the "Installation Succeeded" message indicating the upgrade was successful.



  • 5.  RE: Unable to login as root on vCenter after update

    Posted Oct 11, 2021 02:53 AM

    I have a few vCenters @ 6.7.0.48000 and they seem to all do the same thing. I have to wait around 5 minutes before I can logon as root. And I get the exact same issue as the OP when logging in using the DCUI.

    Seems to be related to a particular service not having completed its startup, but I'm not sure which one yet, still looking.