[Support #CZG-556318]: can't flush connection: feed to downstream ldm broke

Neil,

> Upstream: coriolis.met.tamu.edu
> Downstream: megara.tamu.edu
> 
> Both ldm's at 6.8.1.
> 
> Getting these errors in upstream ldmd.log on coriolis for feed to local 
> downstream ldm on megara.
> 
> Apr 09 15:35:37 coriolis megara.tamu.edu(feed)[52531] NOTE: Starting 
> Up(6.8.1/6): 20130409143536.518 TS_ENDT {{IDS|DDPLUS,  ".*"}}, 
> SIG=8ce544ff51d6b86b5e5d09dfd43559a1, Primary
> Apr 09 15:35:37 coriolis megara.tamu.edu(feed)[52531] NOTE: topo:  
> megara.tamu.edu {{IDS|DDPLUS, (.*)}}
> Apr 09 15:36:51 coriolis megara.tamu.edu(feed)[52531] ERROR: Couldn't flush 
> connection; nullproc_6() failure to megara.tamu.edu: RPC: Unable to receive; 
> errno = Connection reset by peer
> Apr 09 15:36:52 coriolis megara.tamu.edu(feed)[64577] NOTE: Starting 
> Up(6.8.1/6): 20130409143651.494 TS_ENDT {{IDS|DDPLUS,  ".*"}}, 
> SIG=1cb73c312b9afbb150241e9ef347b5c0, Alternate
> Apr 09 15:36:52 coriolis megara.tamu.edu(feed)[64577] NOTE: topo:  
> megara.tamu.edu {{IDS|DDPLUS, (.*)}}
> Apr 09 15:37:53 coriolis megara.tamu.edu(feed)[64577] NOTE: feed or notify 
> failure; COMINGSOON: RPC: Unable to receive; errno = Connection reset by peer
> 
> What do these errors mean?

If Megara requests IDS|DDPLUS data from an LDM on a system other than Coriolis, 
then the log messages are likely due to the downstream LDM on Megamara deciding 
to switch its transfer-mode between ALTERNATE and PRIMARY. The switch requires 
that the connection be closed, which results in such log messages at the 
upstream LDM.

> Downstream reports he is ingesting data.  Currently there is no further 
> qualification of data reception.
> 
> Thanks,
> -Neil
> ---
> Neil Smith  address@hidden   979.845.6272
> Senior IT Specialist, Atmospheric Sciences, TAMU

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: CZG-556318
Department: Support LDM
Priority: Normal
Status: Closed