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

sascha

Hi,

since a couple of days (to be exact 16.0918 - 22:30 local time) the graphs of 8 VMs are not updated any more. Not all VMs of this vCenter are affected. I found the following in error-vmware.log:

.. lots of line like the 3 ones below ...
"my" variable $vmware_signal_file masks earlier declaration in same scope at /home/lpar2rrd/lpar2rrd/bin/vmw2rrd.pl line 2056.
"my" variable $vmware_signal_file masks earlier declaration in same scope at /home/lpar2rrd/lpar2rrd/bin/vmw2rrd.pl line 2056.
"my" variable $vmware_signal_file masks earlier declaration in same scope at /home/lpar2rrd/lpar2rrd/bin/vmw2rrd.pl line 2056.
Sun Sep 16 23:30:17 2018: INFO Time diff > 5 minutes (with TZ respect) 10.212.7.120:esx-st
2018-09-16T20:50:32.382191Z (local time: Sun Sep 16 23:30:17 2018) :
SOAP request error - possibly a protocol issue: <?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="VirtualMachine">vm-1006</obj><propSet><name>alarmActionsEnabled</name><val xsi:type="xsd:boolean">true</val></propSet><propSet><name>availableField</name><val xsi:type="ArrayOfCustomFieldDef"></val></propSet><propSet><name>capability</name><val xsi:type="VirtualMachineCapability"><snapshotOperationsSupported>true</snapshotOperationsSupported><multipleSnapshotsSupported>true</multipleSnapshotsSupported><snapshotConfigSupported>true</snapshotConfigSupported><poweredOffSnapshotsSupported>true</poweredOffSnapshotsSupported><memorySnapshotsSupported>true</memorySnapshotsSupported><revertToSnapshotSupported>true</revertToSnapshotSupported><quiescedSnapshotsSupported>true</quiescedSnapshotsSupported><disableSnapshotsSupported>false</disableSnapshotsSupported><lockSnapshotsSupported>true</lockSnapshotsSupported><consolePreferencesSupported>false</consolePreferencesSupported><cpuFeatureMaskSupported>true</cpuFeatureMaskSupported><s1AcpiManagementSupported>true</s1AcpiManagementSupported><settingScreenResolutionSupported>false</settingScreenResolutionSupported><toolsAutoUpdateSupported>false</toolsAutoUpdateSupported><vmNpivWwnSupported>true</vmNpivWwnSupported><npivWwnOnNonRdmVmSupported>true</npivWwnOnNonRdmVmSupported><vmNpivWwnDisableSupported>true</vmNpivWwnDisableSupported><vmNpivWwnUpdateSupported>true</vmNpivWwnUpdateSupported><swapPlacementSupported>true</swapPlacementSupported><toolsSyncTimeSupported>true</toolsSyncTimeSupported><virtualMmuUsageSupported>true</virtualMmuUsageSupported><diskSharesSupported>true</diskSharesSupported><bootOptionsSupported>true</bootOptionsSupported><bootRetryOptionsSupported>true</bootRetryOptionsSupported><settingVideoRamSizeSupported>true</settingVideoRamSizeSupported><settingDisplayTopologySupported>false</settingDisplayTopologySupported><recordReplaySupported>true</recordReplaySupported><changeTrackingSupported>true</changeTrackingSupported><multipleCoresPerSocketSupported>true</multipleCoresPerSocketSupported><hostBasedReplicationSupported>true</hostBasedReplicationSupported><guestAutoLockSupported>true</guestAutoLockSupported><memoryReservationLockSupported>true</memoryReservationLockSupported><featureRequirementSupported>true</featureRequirementSupported><poweredOnMonitorTypeChangeSupported>true</poweredOnMonitorTypeChangeSupported><seSparseDiskSupported>true</seSparseDiskSupported><nestedHVSupported>true</nestedHVSupported>

... more XML-Data of one of the affected VMs ....

Do you have any idea?
Sascha

sascha

Rebooting ESX and vCenter solved the problem.

Pavel

thanks for posting solution.

Looks like a problem was in VMware.