VMware Cloud Community
vogrand
Contributor
Contributor
‎06-28-2019 01:26 PM

VCSA 6.7 fresh installation not working correctly

Hi

I'm very new to vmware, installed 3x nucs with 3xESXI hosts 6.7

Want Vcenter so installed VCSA 6.7 release but i'm not allowed to https://x.x.x.x:5480

It gives me errors when using a web browser. The connection is interupted according to the web browser.

I've created a DNS zone and the A-record works

reverse zone is created and works

I can SSH to the device, I can ping it etc etc.

Now, the installer gives error during the phase 2 of the VCSA installation and this it the logs

2019-06-28T12:08:38.889Z - info: ******cvLog END******

2019-06-28T12:08:38.889Z - debug: cvLog got ipv4 line:DEFAULT_IPV4: 10.255.2.11, guestIpv4Set: 10.255.2.11

2019-06-28T12:08:38.889Z - debug: cvLog got ipv6 line:DEFAULT_IPV6:, guestIpv6Set: null

2019-06-28T12:08:38.889Z - debug: cvLog got hostname line:Host name has been set to vcsa01.adab.local, guestHostnameSet: vcsa01.adab.local

2019-06-28T12:08:38.889Z - info: cvLog got startLine:2019-06-28T20:04:38.263Z: Doing initial package configuration ...

2019-06-28T12:08:38.889Z - info: cvLog got endLine:2019-06-28T20:06:09.113Z: Initial RPM install done.

2019-06-28T12:08:38.889Z - info: guestNetMode: static, guestNetFamily: IPv4, guestIp: 10.255.2.11, guestIpv4Set: 10.255.2.11, guestIpv6Set: null, guestHostnameSet: vcsa01.adab.local

2019-06-28T12:08:38.890Z - info: <PERFORMANCE>:RPM_INSTALL:90:seconds

2019-06-28T12:08:38.894Z - info: cloudvm log file: C:\Users\anders\AppData\Local\Temp\vcsaUiInstaller\cloudvm-20190628-140146261-20190628-140258750.log

2019-06-28T12:08:38.894Z - info: Final host name: 10.255.2.11

2019-06-28T12:08:38.894Z - info: vamiBaseUrl was set to: https://10.255.2.11:5480/

2019-06-28T12:08:38.897Z - debug: isResolvedTo: fqdn: vcsa01.adab.local, ip: 10.255.2.11

2019-06-28T12:08:38.897Z - info: VAMI_CONN_MAX_TRY: 25

2019-06-28T12:08:38.918Z - error: Could not get response for get request from url https://vcsa01.adab.local:5480/: Error: read ECONNRESET

2019-06-28T12:08:38.918Z - error: VAMI is NOT accessilbe[1]: https://vcsa01.adab.local:5480/, err: Could not get response for get request from url http

.....

2019-06-28T12:08:39.134Z - error: Could not get response for get request from url https://vcsa01.adab.local:5480/: Error: read ECONNRESET

2019-06-28T12:08:39.134Z - error: VAMI is NOT accessilbe[24]: https://vcsa01.adab.local:5480/, err: Could not get response for get request from url https://vcsa01.adab.local:5480/: Error: read ECONNRESET

2019-06-28T12:08:39.143Z - error: Could not get response for get request from url https://vcsa01.adab.local:5480/: Error: read ECONNRESET

2019-06-28T12:08:39.144Z - error: VAMI is NOT accessilbe[25]: https://vcsa01.adab.local:5480/, err: Could not get response for get request from url https://vcsa01.adab.local:5480/: Error: read ECONNRESET

2019-06-28T12:08:39.160Z - info: Cancelling the ping timer for session mgmt

2019-06-28T12:08:43.638Z - error: Request timed out after 30000 ms, url: https://nuc01.adab.local:443/guestFile?id=6&token=52822988-8e6d-93c9-069b-8b77e6220e296

2019-06-28T12:08:53.666Z - error: Request timed out after 30000 ms, url: https://nuc01.adab.local:443/guestFile?id=6&token=5285b312-caa6-5b50-7580-54957cc894756

