SLES11 SP2: extract information from ESXi takes very long and aborts

[edgarmat]

Hello,

  I'm trying to extract status information, using a Nagios plugin called check_esx3, from an ESXi 4.0 using VMware-vSphere-Perl-SDK-5.1.0-780721 on a SLES11 SP2 system with perl-5.10.0 and/or perl-5.16.2 (compiled from source). This takes a ridiculous amount of time: Each step (4 in total: 1)ServiceInformation-test, 2)Login, 3)get properties, 4) extract information) takes at least 45 seconds to complete. The final step fails with an incomplete response (probably due to a timeout).

Running the same(!) script, using the same SDK version, on CentOS with perl-5.8.8 takes 2 seconds to complete with correct information.

Has anyone seen this problem before? And has/knows of a solution ?! 😉

Thanks, Edgar.

NB: The full output from the command below is attached.

The output from "./check_esx3 -u root -p <pwd> -H vir1995-pa -l runtime --trace 4" (trimmed a bit):

REQUEST: $VAR1 = '<?xml version="1.0" encoding="UTF-8"?>

   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

                     xmlns:xsd="http://www.w3.org/2001/XMLSchema"

                     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

   <soapenv:Body>

<RetrieveProperties xmlns="urn:vim25"><_this type="PropertyCollector">ha-property-collector</_this>

<specSet><propSet><type>HostSystem</type><all>0</all></propSet><objectSet><obj type="Folder">ha-folder-root</obj>

<skip>0</skip><selectSet xsi:type="TraversalSpec"><name>folderTraversalSpec</name><type>Folder</type><path>childEntity</path><skip>0</skip><selectSet><name>folderTraversalSpec</name></selectSet><selectSet>

-----<SNIP>-----

<name>folderTraversalSpec</name></selectSet></selectSet><selectSet xsi:type="TraversalSpec"><name>resourcePoolVmTraversalSpec</name><type>ResourcePool</type><path>vm</path><skip>0</skip></selectSet></objectSet></specSet></RetrieveProperties></soapenv:Body></soapenv:Envelope>

';

RESPONSE: $VAR1 = '<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"

xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soapenv:Body>

<RetrievePropertiesResponse xmlns="urn:vim25"><returnval><obj type="HostSystem">ha-host</obj></returnval></RetrievePropertiesResponse>

</soapenv:Body>

</soapenv:Envelope>';

REQUEST: $VAR1 = '<?xml version="1.0" encoding="UTF-8"?>

   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

                     xmlns:xsd="http://www.w3.org/2001/XMLSchema"

                     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

   <soapenv:Body>

<RetrieveProperties xmlns="urn:vim25"><_this type="PropertyCollector">ha-property-collector</_this>

<specSet><propSet><type>HostSystem</type><all>0</all><pathSet>name</pathSet><pathSet>runtime</pathSet><pathSet>overallStatus</pathSet><pathSet>configIssue</pathSet></propSet><objectSet><obj type="HostSystem">ha-host</obj>

</objectSet></specSet></RetrieveProperties></soapenv:Body></soapenv:Envelope>

';

RESPONSE: $VAR1 = '<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"

xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soapenv:Body>

<RetrievePropertiesResponse xmlns="urn:vim25"><returnval><obj type="HostSystem">ha-host</obj><propSet><name>configIssue</name><val xsi:type="ArrayOfEvent"></val></propSet><propSet><name>name</name><val xsi:type="xsd:string">VIR1995-PA</val></propSet><propSet><name>overallStatus</name><val xsi:type="ManagedEntityStatus">green</val></propSet><propSet><name>runtime</name><val xsi:type="HostRuntimeInfo"><connectionState>connected</connectionState><powerState>poweredOn</powerState><inMaintenanceMode>false</inMaintenanceMode><bootTime>2012-11-07T08:05:29.551958Z</bootTime><healthSystemRuntime><systemHealthInfo><numericSensorInfo><name>System Board 9 Power Meter - Device

-----------<SNIP>---------------

Port 2I Box 1 Bay 5 : 558GB : Data Disk</name><status><label>Green</label><summary>Physical element is functioning as expected</summary><key>Green</key></status></storageStatusInfo><storageStatusInfo><name>Disk 6 on HPSA1 : Port 2I Box 1 Bay 6 : 558GB : Data Disk</name><status><label>Green</label><summary>Physical element is functioning as expected</summary><key>Green</key></status></storageStatusInfo><storageStatusInfo><name>Disk 7 on HPSA1 : Port 2I Box 1 Bay 7 : 558GB : Data Disk</name><status><label>Green</label><summary>Physical el';

CHECK_ESX3 CRITICAL - SOAP request error - possibly a protocol issue: <?xml version="1.0" encoding="UTF-8"?>

[SteeringWheel]

Got the same problem, cause and solution are described here: http://communities.vmware.com/message/2157725