Vmomi tracing Log Level

[rfaulconer]

We are running HP hosts and have ran into the scenario described in VMware KB 1033921 where we get frequent CIM messages that can be safely ignored.  We do NOT want to disable CIM as we DO desire the status monitors.

I tripped over a setting in the config.xml file

<!-- The log level at which to output vmomi tracing -->

    <traceAt> verbose </traceAt>

When I changed it to

    <traceAt> warning </traceAt>

Three of the 4 safe to ignore lines (verbose and both info lines) quit logging.

Am I taking a risk by changing the logging level?  I am cluless about what vmomi tracing is supposed to do for me even after reading through every hit I could find.

[adelisa]

Hi welcome to fourm .

you can chage the tracing log level it will not hamper any thing .

please find the steps are below .

To confirm that the error indicates a configuration data problem for a virtual machine:

1. Open the vpxd.log file for vCenter Server in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\logs.
2. Search for the following error:
   [VpxVmomi] Exception while sending result: Invalid argument

To identify the virtual machine with a configuration data problem and resolve the problem:

1. Open the vpxd.cfg file in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter.
2. Add the following entries to the vpxd.cfg file to enable VMOMI tracing.
   <config>
   ...
   <trace>
   <vmomi>
   
   <calls>true</calls>
   
   <verbosity>verbose</verbosity>
   
   <verboseLogBytes>20485760</verboseLogBytes> <!--20MB-->
   </vmomi>
   </trace>
   
   <log>
   
   <maxFileNum>50</maxFileNum>
   
   <compressOnRoll>false</compressOnRoll>
   
   <level>verbose</level>
   </log>
   
   ..
   </config>
3. Restart the VMware vCenter Server service. 
4. Run CapacityIQ for two to three minutes until the error occurs.
5. Open the vpxd.log file and search for the first virtual machine MOID before the InvalidArgument error.
   (vmodl.query.PropertyCollector.ObjectUpdate){
   dynamicType=<unset>,
   kind="enter"
   obj='vim.VirtualMachine:vm-12345',
   changeSet=(vmodl.query.PropertyCollector.Change)[
   ...
   ...
   Format Fault class VMacore:InvalidArgumentException(Invalid argument)
   [VpxVmomi]Exception while sending result: Invalid argument
   
   In this log message, the MOID of the virtual machine with the configuration data problem is vm-12345.
6. Connect to the SQL server that hosts the vCenter Server database and run the following query to locate the virtual machine.
   select name from vpx_entity where id = 12345;
7. In the inventory tree of the vSphere Client, right-click the virtual machine and select Power > Power Off.
8. In the Configuration tab for the host that stores the virtual machine, click Storage, right-click the datastore that stores the virtual machine, and select Browse Datastore.
9. In the Datastore Browser dialog box, right-click the appropriate .vmx file and select Add to Inventory.
10. In the inventory tree, right-click the virtual machine and select Power > Power On.

_______________________________
Affirmation without discipline is the beginning of delusion.