book
Article ID: 332310
calendar_today
Updated On:
Cause
This issue occurs due to a duplicate entry referencing port 8089 within the /etc/vmware-vpx/proxy.xml file.
Resolution
To resolve this issue, remove the duplicate entry referencing port 8089 within the /etc/vmware-vpx/proxy.xml file.
To remove the duplicate entry:
- Log in to the vCenter Server Appliance as the root user.
- Open the console.
- Run this command:
cd /etc/vmware-vpx
- Run this command to view an output that contain all lines with 8089:
grep "8089</serverNamespace>" proxy.xml
You see output similar to:
<serverNamespace>192.168.2.2:8089</serverNamespace>
<serverNamespace>VC-DSN:8089</serverNamespace>
<serverNamespace>[fe80::250:56ff:fe03:3f2]:8089</serverNamespace>
<serverNamespace>sdkTunnel:8089</serverNamespace>
- If you receive two similar lines from the output in step 4, make a copy of the proxy.xml file by running this command:
cp /etc/vmware-vpx/proxy.xml /etc/vmware-vpx/proxy.bak
- Open /etc/vmware-vpx/proxy.xml file using a text editor and locate the duplicated entries.
<e id="26">
<_type>vim.ProxyService.LocalTunnelSpec</_type>
<accessMode>httpOnly</accessMode>
<port>8089</port>
<serverNamespace>vCenter.domain:8089</serverNamespace>
</e>
<e id="27">
<_type>vim.ProxyService.LocalTunnelSpec</_type>
<accessMode>httpOnly</accessMode>
<port>8089</port>
<serverNamespace>vCenter.domain:8089</serverNamespace>
</e>
- Remove the complete element with highest element ID (For example, 27). The endpoint entry looks similar to:
<e id="27">
<_type>vim.ProxyService.LocalTunnelSpec</_type>
<accessMode>httpOnly</accessMode>
<port>8089</port>
<serverNamespace>vCenter.domain:8089</serverNamespace>
</e>
- The elementID values must be sequential - if after removing the duplicate element ID there is a gap in the sequence it is necessary to renumber the element ID values after the removed entry. For example, if element ID 27 was removed and there is an element ID of 28 then change this element ID from 28 to 27 and so on.
- Locate this entry in the proxy.xml file and change the length variable to the total number of remaining endpoint IDs. This should be one less than the current variable
<config>
<EndpointList>
<_length>29</_length>
<_type>vim.ProxyService.EndpointSpec[]</_type>
<e id="0">
- Save the proxy.xml file and restart the VirtualCenter Server service.
Additional Information
The elementID values must be sequential (0,1,2,3,4,5...) - if there is a missing element ID in the sequence (0,1,2,4,5...) then vpxd fails to start with InvalidArgument in the vpxd log file.