vCloud Director: error preparing hosts

[bluemax00x]

Hi all,

I have installed successfully vCloud director following indications from Yellowbricks (great blog!!)

I have reproduced the whole virtual environment on an ESX4.0, with 2 vESX4.1.

After creating the provider  vCD  I get to prepare the hosts and I get an error message:

Error occurred executing agent script "/opt/vmware/cloud-director/agent/vslad-install-esx41-1.0.0.67.bin" on host "esx1.cloud.net".

- Read timed out

which I think correspond to this section of the vcloud-container-debug.log on vCD:

Caused by: java.net.SocketTimeoutException: Read timed out

        at java.net.SocketInputStream.socketRead0(Native Method)

        at java.net.SocketInputStream.read(SocketInputStream.java:129)

        at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)

        at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)

        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)

        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:746)

        at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)

        at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:130)

        at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:127)

        at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:233)

        at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)

        at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:210)

        at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:271)

        at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:227)

        at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:209)

        at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:292)

        at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:126)

        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:483)

        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)

        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)

        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554)

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:93)

        ... 3 more

The vlsad agent get installed correctly but the host preparation fails anyway.

I have manually uninstalled vlsad agents on the vESX hosts and tried few times but I get the same error.

I am getting close to the trial expiration date and I really would like to have the chance to play with vCD.

Any hint really appreciated.

Kind Regards,

[tsugliani]

Hi,

Did you try to check on your ESXi hosts the logs in this directory : /var/log/vmware/vslad ?

How much memory does your virtualized ESXi have ? (try increasing total memory allocated to your ESXi VM)

Regards,

[bluemax00x]

HI thanks for your reply.

I have increased the hypervisors RAM from 2 Gb to 3 Gb. but I get the same error.

As for the log the exit code is 63, which is the good one, according to the installation .bin script:

[root@esx2 vslad]# tail installer.log

2010-12-27 15:32:12:       checking for size greater than 102400

2010-12-27 15:32:12:       no need to rotate yet

2010-12-27 15:32:12:    leaving  rotate_log()

2010-12-27 15:32:12:    entering unlock_installer()

2010-12-27 15:32:13|0f2b35:    leaving  unlock_installer()

2010-12-27 15:32:13|0f2b35:    entering status()

2010-12-27 15:32:14|0f2b35:       info:status_done:done

2010-12-27 15:32:14|0f2b35:    leaving  status()

2010-12-27 15:32:14|0f2b35:    exit code 63

2010-12-27 15:32:15|0f2b35: leaving  shutdown()

My understanding is that the installation of the agent completes successfully and the agent gets started no problem.

There is some post installation operation that the cell is trying to perform but I can't find that... :smileyconfused:

I also tried to disable the firewall, but no luck.

[admin]

The SocketTimeoutException suggests that there were network I/O problems at the time when it was attempting to prepare the hosts.  It could be the network itself or the TCP/IP stack on either side.  Have you experienced any other networking problems when interacting with that ESX host or problems between the vCloud cell machine and the ESX hosts?

[bluemax00x]

Hi, the network response is not great but the lab consists of:2 ESX4.1 virtulalized on top of a single ESX4.0 so everything  gets switched in memory of the physical  hypervisor, a Dell optiplex 740, with 8gb RAM , AMD athlon dual core 2Ghz. I am running on it strictly only the VMs needed for the lab (vcd, vsm, the 2 esx4.1 and vc4.1).

I wonder if there is a manual procedure I can use to prepare the hosts directly, instead of having the cell doing it.

rgds,

[virtualportal]

Hi,

I had some issues previously with Hosts and the vslad agent. Turned out It was a bug and there was some issue with the vCenter database storing some info about that host.

I documented the work around here, It includes removing the Hosts from vCenter and re-adding. This may help in your situation too?

http://virtual-portal.com/virtualportal/?p=291

Steven Bryen

[ealaqqad]

You could as well trying removing the old vCloud Agent and add it again and see if that help. Check out my following post for instructions:

Manually installing the vCloud Director Agent on ESXi 5 / vSphere 5

I hope this help,

Eiad Al-Aqqad

B: http://www.VirtualizationTeam.com

B: http://www.TSMGuru.com