[AWIPS #WDS-351489]: New Support Case

>LDM has not been configured yet, so no worries there.
>Postgres initialization appears to be the issue.
>
>Restarting EDEX.....
>
>[root@metbox5 ~]# edex stop
>
>Stopping EDEX Camel (ingest):
>
>Stopping EDEX Camel (ingestGrib):
>
>Stopping EDEX Camel (request):
>
>EDEX ingest shutdown
>
>EDEX request shutdown
>
>EDEX ingestGrib shutdown
>
>Stopping edex_ldm (via systemctl): [ OK ]
>
>Stopping qpidd (via systemctl): [ OK ]
>
>Stopping httpd-pypies (via systemctl):
>
>Session terminated, killing shell... ...killed.
>
>Stopping edex_postgres (via systemctl): [ OK ]
>
>[edex status]
>
>postgres :: not running
>
>pypies :: not running
>
>qpid :: not running
>
>EDEXingest :: not running
>
>EDEXgrib :: not running
>
>EDEXrequest :: not running
>
>ldmadmin :: not running
>
>[root@metbox5 ~]# edex start
>
>Starting edex_postgres (via systemctl): [ OK ]
>
>Starting httpd-pypies (via systemctl): [ OK ]
>
>Starting qpidd (via systemctl): [ OK ]
>
>Starting EDEX Camel (ingest):
>
>Starting EDEX Camel (ingestGrib):
>
>Starting EDEX Camel (request):
>
>EDEX Camel (request) is running (wrapper PID 23394)
>
>EDEX Camel (request) is running (java PID 23692)
>
>EDEX Camel (ingestGrib) is running (wrapper PID 23399)
>
>EDEX Camel (ingestGrib) is running (java PID 24108)
>
>EDEX Camel (ingest) is running (wrapper PID 23395)
>
>EDEX Camel (ingest) is running (java PID 23894)
>
>Starting edex_ldm (via systemctl): [ OK ]
>
>
>EDEX Status after the restart...same
>
>[root@metbox5 ~]# edex
>
>[edex status]
>
>postgres :: not running
>
>pypies :: running :: pid 22519
>
>qpid :: running :: pid 22597
>
>EDEXingest :: running :: pid 23894 24845
>
>EDEXgrib :: running :: pid 24108 24854
>
>EDEXrequest :: running :: pid 23692 24862
>
>ldmadmin :: not running
>
>Looking at the status of edex_postgres....
>
>[root@metbox5 ~]# systemctl status edex_postgres
>? edex_postgres.service - SYSV: PostgreSQL database, which is the instance 
>used by AWIPS EDEX.
>
>Loaded: loaded (/etc/rc.d/init.d/edex_postgres; bad; vendor preset: disabled)
>
>Active: active (exited) since Wed 2021-06-30 15:40:26 EDT; 3min 6s ago
>
>Docs: man:systemd-sysv-generator(8)
>
>Process: 22217 ExecStop=/etc/rc.d/init.d/edex_postgres stop (code=exited, 
>status=0/SUCCESS)
>
>Process: 22425 ExecStart=/etc/rc.d/init.d/edex_postgres start (code=exited, 
>status=0/SUCCESS)
>
>Tasks: 0
>
>Jun 30 15:40:26 metbox5 systemd[1]: Starting SYSV: PostgreSQL database, which 
>is the instance used by AWIPS EDEX....
>
>Jun 30 15:40:26 metbox5 edex_postgres[22425]: /etc/rc.d/init.d/edex_postgres: 
>line 19: [: =: unary operator expected
>
>Jun 30 15:40:26 metbox5 su[22430]: (to awips) root on none
>
>Jun 30 15:40:26 metbox5 edex_postgres[22425]: Starting EDEX PostgreSQL:
>
>Jun 30 15:40:26 metbox5 systemd[1]: Started SYSV: PostgreSQL database, which 
>is the instance used by AWIPS EDEX..
>



Hello,

Can you look at the postgres logs for possibly some more information? First 
look at /awips2/data/serverlog - if permissions are correct you should see 
something like:

"2021-06-24 20:33:14 UTC 0  :  : HINT:  Future log output will appear in 
directory "pg_log"."

If that's the case, then look in /awips2/data/pg_log/postgres-Thursday.log

Can you attach that file for us to take a look at?

Can you also show the output of /etc/sysconfig/network - that is where it is 
looking for the networking variable and if it is set to no, that is why it's 
failing and you may need to change your network settings.

There may need to make some modifications to your /etc/hosts and 
/awips2/data/pg_hba.conf files as well depending on your setup. 


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: WDS-351489
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.