[LDM #YOW-752087]: LDM transfer mode / terminating

> "it" referring to the upstream servers (serving the data).  Usually one, but 
> sometimes both.  Just over the night, I noticed it happened again after 15 
> hours of running.  And there are a bunch of defunct ldm processes.
> 
> 10383 ?        Ss     0:01 ldmd -I 0.0.0.0 -P 388 -M 256 -m 3600 -o 1800 -q 
> /opt/ldm/var/queues/ldm.pq /opt/ldm/etc/ldmd.conf
> 10386 ?        S      0:03  \_ rtstats -h rtstats.unidata.ucar.edu
> 10387 ?        S      7:14  \_ ldmd -I 0.0.0.0 -P 388 -M 256 -m 3600 -o 1800 
> -q /opt/ldm/var/queues/ldm.pq /opt/ldm/etc/ldmd.conf
> 10388 ?        S      0:00  \_ ldmd -I 0.0.0.0 -P 388 -M 256 -m 3600 -o 1800 
> -q /opt/ldm/var/queues/ldm.pq /opt/ldm/etc/ldmd.conf
> 11872 ?        Z      0:00  \_ [ldmd] <defunct>
> 11874 ?        Z      0:00  \_ [ldmd] <defunct>
> 11889 ?        Z      0:00  \_ [ldmd] <defunct>
> 11897 ?        Z      0:00  \_ [ldmd] <defunct>
> 11898 ?        Z      0:00  \_ [ldmd] <defunct>
> 11905 ?        Z      0:00  \_ [ldmd] <defunct>
> 11915 ?        Z      0:00  \_ [ldmd] <defunct>

The log messages from your upstream LDM mean that it received a request for 
data from a downstream host that was identical to a feed it was already sending 
that host.

This could be due to several things. Possibilities include
    1) Duplicate or overlapping REQUEST entries in the downstream LDM's 
configuration-file;
    2) Multiple downstream LDM-s behind a network address translation (NAT) 
device making the same request;
    3) The connection with the downstream LDM getting broken but the upstream 
LDM not being notified.

We've seen #2 many times. The log message should tell you the IP address of the 
downstream host.

> Also, I'm on version 6.13.7.54 on CentOS 7.9

Hmm... alpha/beta versions of the LDM aren't intended for general use.

Can you upgrade to version 6.13.13?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: YOW-752087
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.