[LDM #AET-991057]: LDM 6.4.4----two problems

Robert,

> Here are the errors from the upstream machine:
> 
> Mar 09 03:34:41 wxmcidas psnldm(feed)[5085]: up6.c:287: nullproc_6() failure 
> to psnldm.balloonfacility.org: RPC: Unable to receive; errno = Connection 
> reset by peer
> Mar 09 03:34:41 wxmcidas rpc.ldmd[29393]: child 5085 exited with status 5
> Mar 09 03:34:41 wxmcidas psnldm[19030]: ldm6_server.c:136: Restricting 
> request: 20060309032443.783 TS_ENDT {{CONDUIT,  ".*"},{NONE,  
> "SIG=42a66de4294053b81ab7dbe73f7bcabd"}} -> 20060309032443.783 TS_ENDT 
> {{CONDUIT,  ".*"}}
> Mar 09 03:34:43 wxmcidas psnldm(feed)[19030]: up6.c:334: Starting 
> Up(6.3.0/6): 20060309032443.783 TS_ENDT {{CONDUIT,  ".*"}}
> Mar 09 03:34:43 wxmcidas psnldm(feed)[19030]: topo:  
> psnldm.balloonfacility.org CONDUIT
> Mar 09 03:56:18 wxmcidas psnldm(feed)[19030]: up6.c:287: nullproc_6() failure 
> to psnldm.balloonfacility.org: RPC: Unable to receive; errno = Connection 
> reset by peer
> Mar 09 03:56:18 wxmcidas rpc.ldmd[29393]: child 19030 exited with status 5
> Mar 09 03:56:18 wxmcidas psnldm[19064]: ldm6_server.c:136: Restricting 
> request: 20060309033043.867 TS_ENDT {{CONDUIT,  ".*"},{NONE,  
> "SIG=ab3d73a9c923cae62de4dc92f66904b2"}} -> 20060309033043.867 TS_ENDT 
> {{CONDUIT,  ".*"}}
> Mar 09 03:56:20 wxmcidas psnldm(feed)[19064]: up6.c:334: Starting 
> Up(6.3.0/6): 20060309033043.867 TS_ENDT {{CONDUIT,  ".*"}}
> Mar 09 03:56:20 wxmcidas psnldm(feed)[19064]: topo:  
> psnldm.balloonfacility.org CONDUIT
> Mar 09 03:58:18 wxmcidas psnldm(feed)[19064]: up6.c:167: HEREIS: RPC: Unable 
> to send; errno = Broken pipe
> Mar 09 03:58:18 wxmcidas psnldm(feed)[19064]: up6.c:430: Product send 
> failure: Input/output error
> Mar 09 03:58:18 wxmcidas rpc.ldmd[29393]: child 19064 exited with status 6

The above indicates that the upstream LDM is being told by the operating-system 
that the connection was broken: in the first two cases because the TCP layer on 
the downstream host sent a "reset" control-message. In the last case no good 
reason for the disconnection was given.  Given the extensive use of the LDM, it 
seems unlikely that these disconnections are due to it, rather, it seems likely 
that they are due to either the network or the networking layers of the hosts 
in question.  You *might* be able to verify this by switching to a previous 
version of the LDM -- although the autoshifting feature in 6.4 might confuse 
the issue.

Incidentally, the timestamps on the two sets of log messages don't correlate.

Do you have a network administrator to whom you can take this problem?

> I haven't seen these types of errors before.
> 
> Thanks,
> Robert Mullenax
> NMSU/CSBF

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: AET-991057
Department: Support LDM
Priority: Normal
Status: On Hold