vRO 7.3.1 always show service unavailable

[panjl3]

I deployed the latest release 7.3.1, but it always show service unavailable when I access the web page via IP.

I typed http://10.240.198.176 and it redirected to http://10.240.198.176/vco/

I also tried https://10.240.198.176:8281/vco, also the same:

https://10.240.198.176:5480(Appliance configuration apge) and control-center is ok to access.  So I tried rebooted the appliance via Appliance configuration page, but did not solve the issue.

I also waited about one day, but the server was still not initialized.

I re-deployed a new one, the phenomenon was the same.

vRO 7.3.0 did not has the issue. Something I missed? Need help!!!  Thank you.

[iiliev]

This error means the vRO server hasn't started properly for some reason. To troubleshoot it, the first thing is to check vRO logs (under /var/log/vco/app-server/ folder); there should be some errors/exceptions/messages pointing to the problem.

[panjl3]

Thank you Ilian Iliev. Solved by log into the appliance console, and run /opt/vmware/share/vami/vami_config_net to set host name of the appliance to "localhost". Or manually edit /etc/hosts to add 127.0.0.1 localhost.localdomain.  We use dhcp. In previous vRO, the default host name after deployment of the appliance was localhost.localdom and /etc/hosts contained this entry. In vRO 7.3.1, the default changed to localhost.localdomain  but the /etc/hosts doesn't has this entry, so can not resolve localhost.localcomain and throw "unkonwn host" exception in log.

Post the solution here in case others may encounter it. And report this potential issue to you so you can check.

[daphnissov]

You need to use a proper hostname that you define when deploying the appliance. All systems need a real name with DNS entries to match, and not having that creates problems.

[g0rbi]

for me after doing vm hw compatibility upgrade from v13 to v18 this one helped:

https://kb.vmware.com/s/article/76870