2019-06-28T12:09:03.669Z - error: Request timed out after 30000 ms, url: https://nuc01.adab.local:443/guestFile?id=6&token=5207dff2-e30d-4339-6b20-ff7d215c4dd26

2019-06-28T12:09:08.888Z - error: Request timed out after 30000 ms, url: https://nuc01.adab.local:443/guestFile?id=6&token=527c50b6-b4ab-3def-a235-e63dc177e4f76

2019-06-28T12:09:08.916Z - error: Request timed out after 30000 ms, url: https://vcsa01.adab.local:5480/

2019-06-28T12:09:08.930Z - error: Request timed out after 30000 ms, url: https://vcsa01.adab.local:5480/

2019-06-28T12:09:08.941Z - error: Request timed out after 30000 ms, url: https://vcsa01.adab.local:5480/

2019-06-28T12:09:08.948Z - error: Request timed out after 30000 ms, url: https://vcsa01.adab.local:5480/

2019-06-28T12:09:08.965Z - error: Request timed out after 30000 ms, url: https://vcsa01.adab.local:5480/

2019-06-28T12:09:08.965Z - error: Request timed out after 30000 ms, url: https://vcsa01.adab.local:5480/

2019-06-28T12:09:08.977Z - error: Request timed out after 30000 ms, url: https://vcsa01.adab.local:5480/

I've probably deleted & recreated the vcsa appliance 10++ times with the same issue and need some pointers..

Is it the NUC01 that fails the installation? What can I do? Something I'm missing here?

Tags (1)
0 Kudos
7 Replies
krisjinka
Contributor
Contributor
‎04-06-2020 08:13 AM

Hello, I am trying to deploy vCenter Server Appliance on the ESXi 6.7 Host as a VM. After completing the stage 1, stage 2 goes into error.

The installer log shows the following errors:

2020-04-03T06:37:03.353Z - info: ******cvLog END******

2020-04-03T06:37:03.353Z - info: cvLog got startLine:2020-04-03T06:34:12.663Z: Doing initial package configuration ...

2020-04-03T06:37:03.353Z - info: cvLog got endLine:2020-04-03T06:36:49.305Z: Initial RPM install done.

2020-04-03T06:37:03.354Z - info: guestNetMode: static, guestNetFamily: IPv4, guestIp: 10.251.205.5, guestIpv4Set: null, guestIpv6Set: null, guestHostnameSet: null

2020-04-03T06:37:03.354Z - warn: Neither ipv4 nor ipv6 is set in the cloudvm

2020-04-03T06:37:03.354Z - info: <PERFORMANCE>:RPM_INSTALL:156:seconds

2020-04-03T06:37:03.355Z - info: cloudvm log file: C:\Users\USER_NAME\AppData\Local\Temp\vcsaUiInstaller\cloudvm-20200403-152841143-20200403-153108896.log

2020-04-03T06:37:03.355Z - info: Final host name: 10.251.205.5

2020-04-03T06:37:03.355Z - info: vamiBaseUrl was set to: https://10.251.205.5:5480/

2020-04-03T06:37:03.355Z - info: VAMI_CONN_MAX_TRY: 25

2020-04-03T06:37:08.189Z - error: Request timed out after 30000 ms, url: https://10.251.205.18:443/guestFile?id=2&token=522bee2b-247e-2338-858a-0db98bd4a6dc2

2020-04-03T06:37:18.147Z - error: Request timed out after 30000 ms, url: https://10.251.205.18:443/guestFile?id=2&token=529522fc-4d64-9d6e-b97c-18851e4d80512

2020-04-03T06:37:24.358Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:37:24.358Z - error: VAMI is NOT accessilbe[1]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:37:28.151Z - error: Request timed out after 30000 ms, url: https://10.251.205.18:443/guestFile?id=2&token=52749e42-e458-d175-8fd9-9337c1032d232

2020-04-03T06:37:33.352Z - error: Request timed out after 30000 ms, url: https://10.251.205.18:443/guestFile?id=2&token=52415f75-76a5-fdaf-b407-487912e2d7a22

