[AWIPS #YVL-282599]: AWIPS2 dual-IP issue

Hi Scott,

This is a known issue with the edex process manager script "edex", and I've 
been trying to find a universal solution for excluding non-routeable IP 
address.  If you could copy me back the return of 'ifconfig' I can provide you 
with a temporary fix for this script tailored for your system.

Michael James
Unidata





> I'm having issues with starting 'edex' on a dual-IP server.  If I down
> one of the IP's, it reports to start up OK, however with both enabled
> I'm hitting what appears to be a (hopefully simple) parsing error.
> Unfortunately both IP's are requisite in order to provide both external
> connectivity to the world at large, AND access our vast pool of
> network-storage..
> 
> Here's what I'm seeing - node IP's are 169.154.195.56 and 10.100.98.115
> 
> [root@awips ~]edex startgrep: 10.100.98: No such file or directory[WARN]
> *** File [/awips2/data/pg_hba.conf] contains incorrect IP addresses
> Run setup now? [y/n]
> 
> I can re-run setup but it fixes nothing - probably because of a `sed`
> txt parsing error somewhere in AWIPS
> 
> Run setup now? [y/n]y[edex] EDEX IP and Hostname Setupgrep: 10.100.98:
> No such file or directory Checking /awips2/data/pg_hba.conf      **
> Missing 169.154.195.56 10.100.98 Checking /awips2/edex/bin/setup.env
> [OK] Checking /usr/local/ldm/etc/ldmd.conf [OK]sed: -e expression #1,
> char 30: unterminated `s' command[edit] 169.154.195.56 10.100.98.0 added
> to       File backed up to
> /awips2/data/pg_hba.conf.setup_20150513172754[done]
> 
> Even if I manually add the correct values(i.e. both IP's in CIDR
> format) to pg_hba.conf, the edex checker will still detect errors in
> pg_hba.conf due to the parse error, and refuse to start.
> 
> Any guidance?  edex CAN be started via bringing one of the network
> interfaces down, but that's far from desirable...
> 
> 
> 
> 
> 
> 


Ticket Details
===================
Ticket ID: YVL-282599
Department: Support AWIPS
Priority: Normal
Status: Open