Skip to main content

VCSA service not starting

 Error while starting VCSA service:

~ ]# service-control --start vpxd

Operation not cancellable. Please wait for it to finish...

Performing start operation on service vpxd...

Error executing start on service vpxd. Details {

    "detail": [

        {

            "id": "install.ciscommon.service.failstart",

            "translatable": "An error occurred while starting service '%(0)s'",

            "args": [

                "vpxd"

            ],

            "localized": "An error occurred while starting service 'vpxd'"

        }


Verify logs:

verify the /var/log/vmware/vpxd/vpxd.log and check any errors :

[Originator@6876 sub=HostPicker opID=sps-Main-407637-499-33] Couldn't find any candidate host that satisfies all constraints

error vpxd[47211 No hosts are compatible with provided version 6.7.2


Solution:

     1.Upgraded hardware version to 13 as your new esxi was 6.7.2.

     2.DNS issue resolved on host by changing hosts file on VCSA server.(make sure the IP and DNS names is mapped properly) after login to VCSA using root user.

     3.restarted Service on VCSA 




Comments

Post a Comment

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...
Post a Comment
Read more

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported
Post a Comment
Read more