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

[LDM #DQO-447584]: Odd error messages on latest LDM.

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 #DQO-447584]: Odd error messages on latest LDM.
  • Date: Mon, 16 Nov 2015 08:49:34 -0700
Hey Stonie,

[I drove your inquiry into our support system so that others can benefit. Hope 
you don't mind.]

The messages you see are normal. They're due to the LDM's ability to optimize 
which upstream LDM is in primary transfer mode and which is in alternate 
transfer mode. When the downstream LDM switches modes, it closes the existing 
connection and re-connects in the new mode. This causes the new upstream LDM 
process to terminate the previous one -- resulting in the messages you see.

This can happen as often as once per minute if the upstream LDMs are 
electronically close. But who cares?

> Steve and Tom - updated to 6.12.14, and with that update, started to see
> messages that had not seen before:
> 
> On the upstream node, I see this:
> 
> Nov 15 18:28:04 tomslunch journal: sandwich.dukeof.com(feed)[20074]
> NOTE: Starting Up(6.12.14/6): 20151115172803.168 TS_ENDT {{IDS|DDPLUS,
> ".*"}}, SIG=bda7626ed1e55676f04886017d975c68, Alternate
> Nov 15 18:28:04 tomslunch journal: sandwich.dukeof.com(feed)[20074]
> NOTE: topo:  sandwich.dukeof.com {{IDS|DDPLUS, (.*)}}
> Nov 15 18:29:03 tomslunch journal: sandwich.dukeof.com(feed)[20075]
> NOTE: [uldb.c:1529] Terminated obsolete upstream LDM
> (addr=155.155.155.16, pid=20074, vers=6, type=feeder, mode=alternate,
> sub=(20151115172803.168 TS_ENDT {{IDS|DDPLUS, ".*"}}))
> Nov 15 18:29:03 tomslunch journal: sandwich.dukeof.com(feed)[20074]
> NOTE: Exiting
> Nov 15 18:29:03 tomslunch journal: sandwich.dukeof.com(feed)[20076]
> NOTE: [uldb.c:1529] Terminated obsolete upstream LDM
> (addr=155.155.155.16, pid=20075, vers=6, type=feeder, mode=alternate,
> sub=(20151115181738.357 TS_ENDT {{IDS|DDPLUS, ".*"}}))
> Nov 15 18:29:03 tomslunch journal: sandwich.dukeof.com(feed)[20075]
> NOTE: Data-product with signature 890d17e053d69cdc31348f336ae29948
> wasn't found in product-queue
> Nov 15 18:29:03 tomslunch journal: sandwich.dukeof.com(feed)[20075]
> NOTE: Starting Up(6.12.14/6): 20151115181738.357 TS_ENDT {{IDS|DDPLUS,
> ".*"}}, SIG=890d17e053d69cdc31348f336ae29948, Alternate
> Nov 15 18:29:03 tomslunch journal: sandwich.dukeof.com(feed)[20075]
> NOTE: topo:  sandwich.dukeof.com {{IDS|DDPLUS, (.*)}}
> Nov 15 18:29:03 tomslunch journal: sandwich.dukeof.com(feed)[20075]
> NOTE: Exiting
> 
> Correspondingly, on the downstream node, I see this:
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: LDM-6 desired
> product-class: 20151115181638.093 TS_ENDT {{IDS|DDPLUS,  ".*"},{NONE,
> "SIG=890d17e053d69cdc31348f336ae29948"}}
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: LDM-6 desired
> product-class: 20151115181638.093 TS_ENDT {{IDS|DDPLUS,  ".*"},{NONE,
> "SIG=890d17e053d69cdc31348f336ae29948"}}
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: Upstream LDM-6 on
> 129.129.0.34 is willing to be an alternate feeder
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: Upstream LDM-6 on
> 129.129.0.34 is willing to be an alternate feeder
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: [svc_tcp.c:353] EOF
> on socket 3
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: one_svc_run(): RPC
> layer closed connection
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: Connection to
> upstream LDM closed: pid=20073
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: [svc_tcp.c:353] EOF
> on socket 3
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: one_svc_run(): RPC
> layer closed connection
> Nov 15 18:28:03 sandwich 129.129.0.34[14492] NOTE: Connection to
> upstream LDM closed: pid=20073
> ...
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: LDM-6 desired
> product-class: 20151115181738.357 TS_ENDT {{IDS|DDPLUS,  ".*"},{NONE,
> "SIG=890d17e053d69cdc31348f336ae29948"}}
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: LDM-6 desired
> product-class: 20151115181738.357 TS_ENDT {{IDS|DDPLUS,  ".*"},{NONE,
> "SIG=890d17e053d69cdc31348f336ae29948"}}
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: Upstream LDM-6 on
> 129.129.0.34 is willing to be an alternate feeder
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: Upstream LDM-6 on
> 129.129.0.34 is willing to be an alternate feeder
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: [svc_tcp.c:353] EOF
> on socket 3
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: one_svc_run(): RPC
> layer closed connection
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: Connection to
> upstream LDM closed: pid=20075
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: [svc_tcp.c:353] EOF
> on socket 3
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: one_svc_run(): RPC
> layer closed connection
> Nov 15 18:29:03 sandwich 129.129.0.34[14492] NOTE: Connection to
> upstream LDM closed: pid=20075
> ...
> 
> Any ideas?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: DQO-447584
Department: Support LDM
Priority: Normal
Status: Closed