[LDM #HUD-735823]: LDM 6.13.7 configure issue

Scott,

> I ran the two commands you just showed, and I got 6.13.8, which is good for 
> the LDM version. I also ran the notifyme command, and I see nothing.

Our NOAAPort system has ingested the following:

20190305T203241.740440Z             notifyme[14583]      
notifyme.c:notifymeprog_5() INFO     3422943 20190305203241.738017 IDS|DDPLUS 
19744909  FOUS11 KWNO 052000 /pLAVUSA
20190305T210936.895206Z             notifyme[14583]      
notifyme.c:notifymeprog_5() INFO        4848 20190305210936.894954 IDS|DDPLUS 
19845216  FOUS11 KWBC 052109 /pQPFHSD
20190305T213231.379907Z             notifyme[14583]      
notifyme.c:notifymeprog_5() INFO     3394431 20190305213231.375720 IDS|DDPLUS 
19899896  FOUS11 KWNO 052100 /pLAVUSA
20190305T223437.443663Z             notifyme[14583]      
notifyme.c:notifymeprog_5() INFO     3423348 20190305223437.438728 IDS|DDPLUS 
20068638  FOUS11 KWNO 052200 /pLAVUSA
20190305T233238.161302Z             notifyme[14583]      
notifyme.c:notifymeprog_5() INFO     3423348 20190305233238.159029 IDS|DDPLUS 
20203337  FOUS11 KWNO 052300 /pLAVUSA

Note that one of these doesn't have the " /pLAV" suffix.

> Do you think it could be a hardware issue? We are AMD Ryzen 7, 32 GB RAM, 
> Intel Dual Ethernet Card, and a ethernet switch to split the NOAAPort feed.

Is there anything in the LDM log file from noaaportIngester(1) about missing 
data?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: HUD-735823
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.