[AWIPS #BTQ-912768]: awips password

> I'm still feeling my way around with EDEX, but I couldn't find any reference 
> to this issue except a closed thread on github that you logged without a 
> solution.  I'm seeing messages like the following when I watch the edex log 
> (still not exactly sure where, if anywhere, the log file is stored):
> INFO  2016-08-27 18:05:36,304 [dhrProcess-1] MainMethod: EDEX - 
> /awips2/edex/bin
> 
> ERROR 2016-08-27 18:05:36,305 [dhrProcess-1] MainMethod: EDEX - Password:
> psql: FATAL:  password authentication failed for user "awips"
> Password:
> If I set a password for user awips during the install, I failed to write it 
> down or remember it.  How do I go about fixing this?


This is actually a big red herring, it's the Hydro apps DHR and DPA gather 
scripts which are running, but they are unable to processed these level3 NIDS 
products.  There is no consequence to this other than log files fill up with 
these messages.  This is safe to ignore, and in the upcoming 16.2.2 release 
this has been resolved by new Data Distribution Files.

> 
> Also, I have been working on adding "traditional" LDM actions to save data 
> for gempak and IDV.  So far, I have only set up actions that file data (i.e., 
> no gempak decoders, as I haven't yet installed gempak).  I seem to remember 
> that user gempak and user ldm were supposed to be in the same group.  Is that 
> still the case?  Should gempak be in group awips or fxalpha or does it not 
> matter?


Typically we have users gempak and ldm in the "ustaff" group, but I do not 
think sharing a group is required. The GEMPAK programs and tables can be read 
by the ldm user fine without. 

Michael James
Unidata Program Center
Boulder, CO

Ticket Details
===================
Ticket ID: BTQ-912768
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.