[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #OVS-299210]: Problem w/ LDM: My end or downstream?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #OVS-299210]: Problem w/ LDM: My end or downstream?
  • Date: Thu, 24 May 2007 12:33:27 -0600
Gerry,

> Here's the downstream/client representative entry:
> 
> May 24 17:54:42 cl-t021-260cl bigbird.tamu.edu[29229] ERROR:
> Disconnecting due to LDM failure; Upstream LDM died
> May 24 17:54:46 cl-t021-260cl bigbird.tamu.edu[29229] NOTE: LDM-6
> desired product-class: 20070524165445.942 TS_ENDT {{NNEXRA D,
> ".*"},{NONE,  "SIG=84d8aff1abcdc834362afa9352d5fed7"}}
> May 24 17:54:46 cl-t021-260cl bigbird.tamu.edu[29229] NOTE: Upstream
> LDM-6 on bigbird.tamu.edu is willing to be an alternate  feeder
> May 24 17:54:47 cl-t021-260cl pqact[29226] INFO:      165
> 20070524165449.578 NNEXRAD 53742227  SDUS33 KDTX 241644 /pNMDDTX ! nids/
> May 24 17:54:47 cl-t021-260cl pqact[29226] INFO:                file:
> -close    data/gempak/nexrad/NIDS/DTX/NMD/NMD_20070524 _1644
> May 24 17:55:47 cl-t021-260cl bigbird.tamu.edu[29229] ERROR:
> Disconnecting due to LDM failure; Upstream LDM died

The above indicates that the downstream LDM couldn't receive any
data from the upstream LDM because the upstream LDM died for some
unknown reason.

> And bigbird, for this host:
> 
> May 24 17:57:50 bigbird rpc.ldmd[31090] NOTE: child 7627 exited with
> status 6

There's no log message from the upstream LDM corresponding to the
log messages from the downstream LDM.  I suspect, however, that the
upstream messages would be similar to the above and to the following:

> May 24 17:57:51 bigbird ip-72-55-137-133.static.privated[7722] NOTE:
> feed or notify failure; COMINGSOON: RPC: Timed out
> May 24 17:57:51 bigbird rpc.ldmd[31090] NOTE: child 7722 exited with
> status 3

This indicates that the upstream LDM couldn't notify the downstream
LDM that a data-product was ready to be sent (the connection is in
ALTERNATE mode) because the upstream LDM didn't receive a reply from
the downstream LDM in the time allotted by the RPC layer.

I suspect that the network between the upstream and downstream LDM-s
has insufficient bandwidth or is too congested.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: OVS-299210
Department: Support LDM
Priority: Normal
Status: Closed