Cluster Installation Wizard - Step "database setup" - failed test-connections

Hi Stefan,

Please provide the hostname of the CM server in the "Database-Hostname"
textbox. The entry should look like "hostname:7432" instead of just
":7432".

CM tries to fill it automatically by getting hostname where it is running,
but that seems to be returning empty for your case.

Vikas

Hi Stefan,

Also check that your /etc/cloudera-scm-server/db.mgmt.properties looks
correct. There is a bug where this file is sometimes generated with empty
host names, usually when you are on a VPN connecting to AWS and start the
embedded db for the first time. We can't correctly resolve the host name
when on a VPN sometimes.

If the db.mgmt.properties file is missing the host names, then fix it by
adding the fully qualified domain name for your host. Don't use
"localhost". Reboot your scm server (sudo service clouders-scm-server
restart) and it should work correctly.

Thanks,
Darren

Thank you to all of you for your replies.

I added the SCM hostname to /etc/cloudera-scm-server/db.mgmt.properties,
restarted the SCM server and started building the cluster from tzhe
beginning. It worked.


problem solved.

btw, I have no VPN, no AWS. It was a clean install on 5 identical CentOS
6.4 servers.