Hi Community,
I have a Windows Server based vCenter Server 6.5 Update 1 with external platform services controller. VMware VirtualCenter service is not starting . Inside vpxd-xxx.log file (attached), it is logging following errors;
warning vpxd[05288] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x000001e8d1660e98, h:2660, <TCP '0.0.0.0:0'>, <TCP '[::1]:10080'>>, e: system:10061(No connection could be made because the target machine actively refused it)
warning vpxd[05448] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x000001e8d1d3b598, h:2660, <TCP '0.0.0.0:0'>, <TCP '[::1]:10080'>>, e: system:10061(No connection could be made because the target machine actively refused it)
info vpxd[04688] [Originator@6876 sub=VpxdAuthClient] fallback to loginByCertificate
on External appliance based PSC running 6.7 , service-control --status shows all services running.
DomainJoin-cli query shows PSC is joined to the AD domain.
I have tried following method, it does not produce required result. I followed command line option
/usr/lib/vmware-vmafd/bin/dir-cli computer password-reset --login administrator --live-dc-hostname<Platform Services Controller FQDN> --password <administrator@vsphere.local password>
I didn't restore vCenter Server from backup. What I would do is to suspend External PSC anytime I shutdown my lab setup while shutting down vCenter Server as well.
Any idea as to how to resolve this issue.
this is windows issue in 2012 some time in evaluation copy
I have managed to resolve it by performing the following;
1. Backed up existing vPostGres database.
2. Uninstalling vCenter Server on Windows Server 2016 . I didnt export certificates.
3. Re-installing vCenter Server with an existing external platform service controller (appliance based)
4. After successful installation, stopped vpxd and content library services, restored vPostGres database
5. Started vpxd and content-library services. Then, i could access flash and HTML5 based web client with same set of ESXi hosts. I had to disable and enable HA before adding hosts back into the
cluster though.