[LDM #LTH-656578]: decoders

Hi Marty,

re:
> After the reboot, I see data appearing in /data. However, I still don't see
> the result of the decoders.

After the modification to /etc/selinux/config (and an ensuing reboot) and 
/etc/rsyslog.conf, LDM logging started working, which is a good thing
since it let me know a lot of what was going on.  The ~ldm/logs/ldmd.log
file just after the reboot showed that decoders/<decoder> was not
being executed.

I modified all of the ~ldm/etc/pqact.* pattern-action files and removed
'decoders/' from PIPE actions.  After doing this, a number of the ERROR
messages in the LDM log file disappeared; but others remained.  To
investigate those ERRORs, I CDed to the ~ldm/decoders directory and
took a look at the set of decoders you had there... I found that
several that were to be executed out of a pattern-action file were
missing.  So, I copied all GEMPAK decoders to the ~ldm/decoders
directory:

cd ~ldm/decoders
cp /usr/local/gempak/NAWIPS/os/linux64/bin/dc* .

After doing this, I restarted the LDM and all of the ERROR messages
being caused from missing decoders went away.

I still see errors that need addressing:

 ...

Feb 21 22:39:04 titan 130.65.97.148[5973] NOTE: LDM-6 desired product-class: 
20120221213904.271 TS_ENDT {{LIGHTNING,  ".*"}}
Feb 21 22:39:04 titan ldm1.wdtinc.com[5974] NOTE: LDM-6 desired product-class: 
20120221213904.273 TS_ENDT {{EXP,  "pge/wrf"}}
Feb 21 22:39:04 titan 130.65.97.148[5973] ERROR: Disconnecting due to LDM 
failure; Upstream LDM didn't reply to FEEDME request; RPC: Authentication 
error; why = (authentication error 5)
Feb 21 22:39:04 titan 130.65.97.148[5973] NOTE: LDM-6 desired product-class: 
20120221213904.277 TS_ENDT {{LIGHTNING,  ".*"}}
Feb 21 22:39:04 titan 130.65.97.148[5973] ERROR: Disconnecting due to LDM 
failure; Upstream LDM didn't reply to FEEDME request; RPC: Authentication 
error; why = (authentication error 5)
Feb 21 22:39:04 titan ldm1.wdtinc.com[5974] ERROR: Disconnecting due to LDM 
failure; nullproc_6 failure to ldm1.wdtinc.com; RPC: Unable to receive; errno = 
Connection reset by peer

 ...

I believe that these errors are caused by:

- ldm1.wdtinc.com has no ALLOWs for your new machine

- rossby (130.65.97.148) does not have an ALLOW for LIGHTNING
  data for your new machine

I also see some unexpected directories in /data (e.g., /data/data)
that I believe are being caused by your setup.  The typical setup
for the LDM is to soft link ~ldm/data to a directory like /data/ldm
(or /machine/ldm, etc.).  The actions in the GEMPAK pattern-action
files then create /data/ldm/data and so on.  If you like, I am willing
to change the directory setup for your decoding.  Unfortunately, I
can do this right now as I have to leave to pick-up something.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: LTH-656578
Department: Support LDM
Priority: Normal
Status: Closed