Hello.
I'm facing a strange problem on my vCenter. The message "Failed to request health status from URI..." is shown as Health Message while configuring a vCenter node. Also, I can't see status and other information about most of the vCenter services as can be seen in the following image:
When I try to change anything in Manage tab, I get the following error message:
I have already followed the instructions in KB 2089949, without success.
Has anyone faced with this issue?
Thanks!
André
I am trying to run a KVM lab running an esxi 7 and then vcenter 7. However, the install fails with the message and log below.
The install aborts due to a certificate expired but the certificate is not expired... Anyone facing the same problem? All machines are NTP synchronized.
+ <ManifestValidate valid="true"/>
2020-07-21T23:05:11.566Z - info: output:CERTIFICATE
+ <CertificatePeriod expired="true"/>
2020-07-21T23:05:11.580Z - info: output:CERTIFICATE
+ <CertIssuer>
+ /C=US/ST=California/L=Palo Alto/O=VMware, Inc.
+ </CertIssuer>
+ <CertSubject>
+ /C=US/ST=California/L=Palo Alto/O=VMware, Inc.
+ </CertSubject>
+ <X509Cert>
+ -----BEGIN CERTIFICATE-----
+ MIIDyzCCArOgAwIBAgIJAIR/y018RgMXMA0GCSqGSIb3DQEBCwUAME0xCzAJBgNV
...
+ -----END CERTIFICATE-----
+ </X509Cert>
2020-07-21T23:05:30.692Z - info: output:ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.vi.import.vapp.create.spec</Type>
+ <LocalizedMsg>
+ Create import spec failed. Please verify importSpec
+ </LocalizedMsg>
+ </Error>
+ </Errors>
2020-07-21T23:05:30.726Z - info: output:RESULT
+ ERROR
2020-07-21T23:05:30.726Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><CertificatePeriod expired="true"/><CertIssuer>/C=US/ST=California/L=Palo Alto/O=VMware, Inc.</CertIssuer><CertSubject>/C=US/ST=California/L=Palo Alto/O=VMware, Inc.</CertSubject><X509Cert>-----BEGIN CERTIFICATE-----MIIDyzCCArOgAwIBAgIJAIR/y018RgMXMA0GCSqGSIb3DQEBCwUAME0xCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRIwEAYDVQQHDAlQYWxvIEFsdG8xFTATBgNVBAoMDFZNd2FyZSwgSW5jLjAeFw0xNjA5MDgwMTE3MjFaFw0yOTEyMzEwMTE3MjFaME0xCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRIwEAYDVQQHDAlQYWxvIEFsdG8xFTATBgNVBAoMDFZNd2FyZSwgSW5jLjCCASAwDQYJKoZIhvcNAQEBBQADggENADCCAQgCggEBALU9NUtC39fqG7yo2XAswUmtli9uA+31uAMw9FFHAEv/it8pzBQZ/4r+2bN+GnXOWhuDd1K4ApKMRvoO4LwQfZxrkx4pXrsu0gdb4OunHw0D8MrdzSoob8Js/uq+IJ+8Bhsc6b7RzTUt9HeDWzHasAJVgMsjehGt23ay9FKOT6dVD6D/Xi3qJnB/4t/XNS6L63dC3ea4guzKDyLaXIP5bf/m56jvVImFjhhTW2ASbnEUlZIVrEuyVcdG7e3FvZufE553JmHL0YG/0m5bIHXKRzBRx0D3HHOAzOKwkkOnxJHSTN4Hz8hSYCWvzUAjSYL3Q8qiTd7GHJ2ynsRnu3KlzKUCAQOjga8wgawwHQYDVR0OBBYEFHg8KQJdm8NPQDmYP41uEgKG+VNwMH0GA1UdIwR2MHSAFHg8KQJdm8NPQDmYP41uEgKG+VNwoVGkTzBNMQswCQYDVQQGEwJVUzETMBEGA1UECAwKQ2FsaWZvcm5pYTESMBAGA1UEBwwJUGFsbyBBbHRvMRUwEwYDVQQKDAxWTXdhcmUsIEluYy6CCQCEf8tNfEYDFzAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBCwUAA4IBAQADK9uUhsXzpuUcWJq83Vh2HHSxZ/DdR6h+FNYHfEX8h8DOIwhRHhIHoqXkwwnpbjipFBtSzNKzTmzMQBwB7GwzGSsBO2TU8alX2ssnDg2AqwgIeLzclfaQlYoid678KrewnFryr9PYMntr7uyU1duesmey12GS2z5UIhA4BaOnrPJcLCP22nXVlPEsa46ob7XHj4ngZ0ck/qE58Z90GaAuxaa2R3OlHQ+AhXc3q5IixqMDa0MLPd41Qv2kC5iZ+tCfXVdlf4/RqQBNHR8FFVxcjpaROId9Y9/yHdsMt55nN7pf7vRf5vSk1bHvLmlOYgiRtAj6rdPq0c+/C+fct1cM-----END CERTIFICATE-----</X509Cert><Errors><Error><Type>ovftool.vi.import.vapp.create.spec</Type><LocalizedMsg>Create import spec failed. Please verify importSpec</LocalizedMsg></Error></Errors></data>
2020-07-21T23:05:30.728Z - error: Ovf Service:vmrefFlag: false
2020-07-21T23:05:30.728Z - info: Cancelling timeout due to error from progress callback
2020-07-21T23:05:30.728Z - error: Progress Controller: [VCSA ERROR] - Progress callback error
2020-07-21T23:05:30.728Z - error: Progress Controller: [VCSA ERROR] - Details Create import spec failed. Please verify importSpec
2020-07-21T23:05:30.733Z - info: Cancelling the ping timer for session mgmt
2020-07-21T23:05:30.733Z - info: Cancelling the ping timer for session mgmt
2020-07-21T23:05:30.751Z - info: ovfProcess child process exited with code 1
Buongiorno,
dopo perdita da parte di VCSA 5.1 col NAS (per problemi al NAS), e dopo correzione degli errori al file system, il vCenter non è più funzionante, anzi lo "START" è grayed-out.
Tentando di ripristinare la situazione lanciando "Setup Wizard" (configure with default settings), la configurazioe del databse va a buon fine, mentre ricevo l'errore in oggetto per SSO. Ho cercato invano una soluzione, provato diversi workaround, ma nulla... Qualche idea?
Questo è l'errore completo di SSO:
Failed to execute '/usr/sbin/vpxd_servicecfg sso write embedded embedded CENSORED CENSORED':
VC_CFG_RESULT=721(Error: An unexpected error has ocurred during database operation. Please double check the database configuration)
Grazie.
Hi Community,
I previously used SCP to backup my 6.5 VCSA to a Linux server. Looking at the documentation for v7 SCP is not mentioned any more. Has anyone come across this in their upgrades? Does it still work?
TIA,
David
Hi,
Firstly : i'm sorry for my english and thank for your futur help
I have a problem since 1 week on my vsphere/vcenter environnement. i have this error :
I have tried to restore my vcenter from 1 week when i know all works but i have error again. I search on forum same problem and solutions but nothink works.
Thanks for your help
Regards
Intitek
Hey Guys,
we have the Problem that we cannot create new User under Administration-->SSO-->Users and Groups. When i login with administrator@vsphere.local to the VCSA and try to create new User it shows you do not have permission to view this object. The administrator@vsphere.local is in Administrator Group under Global Permissions and Roles. Basically even with other Users which have Admin rights it is not possible to create new User.
I can only add AD User which is not what we want. We just need a User to logon to the VCSA.
How can we fix this issue? Is the User Database corrupt? Because it worked for sure before. We didnt do any Updates in the meantime.
When you need further Information please dont hesitate to ask me.
Thank you in advanced.
Kind regards
Daniel
Hi All,
Is it possible to enable vCHA across two vC instances in linked mode?
Active node o 1 vc instance, Passive and Witness on other vc instance.
Let me know your thoughts. Thank you.
Best Regards,
Vijay
When replacing a self signed vcenter 6.7 certificate with a public cert the operation fails and vcenter reverts back to a self signed cert.
Error while starting services, please see service-control log for more details
Status : 0% Completed [Operation failed, performing automatic rollback]
Error while replacing Machine SSL Cert, please see /var/log/vmware/vmcad/certificate-manager.log for more information.
Performing rollback of Machine SSL Cert...
Same issue is published here. https://blog.krogloth.de/vmware-vcenter-vcsa-ssl-certificates-using-lets-encrypt/
Is pressing the Ctrl+C the only solution on 6.7 to keep the public cert?
Thanks
Hi i need hlep to know the process to patch vcenter server with external psc version 6.7 to 6.7u3f
Thanks for help
Hi everyone,
I have 3 Cluster deploy Agentless antivirus.the Cluster03 was filed.
When I try resolve GI agent,it was filed,sea "Communicating with EsxAgentManager Error",and the EAM Status "Staring".
and the vCenter Server Extensions --vSphere ESX Agent Manager--configure ---ESX Agencies empty, but the other cluster normal running.
in the vcsa shell ,the vmware-eam service is running
I am trying Restarting VCSA /NSX MGMT/ vmware-eam service
How can I fix it ?
---------
EM
Which certificates should be procured to enable a secure connection between a vCenter Server and local machines in an organization that already has a CA?
Hey guys
I'm working on changing my authentication from IWA to LDAPS, as the user/group lookup happens via LDAP when you're using IWA.
The change is pretty much straight forward as I'd have to delete the IWA identity source and recreate it as LDAPS.
But I'm unsure of what will happen to my already configured roles.
I have a ton of roles configured to use AD groups.
Would these be removed, once i delete my IWA identity source? Or would they stay and continue to work after i recreate my identity source?
Has anyone else attempted this?
I am about to upgrade vcsa from 6.7 to 7.0 which I am using all external PSCs
I did the test in a lab and I did it one site at a time. (converged the PSC in one site, and ran the vcsa upgrade)
But vmware is saying I need to converge all the PSCs in all sites before upgrading to vcsa7
any idea?
Hi,
I'm testing the upgrade of vCenter 6.5 to 6.7 in a lab. Cloned my DC's, PSC appliance and 4 vCenter Server appliances connected to the PSC. When now starting the appliances in my testlab, the vCenter 5480 interface is accessible, but all services are down.
When I run "Service control --status", only lwsmd and vmafdd are running, all other services are down. IP has remained the same, name hasn't changed. Only thing that changed is the mac-address. Could this have triggered some certificate changes or becoming invalid?
Hello,
After I move The VCSA from one host to another host I cannot reach the VCSA.
So I try to connect to the ESXi host and I see the VCSA not taking IP I check on Setting I found an error on the front of CPU Memory and storage with the below message:
As this host resources are being managed by vcenter server, some configuration option are disabled.if you wish to change this VM's resources settings, please do so from vcenter server.
Hi,
For unknown reason, VMware-vapi-endpoint this service failed to start on our vcsa 6.5, i tried to dig out by vecs-cli, but with no luck, here are the error messages:
#/usr/lib/vmware-vmafd/bin/vecs-cli entry list --store TRUSTED_ROOT_CRLS
Number of entries in store : 1
vecs-cli failed. Error 11: Possible errors:
LDAP error: Administrative limit exceeded
Win Error: Operation failed with error ERROR_BAD_FORMAT (11)
#/usr/lib/vmware-vmafd/bin/vecs-cli entry list --store TRUSTED_ROOT_CRLS --text | less
vecs-cli failed. Error 4312: Possible errors:
LDAP error: Unknown (extension) error
Win Error: Operation failed with error ERROR_OBJECT_NOT_FOUND (4312)
Is it related to TRUSTED_ROOT_CRLS issue ?
Thanks
vCenter service in the Windows server is down - in our POC environment.
our vCenter admin account "administrator@vSphere.local" got locked.
Error message while Restarting the services using command line tool:
Service-control failed. Error: Failed to start services in profile ALL. RC=1, st
derr=Failed to start vapi-endpoint, sca, vpxd-svcs services. Error: Operation ti
med out
Hi,
i just noticed, that the CPU load from around 30% jumps to around 70%. And this for the complete time since i installed the update.
Even after a reboot i have the same problem.
I found two hints:
The vAPI Endpoint shows a warning:
Failed to connect to 1da6ff8a-0bfd-4605-b4cc-c18ba520e95b\com.vmware.vcenter.nsxd.vapi vAPI provider.
And when using "top" on the vCenter CLI i have one process with high CPU:
PID USER PR NI VIRT RES %CPU %MEM TIME+ S COMMAND
22892 root 20 0 753.5m 85.6m 98.7 0.5 30:11.56 S /usr/lib/vmware-wcp/wcpsvc --port 8920 --logfile /var/log/vmware/wcp/wcpsvc.log --configfile /etc/vmware/wcp/wcpsvc.yaml --audit-+
When i'm searching google for that service i found "Workload Management" this is for "Kubernetis", this i havn't licensed and i havn't NSX-D installed.
I stopped the serivce "Workload Control Plane" and the CPU load goes down.
Has somebody seen this behavior too?
Looks like a bug to me...
Kind regards
Stefan
Is there anyway to get certifcate manager to generate new certs longer than 2 years? We just ran Option 8 - Reset All Certificates on a embedded vCenter and it only renewed for 2 years.
Good! After a sudden blackout, vCenter did not start, but best of all, I tried to start replicas of previous days and the problem was also. I enclose what I get when I force the start of the services:
Operation not cancellable. Please wait for it to finish...
Performing start operation on service lwsmd...
Successfully started service lwsmd
Performing start operation on service vmafdd...
Successfully started service vmafdd
Performing start operation on service vmdird...
Successfully started service vmdird
Performing start operation on service vmcad...
Successfully started service vmcad
Performing start operation on service vmware-sts-idmd...
Successfully started service vmware-sts-idmd
Performing start operation on service vmware-stsd...
Successfully started service vmware-stsd
Performing start operation on service vmdnsd...
Successfully started service vmdnsd
Performing start operation on profile: ALL...
Service-control failed. Error: Failed to start services in profile ALL. RC=1, stderr=Failed to start topologysvc, vpxd-svcs, vmware-postgres-archiver, vmware-vpostgres services. Error: Operation timed out