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.
Marc, > I'm seeing the following type messages in our LDM logs: > > Feb 10 22:12:21 chinkapin idd[23418]: Desired product class: > 20070210214239.989 > TS_ENDT {{WMO, ".*"}} > Feb 10 22:12:21 chinkapin idd[23418]: Connected to upstream LDM-6 > Feb 10 22:12:21 chinkapin idd[23418]: Upstream LDM is willing to feed > Feb 10 22:13:01 chinkapin idd[23418]: ERROR: requester6.c:206: > Connection to ups > tream LDM closed > Feb 10 22:13:31 chinkapin idd[23418]: Desired product class: > 20070210214425.138 > TS_ENDT {{WMO, ".*"}} > Feb 10 22:13:31 chinkapin idd[23418]: Connected to upstream LDM-6 > Feb 10 22:13:31 chinkapin idd[23418]: Upstream LDM is willing to feed > Feb 10 22:14:18 chinkapin idd[23418]: ERROR: requester6.c:206: > Connection to ups > tream LDM closed > > connections keep dropping and reconnecting. Looks like this has been > going on for a while but only recently (past couple days) have we seen > that CONDUIT data seems to be missing on our LDM server. When I saw > these messages in our logs it seemed that this might be the culprit, but > when I checked our older logs, I see the "Connection to upstream LDM > closed" message going back at least a month. > > We're running LDM 6.0.14. We get our conduit feed from idd.cise-nsf.gov. LDM 6.0.14 is pretty old (it was released in 2003). There've been a lot of changes to the LDM since then -- some of which might resolve your problem. Can I convince you to install the latest version? Regards, Steve Emmerson Ticket Details =================== Ticket ID: PKD-657862 Department: Support LDM Priority: Normal Status: Closed