[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AWIPS #SGX-641557]: EDEX b18.1.2-3 ingest failing to run with default configuration

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.

  • Subject: [AWIPS #SGX-641557]: EDEX b18.1.2-3 ingest failing to run with default configuration
  • Date: Wed, 05 Jan 2022 09:26:32 -0600
 >Just realized the recursion error is because I unzipped a .jar. Whoops.

If the jar is zipped and the unzipped contents are removed, do you still get 
EDEX ingest fail to start? 

Have you installed this on a new Centos7 machine then or one that previously 
had an AWIPS version? I'm wondering if there is a dependency that AWIPS doesn't 
install, but is needed and was on your previous build? Can you list all of your 
rpm's installed and we can cross-reference that with our machines? 

Typically, you should switch users to the awips user by

su - awips 

to switch to the awips user evironment variables (instead of su awips). Can you 
try that before a sudo edex start as the awips user?


Thanks,

Tiffany Meyer
AWIPS Lead Software Engineer
UCAR-Unidata

If you're interested, please feel free to fill out a survey about the support 
you receive:  
https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform

Ticket Details
===================
Ticket ID: SGX-641557
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.