Skip to main content

Enabling debug logging on the VMware vSphere Service

  • login to vCenter Server appliance using ssh root


  • Login to Shell prompt and go to the below path


        vCenter Server Appliance 6.7 (HTML) /usr/lib/vmware-vsphere-ui/server/conf/serviceability.xml 

        vCenter Server Appliance 6.7(FLEX) /usr/lib/vmware-vsphere-client/server/configuration 

        Windows vCenter -C:\ProgramData\VMware\vCenterServer\runtime\vsphere-                                ui\server\configuration

  • Open and change the file Serviceability.xml

from

<root level="INFO">

<appender-ref ref="SIFTED_LOG_FILE"></appender-ref>

<appender-ref ref="LOG_FILE"></appender-ref>

</root>

to:

<root level="DEBUG">

<appender-ref ref="SIFTED_LOG_FILE"></appender-ref>

<appender-ref ref="LOG_FILE"></appender-ref>

</root>

  • re-start the vSphere Web Client service.


 -> Flex: service-control --stop vsphere-client

           service-control --start vsphere-client


  -> HTML5: service-control --stop vsphere-ui

                 service-control --start vsphere-ui

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