The orchestration script will check for a properly configured hostname.
WARNING : Unable to resolve hostname. Hostfile (such as /etc/hosts), or DNS are not configured properly. To enable Endeca Server host name resolution, the IP address of the host machine should not map to the phrase 'localhost'. Instead, it should be mapped to the Fully Qualified Domain Name (FQDN), or the first portion of this name. For example, these mappings ensure host name resolution for the Endeca Server: 123.0.0.1 jdoe.acme.com, or 123.0.0.1 jdoe. This mapping is not valid: 123.0.0.1 localhost.
Because the message is only a warning, the orchestration script will continue to run. However, the warning may indicate problems with later starting Endeca Server. You, therefore, should check that the /etc/hosts file includes a mapping from the site-local IP address to FQDN, or the first portion of the correct, Fully Qualified Domain Name. If /etc/hosts includes a mapping to localhost, it should not be the only entry, or the first entry in this file. Do not use any other OS-specific methods for determining the hostname—only use the configuration in /etc/hosts. This is because the mappings in /etc/hosts always override the mappings from DNS (even if they are present), and Endeca Server relies on /etc/hosts.
For further details, see the "Hostname resolution in the Endeca Server" topic in Chapter 2 of the Oracle Endeca Server Administrator's Guide.