Horizon Workspace: installation wizard fails with ...

ydacentec · ‎03-21-2013

Hi all

I have deployed the OVA file for Horizon Workspace via the vSphere Client.
I started then the console of configurator-va.
I answered the questions in the Horizon Workspace Installation Wizard inside the console.
The wizard starts starting the other deployed VMs.
Then the wizards exits with following error:

Configuring ssh for VMs

Runtime error!

ssh failed: scp failed.

success

Failed to configure VMs in the vApp. Contact VMware support.

Exit code: 1

You will need to redeploy the Application

Screenshot in attachment.

Has anyone a suggestion what could have gone wrong? Where can I find any log file?

Kind regards

Yannick

ydacentec · ‎03-21-2013

Some additional info:

I booted configurator-va via an Ubuntu life cd to get some logging for its disk (I mounted the disk).

In opt/vmware/var/log/configurator.log, there was no more information as I had on the output of my screen.
Grepping for ssh in opt/vmware/var/log resulted in no additional files
Grepping for ssh in var/log resulted in following:

ubuntu@ubuntu:/mnt/hd$ sudo grep -ri ssh var/log

(...)

var/log/warn:Mar 21 15:09:47 localhost sshd[5490]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
var/log/warn:Mar 21 15:09:47 localhost sshd[5490]: error: Bind to port 22 on :: failed: Address already in use.
var/log/warn:Mar 21 15:09:47 localhost sshd[5490]: fatal: Cannot bind any address.

Maybe this can help someone to have a clue why the install is failing?

Kind regards

Yannick

pbjork · ‎03-21-2013

I see a lot of localhost.localdom in your screen shot. This indicates an issue with your DNS setup. Can you make sure you have proper DNS records for all your appliances and corresponding PTR records?

sravuri · ‎03-21-2013

It looks like vcenter is returning the hostname for those VMs as localhost.localdom.

Please check your networking configuration.

ydacentec · ‎03-22-2013

Thanks for the hints.

At the start of the wizard, all the DNS (reverse) lookups were checked by the wizard and they were correct:

Now, I am still in the live cd on the configurator-va VM, and DNS (reverse) lookup works as expected:

ubuntu@ubuntu:~$ for fqdn in `cat fqdn`; do host $fqdn; done
horizon-esxi.daas.com has address 172.19.12.111
horizon-vcenter.daas.com has address 172.19.12.112
horizon-gateway.daas.com has address 172.19.12.113
horizon-configurator-va.daas.com has address 172.19.12.114
horizon-service-va.daas.com has address 172.19.12.115
horizon-connector-va.daas.com has address 172.19.12.116
horizon-data-va.daas.com has address 172.19.12.117

ubuntu@ubuntu:~$ for ip in `cat ips`; do host $ip; done
111.12.19.172.in-addr.arpa domain name pointer horizon-esxi.daas.com.
112.12.19.172.in-addr.arpa domain name pointer horizon-vcenter.daas.com.
113.12.19.172.in-addr.arpa domain name pointer horizon-gateway.daas.com.
114.12.19.172.in-addr.arpa domain name pointer horizon-configurator-va.daas.com.
115.12.19.172.in-addr.arpa domain name pointer horizon-service-va.daas.com.
116.12.19.172.in-addr.arpa domain name pointer horizon-connector-va.daas.com.
117.12.19.172.in-addr.arpa domain name pointer horizon-data-va.daas.com.

The networking is rather straight forward:

Networking on ESXi node:

IP pool on Datacenter

Has anyone hints on which other aspect of the networking it could have gone wrong?

tjb627 · ‎03-22-2013

I've tried 2 or 3 times to deploy Horizon Workspace and I get the same error. All the DNS lookups complete succesfully, I answer all questions in the wizard and then I eventually get the "Failed to configure VMs in the vApp. Contact VMware Support" message. If you figure this issue out please share.

tjb627 · ‎03-23-2013

I figured out my problem. I was missing the DNS Search Path entry on my IP Pool. After adding that and redeploying the OVF the configurator was able to finish it's wizard.

ydacentec · ‎03-25-2013

I am not that lucky. I tried following DSN IP-pool configurations:

IPv4 DNS Servers (172.19.0.1)
IPv4 DNS Servers (172.19.0.1), DNS Domain (daas.com)
IPv4 DNS Servers (172.19.0.1), DNS Search Path (daas.com)
IPv4 DNS Servers (172.19.0.1), DNS Domain (daas.com), DNS Search Path (daas.com)

Unfortunately, none of them worked (always the same ssh error).

ToWka · ‎04-15-2013

Try to search old horizon VM's in your vSphere infrastructure and delete them.

LeeUSMC88 · ‎09-09-2013

Did you find a resolution?

admin · ‎09-09-2013

Unfortunately not yet...

MvanZutphen · ‎09-10-2013

I have the same problem, did you find a resolution?

Tvirtual4 · ‎09-10-2013

I was getting the same error. What worked for me was to use a complex password with special characters for the password used for VMs. Another tip is to make a snapshot of the configurator-va and all other -va VMs prior to running the configuratar-va setup from the console and if it bombs just revert all to previous snapshot and try again.

LeeUSMC88 · ‎09-10-2013

I believe it is different between the two versions - 1.0 It normally comes down to the dormant extensions or password complexity. 1.5 had an issue with the installer, they are putting out a new download this week.

MvanZutphen · ‎09-12-2013

The new installer is online (horizon-workspace-1.5.0-1318295.ova) and the horizon workspace installer is working now for me

mcmcomput · ‎10-16-2013

BTW... This issue is resolved in the latest releases, however there is a KB article on a workaround. VMware KB: Installing VMware Horizon Workspace 1.5.0 Build 1220937 fails with the error: WARNING: Yo...

jsb197 · ‎01-16-2014

Is there anyone that has a resolution to this? Tried everything in all posts, all combinations of DNS imaginable, with no luck, same error in the original post. DNS resolutions work normal, all records in place and resolvable, vapp deploys, but initial configuration dies with the same ssh/scp , runtime error. Removed all old extensions from vcenter as well after each failure. I'm at a loss on this one.

I have made it further at times when changing the DNS search path in the IP pool to another domain in our DNS, both matching the DNS name used for the vapp VM's and not matching, but eventually still fails during initial configuration no matter how I mix it up.

Tried complex passwords, simple ones, etc. Nothing changes.

sravuri · ‎01-19-2014

Can you confirm the build number you are using, please?

Also, a webex may help. Can you send me a private message to let me know what time works?

joernmeyer · ‎03-01-2014

There is an error in the 1220937 Build

To work around this issue, remove the expiration from the password.

To remove the expiration from the password, perform these steps:

Note: Perform the steps after deploying the OVA and before you run the Command-Line Interface on configurator-va.

Power on the vApp. Note that the Configurator-va is powered on.
Power on the other virtual appliances (VAs).
On each VA except the Configurator-va, log in as root on the console.

Note: The default password is vmware.
Verify that the password has expired by running the command:

chage -l configurator

Note: The Password Expires value displays a date in the past.
Remove the expiration date using the command:

chage -M -1 configurator
To confirm that the password no longer has an expiration date, run the command:

chage -l configurator

You see the output:

Password Expires: Never
Shut down all of the VAs except the Configurator-va.
You can now use the Command-Line Interface on the Configurator-va.

VMware KB: Installing VMware Horizon Workspace 1.5.0 or deploying a new VMware Horizon Workspace Dat...

All

Horizon Workspace: installation wizard fails with SSH error