VCSA (6.0.0.30200) broken - HELP

[briggsb]

I have logged this as a ticket, but I am in real trouble right now as all backups are failing, so clutching at straws and hoping someone is watching over a weekend.

I think this must have happened on Friday at some point after I left the office, but I only noticed the problem on Saturday as I was checking the progress of a VM that I was working on. The VM in question should have nothing to do with this problem.

The issue I has was that I couldn't access the VM as Vcenter web client was giving me an error (500 error of some sort, but was a proper error page, not just text as it is now). Not sure why, it's never happened before, but a reboot of VCSA seemed like the first port of call.

The reboot took for ever, well over 15 miunutes, and when it finally came up, the error you get now is...

503 Service Unavailable (Failed to connect to endpoint:
[N7Vmacore4Http16LocalServiceSpecE:0x7fdaf26c3c10] _serverNamespace =
/vsphere-client _isRedirect = false _port = 9090)

I can access the console of the VCSA, but if I try and enable SSH and try to login to the VCSA on SSH, it disables SSH as soon as I try the password. This happens over and over so I cannot access the VCSA via SSH to even investigate.

I have since removed the VCSA from inventory on VM2, and imported it on VM3 (shared storage so nothing moved). This is because of a post I saw mentioning USB devices which will be the case on the original VM.

Runing VCSA on VM3 is no different, still a very long wait to load, and same error on webpage. Again, SSH gets disabled as soon as I try to actuall SSH in for some reason.

TIA, Alan

[Beingnsxpaddy]

Dear briggsb​, I am sure you must have tried some steps already, can you confirm if you are able to access the VCSA "https://appliance-IP-address-or-FQDN:5480"

If yes, can you confirm all the services are up?

Regards

Pradhuman

VCIX-NV, VCAP-NV, vExpert, VCP2X-DCVNV

If my Answer resolved your query don't forget to mark it as "Correct Answer".

[a_p_]

Issues like this may be caused by low (or no) free disk space on one of the partitions/file systems (often /storage/db) within the vCSA.

Since you cannot login, it may be worth a try running e.g. RVTools (https://www.robware.net/rvtools/) against the ESXi host on which the vCSA is currently registered, to see whether it is able to retrieve this information from the vCSA.

André

[briggsb]

I get 'session has expired. please login again.' on port 5480...

[briggsb]

Thanks for all the replies. Disk space indeed was the issue, but to such an extent you couldn't get in to a shell either. The support was excellent once I'd escalated the severity, and they spent a couple of hours hacking away at the VCSA to get a command prompt, and set about freeing up some space. It was a recurring password expiration warning that filled the logs apparently? So they had me reset the password and I'm good now for another year

[Vijay2027]

Also you can set the password to never expire:

Command: chage -M -1 root