Hi justingarcia,
Please share following information:
1. Are you able to login to vCenter with SSO admin credentials ?
2. Is the issue noticed with all AD users or just a particular AD account ?
3. If the issue is with one user, what is the role assigned to under vCenter permissions ?
Thank you for your reply,
Yes, User able to login using administrator@vsphere.local account, and his Admin role user, but the entire AD users can't access the vCenter Server,
As of now the vCenter Server is now working after we restarted the appliance. It's kinda weird, Maybe there's a vCenter service that failed to start, but again we do not know what causes the issue.
Hi all,
relocated server, for some reason swap file was on another attached location. Now no vms will start can’t access swap file.
esxi 6.0. Is there a quick easy way to get the vms up and running without trying to gain access to the original swap file location?
thank you!!!
I’ve tried to goto advanced and remove / change the swap file line and unregister - register the VM but didn’t work....tried manually creating the the path to the data store under advanced and didn’t work.
It depends on how the swap file location has been configured.
In case it's a cluster configuration (ESXi managed by vCenter Server) you should be able to reconfigure it in the cluster settings. In case the relocation has been configured on a per VM basis, you will have to remove the related settings from each of the VM's configuration (.vmx) files.
André
Glad to hear that AD authentication is now working post vCenter reboot. For next time, if you want to check the services and restart them instead of rebooting:
service-control --status
service-control --stop --all
service-control --start --all
Moderator: Please do not start multiple threads on the same topic.
As this thread has a reply, I have deleted the first instance you created earlier today.
It’s not a cluster sorry.
1 x DC
1 x RDS
very basic setup. as simple as you can
In this case, please download the VM's configuration (.vmx) files, and attach them to a reply post.
Please verify that the files do not contain non-public content, e.g. private annotations etc.
André
what worked for me:
SSH into the server. check the status of the services:
[ ~ ]# service-control --status
Running:
lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-certificatemanagement vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rhttpproxy vmware-sca vmware-sps vmware-sts-idmd vmware-stsd vmware-topologysvc vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui
Stopped:
applmgmt vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-statsmonitor vmware-vcha vsan-dps
start the applmgmt service
[ ~ ]# service-control --start applmgmt
Operation not cancellable. Please wait for it to finish...
Performing start operation on service applmgmt...
Successfully started service applmgmt
all fixed.
I’ll do that tomorrow morning thanks. Nothing private will only have one datastore DS1.
This is a Linux server right? What can you see on the OpenLDAP server on the /var/log/auth.log and /var/log/secure ?
Hi bukowski12,
I don't think you're doing anything wrong. I think the initial replies to my post were incorrect and SCP is in fact not supported in vSphere 7 as the more recent posts show.
Thanks,
David
Thanks to scott28tt for the clarification
David
With new updates to apply to vCenter 7.0U1 showing in my console (7.0.1.00000 to 7.0.1.00100), I thought I'd update my lab. Unfortunately, I'm now stuck in a loop of failing update checks [see attached screenshots: 1) prechecks succeed, 2) SSO Admin password requested, 3) exception in precheck], and can't escape.
Even after restarting the VCSA, it stays stuck on the exception page; I can't figure out how to end this insanity!
The log I found (attached) seems to indicate that, although the prechecks pass correctly, the update engine can't find some files that should have been staged.
Help! I don't have any support options on this (it's a lab after all), and if I can avoid having to rebuild from backup (yes, I have both the pre-upgrade backup as well as the automated backups that have been running every day since deployment), it would be appreciated.
Hi Andre,
just to confirm though should be able to repoint to a new location and start the servers up correct without the need for the existing swap file?
Managed to track external drive where swap file as on and managed to get servers back online
I saw the same thing with my upg from 7.0.0xxx to 7.0.1.
Except mine I removed the upgrade.cfg to get back into the backend.
But no front end. and seems all of my vm are lagging.
Still trying to figure how to roll back.
Any suggestions ?
In my case, I've discovered that the loop can be overridden by manually updating the URL in the browser from "https://<vcsa>:5480/#/ui/update/progress" to "https://<vcsa>:5480/#/ui/".
Unfortunately, even though the Update option is now available & finds the waiting patch via URL, when I click "Stage Only", it has a weird error: "Update installation failed, vCenter Server is non-operational." So it's pretty clear that something is still stuck. Also, I don't see any "upgrade.cfg" to remove, so I may be broken in a different place.
And now I've figured out that applying the update via ISO (ref: https://www.virtualizationhowto.com/2019/07/manually-patch-vmware-vcenter-server-vcsa-with-iso/ ) works to get the update installed, but nothing to fix the fact that the update engine within vCenter still thinks it needs to do the update. <sigh>