- #Creating new vm esxi 6.5 error unhandled exception update#
- #Creating new vm esxi 6.5 error unhandled exception license#
INFO:root:Service: applmgmt, Action: stop
INFO:root:Service: vmware-vsan-health, Action: stop INFO:root:Service: vmware-syslog-health, Action: stop INFO:root:Service: vmware-psc-client, Action: stop T14:15:06.608Z INFO certificate-manager please see service-control.log for service status T14:15:06.607Z INFO certificate-manager Running command :- service-control -stop -ignore -all Our certificate-manager however decided it was time to throw an error:
#Creating new vm esxi 6.5 error unhandled exception update#
Once you accepted the change it is proposing it will update the certificates in the locations it is needed and stop and start all services. Certificate-manager tool on the vCenter Server Appliance So we went ahead and fired up the “certificate-manager” tool which can be found in “/usr/lib/vmware-vmca/bin/certificate-manager”, picked option 3 to replace the the Machine SSL with a VMCA certificate (which is a self-signed certificate but that’s fine for this environment), entered the information which was present in the current certificate such as hostnames and IP-address information and accepted all changes. Funny thing though is that this particular vCenter Appliance should’nt even be working anymore because once the certificate is expired, most of the time it won’t even start all of the vCenter services once you reboot it. Below you can find some snippets of logs which might be interesting for you to match your problem to the one I was having:Īll certificates checked out but guess what, the “MACHINE_SSL_CERT” didn’t. Which got me thinking and looking at the certificates for this vCenter Server Appliance.
#Creating new vm esxi 6.5 error unhandled exception license#
Once we dove into the log files from the license service in “/var/log/vmware/cis-license/license.log” we noticed some Security Token Service STS service, SSO service and web-client service issues in regards to certificates. We also noticed that the License module in the vSphere client was also providing us with a timeout. Going to the ESXi host directly you could however see that the license was present and activated.
Going to the “Licensed Features” tab in the vSphere Client (VCSA version 6.0 GA) usually gives you a nice overview of what vSphere license is installed, but this time it was just empty. So we started troubleshooting the VCSA server and noticed that it couldn’t retrieve the installed licenses (VMware vSphere Enterprise Plus) from the production ESXi hosts anymore. Which is weird and something I’ve never seen before. For starters the vMotion and Storage vMotion features weren’t working anymore because of time-outs. Recently we’ve had some weird issues on one of our customers vCenter Servers.
0 kommentar(er)
