config_wizard timeout more than 3600s

[p.hruby]

I'm trying to install APIC-EM for testing purposes on ESXi with slow disk. The installation fails because it takes longer time than 3600s.

Is there a way how configure (hack,...) longer timeout?

Petr

[cchitnis]

If you are installing 1.3.0.4383, here're the requirements from ESXI host:

Server Image Format	ISO
VMware ESXi Version	5.1/5.5/6.0
Virtual CPU (vCPU)	Minimum Required: 6, Recommend: 12
CPU (speed)	2.4 GHz
Memory	64 GB [ For a multi-host deployment (2 or 3 hosts) only 32GB of RAM is required for each host. ]
Disk Capacity	500 GB
Disk I/O Speed	200 MBps

[aradford]

you can get away with slower disk for testing purposes, but there are limits.

Most important is to have enough RAM/cpus otherwise it will never get started.

what is your disk throughput?

what RAM/CPU have you configured?

[p.hruby]

Slow disk is the only weekness of my setup. I have 64GB of RAM and 8 CPUs.

I think that I obtained number 50 during disk performance test. I was able

to install v 1.1 after several attempts. But installation of versions 1.2

and 1.3 ends always with timeout of 3600 s.

[arikgelman]

How much disk space the server have? I had the same problem when I had less than 500GB.

[p.hruby]

I allocated exactly 500GB. I think that disk performace is the only problem

in my case.

[aradford]

Can you confirm where there process fails please?  Is the controller growing services when the timeout occurs?

[p.hruby]

Yes, the controller is growing services. But timeout is reached after 21 of

37 services are successfuly grown.

[p.hruby · Accepted solution]

It looks like my problem was caused not only by disk performance but also

by CPU resources. As soon as I configured 16 CPUs my installation was

successful (on 3rd attempt ..)

>