1 2 Previous Next 17 Replies Latest reply on Jul 23, 2019 6:16 AM by RajeevVCP4

    Vcenter installation Failure: "Failed to send http data"

    Reydar1 Lurker

      Hello,

       

      I am trying to install vcenter and keep getting this error. I have disabled my firewall and still get the error. Please help!

       

      --

      2018-07-03T14:37:44.444Z - info: output:PROGRESS

       

      2018-07-03T14:37:50.279Z - info: output:

       

      2018-07-03T14:37:50.279Z - info: output:

       

      2018-07-03T14:37:50.279Z - info: output:ERROR

      + <Errors>

      + <Error>

      + <Type>ovftool.http.send</Type>

      + <LocalizedMsg>

      + Failed to send http data

      + </LocalizedMsg>

      + </Error>

      + </Errors>

       

       

      2018-07-03T14:37:52.414Z - info: output:RESULT

      + ERROR

       

       

      2018-07-03T14:37:52.415Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>ovftool.http.send</Type><LocalizedMsg>Failed to send http data</LocalizedMsg></Error></Errors></data>

      2018-07-03T14:37:52.415Z - error: Ovf Service:vmrefFlag: false

      2018-07-03T14:37:52.416Z - info: Cancelling timeout due to error from progress callback

      2018-07-03T14:37:52.416Z - error: Progress Controller: [VCSA ERROR] - Progress callback error

      2018-07-03T14:37:52.416Z - error: Progress Controller: [VCSA ERROR] - Details Failed to send http data

      2018-07-03T14:37:52.419Z - info: Cancelling the ping timer for session mgmt

      2018-07-03T14:37:52.419Z - info: Cancelling the ping timer for session mgmt

      2018-07-03T14:37:52.437Z - info: ovfProcess child process exited with code 1

      2018-07-0

        • 1. Re: Vcenter installation Failure: "Failed to send http data"
          daphnissov Guru
          Community WarriorsvExpert

          Please show screenshots of your installation process that contain the values you're using.

          • 2. Re: Vcenter installation Failure: "Failed to send http data"
            Reydar1 Lurker

            1.jpg2.jpg3.jpg4.jpg5.jpg6.jpg7.jpg

            2018-07-03T21:59:21.796Z - info: installerLogFile: C:\Users\David\AppData\Local\Temp\vcsaUiInstaller\installer-20180703-145921793.log

            2018-07-03T21:59:21.813Z - info: networkLogFile: C:\Users\David\AppData\Local\Temp\vcsaUiInstaller\network-20180703-145921793.log

            2018-07-03T21:59:21.935Z - debug: wizardTitle:  - Stage 1: Deploy appliance

            2018-07-03T21:59:23.595Z - debug: wizardTitle: Install - Stage 1: Deploy appliance

            2018-07-03T21:59:28.569Z - debug: wizardTitle: Install - Stage 1: Deploy appliance

            2018-07-03T21:59:29.541Z - debug: nodeType: embedded

            2018-07-03T21:59:29.541Z - debug: wizardTitle: Install - Stage 1: Deploy vCenter Server with an Embedded Platform Services Controller

            2018-07-03T21:59:37.538Z - info: THUMBPRINT(Target): C0:23:3A:EB:EB:8C:E5:2B:76:CF:BE:76:B8:07:9D:FA:43:65:86:07

            2018-07-03T21:59:38.729Z - info: login() to server3.ftu.local

            2018-07-03T21:59:38.729Z - info: initializing vsphere API connection to server3.ftu.local:443

            2018-07-03T21:59:39.932Z - info: vimService apiType: HostAgent, version: 6.7.0

            2018-07-03T21:59:39.950Z - debug: session does not exist: server3.ftu.local, root

            2018-07-03T21:59:39.950Z - debug: Logging in to server3.ftu.local:443 as root

            2018-07-03T21:59:39.986Z - info: Logged in to server3.ftu.local:443 as root, session: 527cb454-284e-93bc-d7ac-bf022fcd9abc

            2018-07-03T21:59:39.987Z - debug: After successful login, initiate pingTimer with delay: 300000

            2018-07-03T21:59:40.006Z - debug: admin roles:[ { entity: { value: 'ha-folder-root', type: 'Folder' },

                principal: 'vpxuser',

                group: false,

                roleId: -1,

                propagate: true },

              { entity: { value: 'ha-folder-root', type: 'Folder' },

                principal: 'dcui',

                group: false,

                roleId: -1,

                propagate: true },

              { entity: { value: 'ha-folder-root', type: 'Folder' },

                principal: 'root',

                group: false,

                roleId: -1,

                propagate: true } ]

            2018-07-03T21:59:40.006Z - debug: user: root, userPrincipal: root

            2018-07-03T21:59:40.006Z - debug: userHasAdminRole:root:root: has admin role

            2018-07-03T21:59:40.006Z - debug: adminRole: true

            2018-07-03T21:59:40.006Z - info: host target precheck

            2018-07-03T21:59:40.326Z - info: hostPrecheck: server3.ftu.local, ha-host

            2018-07-03T21:59:40.326Z - info: ESXi hostVersion=6.7, minVersion=5.5

            2018-07-03T21:59:40.326Z - info: lockdownMode: 'lockdownDisabled'

            2018-07-03T21:59:40.327Z - info: inMaintenanceMode: false

            2018-07-03T21:59:40.327Z - info: hostPrecheck succeeded: server3.ftu.local

            2018-07-03T21:59:40.327Z - info: ESXi hostCheck was successful

            2018-07-03T21:59:40.356Z - debug: [object Object]

            2018-07-03T21:59:58.253Z - info: vmName: vcenter

            2018-07-03T21:59:58.291Z - debug: token:undefined, length:1, running total:1

            2018-07-03T21:59:58.291Z - info: number of vms with name, vcenter: 0

            2018-07-03T21:59:58.316Z - debug: Deployment size page description: Select the deployment size for this vCenter Server with an Embedded Platform Services Controller.

            2018-07-03T21:59:58.317Z - info: ovftoolCmd: F:\vcsa\ovftool\win32\ovftool.exe

            2018-07-03T21:59:58.317Z - debug: ovaFileNameRe: /.*_OVF10.ova$/

            2018-07-03T21:59:58.318Z - debug: files in F:\vcsa: VMware-vCenter-Server-Appliance-6.7.0.12000-8832884_OVF10.ova,ovftool,version.txt

            2018-07-03T21:59:58.318Z - info: ovaFile: F:\vcsa\VMware-vCenter-Server-Appliance-6.7.0.12000-8832884_OVF10.ova

            2018-07-03T21:59:58.706Z - info: probeOvf exited with status 0

            2018-07-03T21:59:58.708Z - info: probeOvf productName: VMware vCenter Server Appliance

            2018-07-03T21:59:58.709Z - info: probeOvf fullVersion: 6.7.0.12000 build 8832884

            2018-07-03T21:59:58.712Z - info: probeOvf result: + SUCCESS

            2018-07-03T21:59:58.718Z - info: layout file: F:\vcsa-ui-installer\win32\resources\app\resources\layout.json

            2018-07-03T21:59:58.718Z - info: nDeploymentOptions: 31

            2018-07-03T21:59:58.722Z - warn: checkDiskspace:[tiny-xlstorage]: dfsys was not obtained

            2018-07-03T21:59:58.722Z - debug: checkDiskspace:[tiny-xlstorage]: diskSpace, required: undefined, provided: 1700

            2018-07-03T21:59:58.722Z - info: checkDiskspace:[tiny-xlstorage]: true

            2018-07-03T21:59:58.722Z - warn: checkDiskspace:[tiny-lstorage]: dfsys was not obtained

            2018-07-03T21:59:58.722Z - debug: checkDiskspace:[tiny-lstorage]: diskSpace, required: undefined, provided: 825

            2018-07-03T21:59:58.722Z - info: checkDiskspace:[tiny-lstorage]: true

            2018-07-03T21:59:58.722Z - warn: checkDiskspace:[tiny]: dfsys was not obtained

            2018-07-03T21:59:58.722Z - debug: checkDiskspace:[tiny]: diskSpace, required: undefined, provided: 300

            2018-07-03T21:59:58.722Z - info: checkDiskspace:[tiny]: true

            2018-07-03T21:59:58.722Z - debug: default storage: tiny, 300

            2018-07-03T21:59:58.722Z - debug: large storage: tiny-lstorage, 825

            2018-07-03T21:59:58.722Z - debug: x-large storage: tiny-xlstorage, 1700

            2018-07-03T21:59:58.723Z - debug: pre-defined defIdx found: 0

            2018-07-03T21:59:58.723Z - info: defIdx: 0, id: tiny

            2018-07-03T21:59:58.725Z - info: { id: 'tiny',

              isDefault: 'true',

              cpu: 2,

              memory: 10240,

              'host-count': 10,

              'vm-count': 100,

              label: 'Tiny',

              description: undefined,

              diskSpace: 300,

              'disk-swap': 25600,

              'disk-core': 25600,

              'disk-log': 10240,

              'disk-db': 10240,

              'disk-dblog': 15360,

              'disk-seat': 10240,

              'disk-netdump': 1024,

              'disk-autodeploy': 10240,

              'disk-imagebuilder': 10240,

              'disk-updatemgr': 102400,

              undefined: 0 }

            2018-07-03T21:59:58.725Z - info: { id: 'default', label: 'Default' }

            2018-07-03T22:00:00.089Z - info: selectedProfile: id=tiny

            2018-07-03T22:00:00.090Z - debug: selectedProfile: { id: 'tiny',

              isDefault: 'true',

              cpu: 2,

              memory: 10240,

              'host-count': 10,

              'vm-count': 100,

              label: 'Tiny',

              description: undefined,

              diskSpace: 300,

              'disk-swap': 25600,

              'disk-core': 25600,

              'disk-log': 10240,

              'disk-db': 10240,

              'disk-dblog': 15360,

              'disk-seat': 10240,

              'disk-netdump': 1024,

              'disk-autodeploy': 10240,

              'disk-imagebuilder': 10240,

              'disk-updatemgr': 102400,

              undefined: 0 }

            2018-07-03T22:00:00.090Z - info: tgtHostName: server3.ftu.local, hostName: server3.ftu.local

            2018-07-03T22:00:00.091Z - debug: hardware: { vendor: 'Supermicro',

              model: 'SYS-6028R-WTRT',

              uuid: '00000000-0000-0000-0000-ac1f6b4146fa',

              otherIdentifyingInfo:

               [ { identifierValue: 'Default string', identifierType: [Object] },

                 { identifierValue: 'C8250FH11NB0107', identifierType: [Object] },

                 { identifierValue: 'Intel Haswell/Wellsburg/Grantley',

                   identifierType: [Object] },

                 { identifierValue: 'Supermicro motherboard-X10 Series',

                   identifierType: [Object] } ],

              memorySize: 68600238080,

              cpuModel: 'Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz',

              cpuMhz: 2400,

              numCpuPkgs: 2,

              numCpuCores: 12,

              numCpuThreads: 24,

              numNics: 2,

              numHBAs: 3 }

            2018-07-03T22:00:00.118Z - debug: Storage page description: Select the storage location for this vCenter Server with an Embedded Platform Services Controller.

            2018-07-03T22:00:00.157Z - debug: Got 1 datastores

            2018-07-03T22:00:00.183Z - debug: dsName: Primary, isWritable: true, dsType: VMFS

            2018-07-03T22:00:00.183Z - info: datastore: total=1, display=1

            2018-07-03T22:00:00.187Z - debug: selectedDatastoreIdx: 0,

            2018-07-03T22:00:02.738Z - debug: Selected datastore: { diskMode: 'thin',

              moRef: '5b39efc6-ac7e3668-ff05-ac1f6b4146fa',

              name: 'Primary',

              type: 'VMFS-6',

              mode: 'existing',

              datastores:

               [ { moid: '5b39efc6-ac7e3668-ff05-ac1f6b4146fa',

                   name: 'Primary',

                   type: 'VMFS-6',

                   versionNum: 6,

                   capacity: '1.74 TB',

                   freeSpace: '1.65 TB',

                   provisioned: '91.14 GB',

                   thinProvisioning: true,

                   displayThinProvising: 'Supported',

                   rawCapacity: 1911260446720,

                   rawFreeSpace: 1813399994368,

                   rawProvisioned: 97860452352 } ],

              diskModeName: 'thin' }

            2018-07-03T22:00:02.739Z - debug: selectedItem: { moid: '5b39efc6-ac7e3668-ff05-ac1f6b4146fa',

              name: 'Primary',

              type: 'VMFS-6',

              versionNum: 6,

              capacity: '1.74 TB',

              freeSpace: '1.65 TB',

              provisioned: '91.14 GB',

              thinProvisioning: true,

              displayThinProvising: 'Supported',

              rawCapacity: 1911260446720,

              rawFreeSpace: 1813399994368,

              rawProvisioned: 97860452352 }

            2018-07-03T22:00:02.739Z - debug: selectedDatastoreMoid: 5b39efc6-ac7e3668-ff05-ac1f6b4146fa

            2018-07-03T22:00:02.740Z - debug: sizingData: { id: 'tiny',

              isDefault: 'true',

              cpu: 2,

              memory: 10240,

              'host-count': 10,

              'vm-count': 100,

              label: 'Tiny',

              description: undefined,

              diskSpace: 300,

              'disk-swap': 25600,

              'disk-core': 25600,

              'disk-log': 10240,

              'disk-db': 10240,

              'disk-dblog': 15360,

              'disk-seat': 10240,

              'disk-netdump': 1024,

              'disk-autodeploy': 10240,

              'disk-imagebuilder': 10240,

              'disk-updatemgr': 102400,

              undefined: 0 }

            2018-07-03T22:00:02.740Z - debug: diskSpaceR: 26843545600

            2018-07-03T22:00:02.740Z - debug: selected datastore: Primary, freeSpaceGb: 1688, diskSpaceR=26843545600, diskMode=thin

            2018-07-03T22:00:02.740Z - debug: thin diskMode, freeSpace: 1813399994368, diskSpaceR: 26843545600

            2018-07-03T22:00:02.740Z - debug: validateDiskspace was successful

            2018-07-03T22:00:02.766Z - debug: Network setttings page description: Configure network settings for this vCenter Server with an Embedded Platform Services Controller.

            2018-07-03T22:00:02.766Z - info: networkFamily options IPv4, IPv6

            2018-07-03T22:00:02.836Z - debug: Got 1 networks

            2018-07-03T22:00:02.858Z - debug: networks retrieved: [ { _type: 'Network',

                _moid: 'HaNetwork-VM Network',

                host: [ [Object] ],

                name: 'VM Network',

                summary:

                 { network: [Object],

                   name: 'VM Network',

                   accessible: true,

                   ipPoolName: '' },

                vm: [ [Object] ],

                vimType: 'vim.Network' } ]

            2018-07-03T22:00:02.859Z - debug: networks filtered: [ { name: 'VM Network',

                moid: 'HaNetwork-VM Network',

                type: 'vim.Network' } ]

            2018-07-03T22:00:02.859Z - info: default network was set to VM Network

            2018-07-03T22:00:02.859Z - debug: nwSelected: { name: 'VM Network',

              moid: 'HaNetwork-VM Network',

              type: 'vim.Network' }

            2018-07-03T22:00:18.326Z - debug: this.networkData: { moRef: 'vim.Network:HaNetwork-VM Network',

              name: 'VM Network',

              netAddrFamily: 'IPv4',

              netMode: 'static',

              netModeString: 'static',

              netAddr: '192.168.1.12',

              netPrefix: '',

              netGateway: '192.168.1.1',

              hostName: 'vcenter.ftu.local',

              netConvertedPrefix: '255.255.255.0',

              dnsServerNames: [ '192.168.1.3' ],

              dnsServerString: '192.168.1.3',

              httpPort: '80',

              httpsPort: '443',

              networks:

               [ { name: 'VM Network',

                   moid: 'HaNetwork-VM Network',

                   type: 'vim.Network' } ] }

            2018-07-03T22:00:18.326Z - debug: targetServer: server3.ftu.local, sysName: vcenter.ftu.local, ipAddr: 192.168.1.12

            2018-07-03T22:00:18.354Z - debug: server3.ftu.local: dnsResolve result for IPv4 : [ '192.168.1.12' ]

            2018-07-03T22:00:18.354Z - error: FQDN->ip is the same as target host/server ip address

            2018-07-03T22:00:18.355Z - warn: Network Prechecks failed because:false

            2018-07-03T22:00:18.355Z - debug: checking if 192.168.1.12 exists in the network of vimConn: undefined

            2018-07-03T22:00:18.356Z - debug: isIp: 192.168.1.12: true

            2018-07-03T22:00:18.356Z - debug: getVmWithIPFQDN: hostName 192.168.1.12 is associated with [ '192.168.1.12' ]

            2018-07-03T22:00:18.415Z - debug: token:undefined, length:1, running total:1

            2018-07-03T22:00:18.416Z - debug: getVmWithIPFQDN numVms:1

            2018-07-03T22:00:18.416Z - error: No VM found with hostname 192.168.1.12

            2018-07-03T22:00:18.416Z - debug: Error in getVmWithIPFQDN: No VM found with hostname 192.168.1.12

            2018-07-03T22:00:26.384Z - debug: this.networkData: { moRef: 'vim.Network:HaNetwork-VM Network',

              name: 'VM Network',

              netAddrFamily: 'IPv4',

              netMode: 'static',

              netModeString: 'static',

              netAddr: '192.168.1.11',

              netPrefix: '',

              netGateway: '192.168.1.1',

              hostName: 'vcenter.ftu.local',

              netConvertedPrefix: '255.255.255.0',

              dnsServerNames: [ '192.168.1.3' ],

              dnsServerString: '192.168.1.3',

              httpPort: '80',

              httpsPort: '443',

              networks:

               [ { name: 'VM Network',

                   moid: 'HaNetwork-VM Network',

                   type: 'vim.Network' } ] }

            2018-07-03T22:00:26.385Z - debug: targetServer: server3.ftu.local, sysName: vcenter.ftu.local, ipAddr: 192.168.1.11

            2018-07-03T22:00:26.405Z - debug: server3.ftu.local: dnsResolve result for IPv4 : [ '192.168.1.12' ]

            2018-07-03T22:00:26.406Z - debug: checking if 192.168.1.11 exists in the network of vimConn: undefined

            2018-07-03T22:00:26.406Z - debug: isIp: 192.168.1.11: true

            2018-07-03T22:00:26.406Z - debug: getVmWithIPFQDN: hostName 192.168.1.11 is associated with [ '192.168.1.11' ]

            2018-07-03T22:00:26.462Z - debug: token:undefined, length:1, running total:1

            2018-07-03T22:00:26.463Z - debug: getVmWithIPFQDN numVms:1

            2018-07-03T22:00:26.463Z - error: No VM found with hostname 192.168.1.11

            2018-07-03T22:00:26.463Z - debug: Error in getVmWithIPFQDN: No VM found with hostname 192.168.1.11

            2018-07-03T22:00:26.463Z - info: Network Prechecks Succeededundefined

            2018-07-03T22:00:26.487Z - debug: scope.networkPrefixLabel: Subnet mask or prefix length

            2018-07-03T22:00:26.488Z - debug: Summary page: summaryTargetLabel: Target ESXi host

            2018-07-03T22:00:27.765Z - debug: sucMsg: You have successfully deployed the vCenter Server with an Embedded Platform Services Controller.

            2018-07-03T22:00:27.766Z - info: vcsaFilePath: F:\vcsa

            2018-07-03T22:00:27.767Z - debug: network prefix length: 24

            2018-07-03T22:00:27.767Z - info: <PERFORMANCE>:DEPLOYMENT_SIZE:tiny

            2018-07-03T22:00:27.767Z - debug: ovaFile retrieved: F:\vcsa\VMware-vCenter-Server-Appliance-6.7.0.12000-8832884_OVF10.ova

            2018-07-03T22:00:27.767Z - info: OVF Tool Options: --X:logFile=C:\Users\David\AppData\Local\Temp\vcsaUiInstaller\ovftool-20180703-145921793-20180703-150027767.log --X:logLevel=trivia --machineOutput --I:morefArgs --targetSSLThumbprint=C0:23:3A:EB:EB:8C:E5:2B:76:CF:BE:76:B8:07:9D:FA:43:65:86:07 --acceptAllEulas --powerOn --X:enableHiddenProperties --allowExtraConfig --X:injectOvfEnv --sourceType=OVA --name=vcenter --deploymentOption=tiny --prop:guestinfo.cis.deployment.node.type=embedded --prop:guestinfo.cis.deployment.autoconfig=False --prop:guestinfo.cis.clientlocale=en --datastore=vim.Datastore:5b39efc6-ac7e3668-ff05-ac1f6b4146fa --net:Network 1=vim.Network:HaNetwork-VM Network --prop:guestinfo.cis.appliance.net.addr.family=ipv4 --prop:guestinfo.cis.appliance.net.mode=static --diskMode=thin --prop:guestinfo.cis.appliance.net.pnid=vcenter.ftu.local --prop:guestinfo.cis.appliance.net.addr=192.168.1.11 --prop:guestinfo.cis.appliance.net.prefix=24 --prop:guestinfo.cis.appliance.net.dns.servers=192.168.1.3 --prop:guestinfo.cis.appliance.net.gateway=192.168.1.1 --prop:guestinfo.cis.appliance.net.ports={"rhttpproxy.ext.port1":"80","rhttpproxy.ext.port2":"443"} --prop:guestinfo.cis.appliance.root.passwd=CENSORED F:\vcsa\VMware-vCenter-Server-Appliance-6.7.0.12000-8832884_OVF10.ova vi://root:CENSORED@server3.ftu.local:443

            2018-07-03T22:00:27.767Z - debug: ovftoolCmd retrieved: F:\vcsa\ovftool\win32\ovftool.exe

            2018-07-03T22:00:27.992Z - info: output:MANIFEST

            + <ManifestValidate valid="true"/>

             

             

            2018-07-03T22:00:29.014Z - info: output:PROGRESS

             

            2018-07-03T22:00:34.927Z - info: output:

             

            2018-07-03T22:00:34.927Z - info: output:

             

            2018-07-03T22:00:34.928Z - info: output:ERROR

            + <Errors>

            + <Error>

            + <Type>ovftool.http.send</Type>

            + <LocalizedMsg>

            + Failed to send http data

            + </LocalizedMsg>

            + </Error>

            + </Errors>

             

             

            2018-07-03T22:00:37.040Z - info: output:RESULT

            + ERROR

             

             

            2018-07-03T22:00:37.041Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>ovftool.http.send</Type><LocalizedMsg>Failed to send http data</LocalizedMsg></Error></Errors></data>

            2018-07-03T22:00:37.041Z - error: Ovf Service:vmrefFlag: false

            2018-07-03T22:00:37.042Z - info: Cancelling timeout due to error from progress callback

            2018-07-03T22:00:37.042Z - error: Progress Controller: [VCSA ERROR] - Progress callback error

            2018-07-03T22:00:37.042Z - error: Progress Controller: [VCSA ERROR] - Details Failed to send http data

            2018-07-03T22:00:37.046Z - info: Cancelling the ping timer for session mgmt

            2018-07-03T22:00:37.046Z - info: Cancelling the ping timer for session mgmt

            2018-07-03T22:00:37.060Z - info: ovfProcess child process exited with code 1

            2018-07-03T22:00:46.304Z - info: Log file was saved at: C:\Users\David\Downloads\installer-20180703-145921793.log

            • 3. Re: Vcenter installation Failure: "Failed to send http data"
              daphnissov Guru
              vExpertCommunity Warriors

              Check your DNS and ensure you have forward *and* reverse DNS lookup for both your ESXi host and "vcenter" or the name of this vCSA. You must have DNS correct before attempting to deploy.

              • 4. Re: Vcenter installation Failure: "Failed to send http data"
                arrowhead333 Lurker

                did you ever find a solution or the cause for this issue? I have been stuck on this for the past few days.

                • 5. Re: Vcenter installation Failure: "Failed to send http data"
                  sk84 Expert
                  vExpert

                  I think there is something wrong with your network and/or dns settings.

                   

                  Look at these log entries:

                  ---

                  2018-07-03T22:00:26.385Z - debug: targetServer: server3.ftu.local, sysName: vcenter.ftu.local, ipAddr: 192.168.1.11

                  2018-07-03T22:00:26.405Z - debug: server3.ftu.local: dnsResolve result for IPv4 : [ '192.168.1.12' ]

                  2018-07-03T22:00:26.406Z - debug: checking if 192.168.1.11 exists in the network of vimConn: undefined

                  2018-07-03T22:00:26.406Z - debug: isIp: 192.168.1.11: true

                  2018-07-03T22:00:26.406Z - debug: getVmWithIPFQDN: hostName 192.168.1.11 is associated with [ '192.168.1.11' ]

                  2018-07-03T22:00:26.462Z - debug: token:undefined, length:1, running total:1

                  2018-07-03T22:00:26.463Z - debug: getVmWithIPFQDN numVms:1

                  2018-07-03T22:00:26.463Z - error: No VM found with hostname 192.168.1.11

                  2018-07-03T22:00:26.463Z - debug: Error in getVmWithIPFQDN: No VM found with hostname 192.168.1.11

                  ---

                   

                  And are you sure you want to deploy the target vCenter to the VM network? Shouldn't this be a vmkernel port with management option enabled?

                  • 6. Re: Vcenter installation Failure: "Failed to send http data"
                    AScera Novice

                    I had the same problem, I tried again and again with the same result for a day, at the end of the afternoon it worked. My scenario.

                     

                    1. A Windows_A Server with .iso for the deployment of VCSA, with IP 10.30.252.200.

                    2. Network = 10.30.252.0/24, DNS Server = 10.30.252.50. Domain FQND = delta.loc

                    3. The configuration of VCSA, IP=10.30.252.250, FQDN=vcsa01co.delta.loc

                     

                    Create the DNS record manually and validate the name resolution and everything will be fine. By I had the same error, one, two... Etc...

                     

                    How did it work?

                     

                    1. Every time I did a ping to vcsa01co.delta.loc, It resolved the IP address 10.30.252.250, but if I did ping vcsa01co it did not resolve the IP address.

                    2. Clean the cache of my DNS server.

                    3. I Waited 15 minutes.

                    4. Mount the VCSA .iso on a Windows_B Server with IP 10.30.252.201

                    5. Start the VCSA implementation and finished OK.

                     

                    I can not conclude if it was a problem with the DNS server, because I created different records for VCSA several times without results and if it was the computer from which I made the installation.

                     

                     

                    I hope will be helpful.

                     

                    Regards, RA.

                    1 person found this helpful
                    • 7. Re: Vcenter installation Failure: "Failed to send http data"
                      Robert121281 Novice

                      This issue has nothing to do with the DNS. I have tried to deploy 6.7U1 from different hosts on different hosts. It is not working at all. There is no difference using the IP or the FQDN, no difference. You can enter the data, it fails. Try again - it goes to 20% and fails. Try again with the same data, fails again. It is totally random. I did try this on fresh installed hosts, fresh laptop, VM to perform the installation on. Nothing to do with any firewall either. DNS is fine. All entries are properly set and resolve fine.

                       

                      Regards,

                      Robert

                      • 8. Re: Vcenter installation Failure: "Failed to send http data"
                        Robert121281 Novice

                        That's how the logs look for me. The issue is with the ovftool:

                         

                        -->

                        2018-12-12T08:00:32.966+01:00 trivia OVFTool[01168] [Originator@6876 sub=Default] CURL: => Sending SSL data of size 5

                        2018-12-12T08:00:32.966+01:00 trivia OVFTool[01168] [Originator@6876 sub=Default] CURL: TLSv1.2 (OUT), TLS alert, Client hello (1):

                        -->

                        2018-12-12T08:00:32.966+01:00 trivia OVFTool[01168] [Originator@6876 sub=Default] CURL: => Sending SSL data of size 2

                        2018-12-12T08:00:32.966+01:00 verbose OVFTool[03932] [Originator@6876 sub=Default] Closing image source and targets

                        2018-12-12T08:00:32.966+01:00 verbose OVFTool[03932] [Originator@6876 sub=Default] Bad return code from POST request: 404

                        2018-12-12T08:00:32.966+01:00 error OVFTool[03932] [Originator@6876 sub=Default] Error closing image-target

                        2018-12-12T08:00:32.966+01:00 error OVFTool[03932] [Originator@6876 sub=Default] Error: class boost::exception_detail::clone_impl<struct boost::exception_detail::error_info_injector<class OvfToolException> >(Bad response code (404) from POST request)

                        --> [context]zKq7AUsEAQAAAH9cjQAUT1ZGVG9vbAAAA5Yadm1hY29yZS5kbGwAAOlyBQALlQUAzRYCAUOiAW92ZnRvb2wuZXhlAAHI7gsBsIgKAYhUBQEPkwUBC4gFAch5BQH6lwUBZJsFAJakFwAnmRgAu4gbAl2qA3VjcnRiYXNlLkRMTAADyjMBa2VybmVsMzIuZGxsAATSngNudGRsbC5kbGwABKWeAw==[/context]

                        2018-12-12T08:00:32.966+01:00 verbose OVFTool[03932] [Originator@6876 sub=Default] Connection error during upload

                        2018-12-12T08:00:32.966+01:00 verbose OVFTool[04156] [Originator@6876 sub=Default] Connection error, sleep then retry (10 remaining)

                        2018-12-12T08:00:37.978+01:00 verbose OVFTool[04156] [Originator@6876 sub=Default] Exception thrown: class boost::exception_detail::clone_impl<struct boost::exception_detail::error_info_injector<class OvfToolConnectionException> >(Failed to send http data)

                        --> [context]zKq7AUsEAQAAAH9cjQATT1ZGVG9vbAAAA5Yadm1hY29yZS5kbGwAAOlyBQALlQUAzRYCAeOeCW92ZnRvb2wuZXhlAAFTngkBqLsKAaiRBQELiAUByHkFAfqXBQFkmwUAlqQXACeZGAC7iBsCXaoDdWNydGJhc2UuRExMAAPKMwFrZXJuZWwzMi5kbGwABNKeA250ZGxsLmRsbAAEpZ4D[/context]

                        2018-12-12T08:00:37.978+01:00 verbose OVFTool[04156] [Originator@6876 sub=Default] Backtrace:

                        --> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-9264255, tag: OVFTool, cpu: x86, os: windows, buildType: release

                        --> backtrace[00] vmacore.dll[0x001A9603]

                        --> backtrace[01] vmacore.dll[0x000572E9]

                        --> backtrace[02] vmacore.dll[0x0005950B]

                        --> backtrace[03] vmacore.dll[0x000216CD]

                        --> backtrace[04] ovftool.exe[0x00099EE3]

                        --> backtrace[05] ovftool.exe[0x00099E53]

                        --> backtrace[06] ovftool.exe[0x000ABBA8]

                        --> backtrace[07] ovftool.exe[0x000591A8]

                        --> backtrace[08] ovftool.exe[0x0005880B]

                        --> backtrace[09] ovftool.exe[0x000579C8]

                        --> backtrace[10] ovftool.exe[0x000597FA]

                        --> backtrace[11] ovftool.exe[0x00059B64]

                        --> backtrace[12] vmacore.dll[0x0017A496]

                        --> backtrace[13] vmacore.dll[0x00189927]

                        --> backtrace[14] vmacore.dll[0x001B88BB]

                        --> backtrace[15] ucrtbase.DLL[0x0003AA5D]

                        --> backtrace[16] kernel32.dll[0x000133CA]

                        --> backtrace[17] ntdll.dll[0x00039ED2]

                        --> backtrace[18] ntdll.dll[0x00039EA5]

                        --> [backtrace end]

                        2018-12-12T08:00:37.978+01:00 verbose OVFTool[04156] [Originator@6876 sub=Default] [Vi4Target::Abort] started.

                         

                        Anybody seen the same problem?

                         

                        Thanks,

                        Robert

                        • 9. Re: Vcenter installation Failure: "Failed to send http data"
                          daphnissov Guru
                          Community WarriorsvExpert

                          If you're having these failures, please provide some more information. For example, screenshots showing each installation step greatly help to determine what you have and are trying to do.

                          • 10. Re: Vcenter installation Failure: "Failed to send http data"
                            Robert121281 Novice

                            Thanks for your reply. I was deploying the vCSA on a NFS datastore mounted with NFS 4.1. The NFS share was provided by an Ubuntu server (nfs-kernel-server). There were problems creating the files on the NFS DS.

                             

                            2018-12-13T10:55:18.226Z info hostd[2100244] [Originator@6876 sub=DiskLib] DISKLIB-VMFS  : "/vmfs/volumes/1f1d7a8f-5ef53b0c-0000-000000000000/VMware vCenter Server Appliance (P)/VMware vCenter Server Appliance (P)-flat.vmdk" : failed to open (The file specified is not a virtual disk): Size of extent in descriptor file larger than real size. Type 3

                            2018-12-13T10:55:18.226Z info hostd[2100244] [Originator@6876 sub=DiskLib] DISKLIB-LINK  : "/vmfs/volumes/1f1d7a8f-5ef53b0c-0000-000000000000/VMware vCenter Server Appliance (P)/VMware vCenter Server Appliance (P).vmdk" : failed to open (The file specified is not a virtual disk).

                            2018-12-13T10:55:18.227Z info hostd[2100244] [Originator@6876 sub=DiskLib] DISKLIB-CHAIN : "/vmfs/volumes/1f1d7a8f-5ef53b0c-0000-000000000000/VMware vCenter Server Appliance (P)/VMware vCenter Server Appliance (P).vmdk" : failed to open (The file specified is not a virtual disk).

                            2018-12-13T10:55:18.227Z info hostd[2100244] [Originator@6876 sub=DiskLib] DISKLIB-LIB   : Failed to open '/vmfs/volumes/1f1d7a8f-5ef53b0c-0000-000000000000/VMware vCenter Server Appliance (P)/VMware vCenter Server Appliance (P).vmdk' with flags 0x8 The file specified is not a virtual disk (15).

                             

                            Deployment on another datastore was fine. I found that people have some problems with NFS 4.1, reporting similar issues when booting VMs etc. Deployment on iSCSI or NFS 3 mounted datastore is fine.

                             

                            Anybody managed to run NFS 4.1 with an Ubuntu (or other Linux) provided NFS share? Same issues I have when mounting NFS 4.1 from Debian. Share configuration is quite simple:

                             

                            /nfs *(rw,no_root_squash,async,no_subtree_check)

                             

                            Thanks,

                            Robert

                            • 11. Re: Vcenter installation Failure: "Failed to send http data"
                              RobertoMuggli Lurker

                              I had exactly the same error with exactly the same configurations as I can see in your screenshots.

                              DNS is fine, everything resolves correctly, etc.

                               

                              The solution for me was to specify the target host using its IP address instead of the FQDN.

                              The rest is identical to your example.

                               

                              Just my .02$ in case anyone else stops by

                              • 12. Re: Vcenter installation Failure: "Failed to send http data"
                                AScera Novice

                                As I mentioned before: I can not conclude nor was it a problem with the DNS server, because there are several times for VCSA several times without results and if it was the computer since the installation. However, the recommendation is to always use the installation under properly configured DNS. If you do not need it now in the future if you will need it in a larger environment.

                                 

                                Regards, RA.

                                • 13. Re: Vcenter installation Failure: "Failed to send http data"
                                  VipalGujrathi Novice

                                  Check if Port 443 is open from source to target machine

                                   

                                  I mean .. windows machine from where u r initiating deployment to ESXi host where VCSA will be deployed

                                  • 14. Re: Vcenter installation Failure: "Failed to send http data"
                                    jcperezamin Lurker

                                    I have same settings I could not install vcenter appliance and it worked out in another datastore.

                                     

                                    NFS 4.1 Debian Strecth

                                    1 2 Previous Next