This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Thanks for sending the EDEX server logs, I believe the cause of the problem has bee found. In edex-ingest-20180717.log (viewed live with the command "edex log") there are a number of the error messages below, which indicates that EDEX can not communicate with httpd-pypies. Notice the line "Caused by: java.net.UnknownHostException: external" - I believe the httpd server name (which should be localhost or the equivalent) is undefined in /awips2/edex/bin/setup.env At the top of /awips2/edex/bin/setup.env: ### EDEX localization related variables ### export AW_SITE_IDENTIFIER=OAX export EXT_ADDR=external This can be updated with the command "edex setup", which uses the env var $HOSTNAME, though should always be confirmed after a new install that EXT_ADDR is defined as the *externally resolved* host name. In short, the fix should be as easy as: edex setup edex restart and then watch "edex log" to confirm data decoding and storage. Ticket Details =================== Ticket ID: CGK-268271 Department: Support AWIPS Priority: Normal Status: Open =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.