2020-04-03T06:37:45.362Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:37:45.362Z - error: VAMI is NOT accessilbe[2]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:38:06.364Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:38:06.364Z - error: VAMI is NOT accessilbe[3]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:38:27.368Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:38:27.368Z - error: VAMI is NOT accessilbe[4]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:38:48.370Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:38:48.371Z - error: VAMI is NOT accessilbe[5]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:39:09.379Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:39:09.379Z - error: VAMI is NOT accessilbe[6]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:39:30.384Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:39:30.384Z - error: VAMI is NOT accessilbe[7]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:39:43.074Z - debug: Updated current session with lstActTm Fri Apr 03 2020 15:39:38 GMT+0900 (Korea Standard Time)

2020-04-03T06:39:51.387Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:39:51.387Z - error: VAMI is NOT accessilbe[8]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:40:12.389Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:40:12.389Z - error: VAMI is NOT accessilbe[9]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:40:33.393Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:40:33.393Z - error: VAMI is NOT accessilbe[10]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:40:54.394Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:40:54.394Z - error: VAMI is NOT accessilbe[11]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:41:15.399Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:41:15.399Z - error: VAMI is NOT accessilbe[12]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:41:36.402Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:41:36.402Z - error: VAMI is NOT accessilbe[13]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:41:57.408Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:41:57.408Z - error: VAMI is NOT accessilbe[14]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:42:18.409Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:42:18.410Z - error: VAMI is NOT accessilbe[15]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:42:39.412Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:42:39.413Z - error: VAMI is NOT accessilbe[16]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:43:00.416Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:43:00.416Z - error: VAMI is NOT accessilbe[17]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:43:21.419Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:43:21.419Z - error: VAMI is NOT accessilbe[18]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:43:42.422Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:43:42.423Z - error: VAMI is NOT accessilbe[19]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:44:03.428Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:44:03.428Z - error: VAMI is NOT accessilbe[20]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:44:24.431Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:44:24.431Z - error: VAMI is NOT accessilbe[21]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:44:43.076Z - debug: Updated current session with lstActTm Fri Apr 03 2020 15:44:38 GMT+0900 (Korea Standard Time)

2020-04-03T06:44:45.434Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:44:45.434Z - error: VAMI is NOT accessilbe[22]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:45:06.438Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:45:06.438Z - error: VAMI is NOT accessilbe[23]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:45:27.443Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:45:27.443Z - error: VAMI is NOT accessilbe[24]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:45:48.448Z - error: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:45:48.448Z - error: VAMI is NOT accessilbe[25]: https://10.251.205.5:5480/, err: Could not get response for get request from url https://10.251.205.5:5480/: Error: connect ETIMEDOUT 10.251.205.5:5480

2020-04-03T06:45:48.453Z - info: Cancelling the ping timer for session mgmt

I have tried many times, and allways , the installation is stopped after stage 1. Can someone tell me what i am missing ?

0 Kudos
bigbrig
Contributor
Contributor
‎12-18-2022 12:51 AM

Hi. I am experiencing the same error when trying to install recently. Did you ever figure out a solution?

0 Kudos
maksym007
Expert
Expert
‎12-18-2022 04:11 PM

Which vCenter build are you trying to install? 

0 Kudos
bigbrig
Contributor
Contributor
‎01-17-2023 08:08 PM

It was vCenter 7.0.

0 Kudos
compdigit44
Enthusiast
Enthusiast
‎01-18-2023 12:54 PM

can you ping the vcsa name or IP? 

0 Kudos
bigbrig
Contributor
Contributor
‎01-18-2023 02:54 PM

Yes

0 Kudos
bigbrig
Contributor
Contributor
‎02-08-2023 10:18 AM

Hi - just wanted to follow up on this and say check your firewall rules. Mine was blocking these requests as it was SSL on a non-standard port (5480). After the rule was modified these errors went away. Also make sure your DNS lookups forwards and backwards work exactly, and return the right results for your VCSA server A and PTR records. 

0 Kudos