On Azure and EC2 cloud instances, for example, `hostname` is not a fully
qualified name by default. The following steps are required to get EDEX to
work on such a system:
* in /etc/sysconfig/network:
HOSTNAME=miniload3.cloudapp.net
NETWORKING=yes
* in /etc/hosts
10.79.24.5 miniload3.cloudapp.net
where 10.79.24.5 is the *internal* IP address. the goal here is that from
within the server, the fully qualified domain name can be DNS resolved to
the internal IP adress, while outside the server the name is resolved to
the external IP address.
Michael James
Unidata Program Center
Boulder, CO
On Tue, Aug 26, 2014 at 12:21 PM, <admin@xxxxxxxx> wrote:
> I had to explicitly add the hostname to IP in the /etc/hosts file to fix
> this.
>
>
>
> IE
>
>
> awips2-edex 10.16.1.2
>
>
>
> That fixed that issue
>
>
>
> Ray
>
>
>
>
>
> On Tuesday, August 26, 2014 2:13pm, wxprofessor@xxxxxxxxx said:
>
>
>
>
> Be sure that hostname is defined as a fully-qualified domain name, and
> that your DNS can resolve the correct internal IP address, and that this IP
> is the one used in /awips2/edex/bin/setup.env. If not, then you can force
> the correct internal IP with an entry to /etc/hosts. Check IP address
> found with nslookup and ifconfig as well.
>
>
> please provide a sample of forcing the correct entry into /etc/hosts ...
> it is still hanging.. looking at me.. and mocking me! lol :)
>
>
>
> _______________________________________________
> awips2-users mailing list
> awips2-users@xxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership options,
> visit: http://www.unidata.ucar.edu/mailing_lists/
>
>
