Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
= On Tue, Aug 26, 2014 at 12:25 PM, <admin@xxxxxxxx> wrote: > > ldmd.log had errors related to the decoders, pnga2area etc. Had to > explicitly > > call them with the path /usr/local/ldm/decoders/pnga2area and they ran. > > That's an environment variable maybe? > Yes, ~ldm/decoders is not in $PATH, this is a mistake and has been corrected for the next release. > > Now QPID shows no msgs incrementing. > > > > [root@awips2-edex edex]# ps -ef | grep edexBridge > ldm 21210 21207 0 14:06 ? 00:00:00 edexBridge -s 127.0.0.1 > root 22702 13225 0 14:24 pts/0 00:00:00 grep edexBridge > [root@awips2-edex edex]# > > > > that IP address correct on edexBridge? Had to set that manually the setup > didn't. > The EXEC line in ~ldm/etc/ldmd.conf should contain the fully qualified domain name of the EDEX server. I fear that a lot of name resolving is going on, but I'm not certain. Change it to a name instead of an IP address and restart EDEX and the LDM to see.
awips2-users archives: