[LDM #EKO-116885]: LDM 6.15.0.2

Hi Gilbert,

> It has a fatal issue. It will compile and initially run, but then, in my
> LDM logs, the feeds stop, and I see these error messages
...
> 20230708T053241.237513Z 10.11.2.50[1959939] requester6.c:make_request:221     
>   NOTE  Upstream LDM-6 on 10.11.2.50 is willing to be a primary feeder
> 20230708T053241.238703Z 10.11.2.50[1959937] requester6.c:make_request:221     
>   NOTE  Upstream LDM-6 on 10.11.2.50 is willing to be a primary feeder
> 20230708T053242.239847Z 10.11.2.50[1959939] svc_tcp.c:readtcp:363             
>   NOTE  EOF on socket 6
> 20230708T053242.239897Z 10.11.2.50[1959939] one_svc_run.c:one_svc_run:96      
>   NOTE  RPC layer closed connection on socket 6
> 20230708T053242.239922Z 10.11.2.50[1959939] LdmConfFile.c:requester_exec:925  
>   NOTE  Sleeping 60 seconds before retrying...
> 20230708T053242.240005Z 10.11.2.50[1959937] svc_tcp.c:readtcp:363             
>   NOTE  EOF on socket 6
> 20230708T053242.240030Z 10.11.2.50[1959937] one_svc_run.c:one_svc_run:96      
>   NOTE  RPC layer closed connection on socket 6
> 20230708T053242.240053Z 10.11.2.50[1959937] LdmConfFile.c:requester_exec:925  
>   NOTE  Sleeping 60 seconds before retrying...

Interesting. I'll investigate. Thanks for sending this in.

In the meantime, can you tell me if the downstream LDM processes in the above 
have a network address translation (NAT) device between them and 10.11.2.50? 

Also, were the two downstream LDM processes requesting the same or overlapping 
feedtypes from the upstream LDM?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: EKO-116885
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.