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.
Adam, > I stand corrected.... > > NLDN is also working....just didn't want long enough for the product to come > in/didn't see it right off the bat. > > I have also gotten 2 of these in about the last hour: > > Apr 17 20:03:41 tornado idd.cise-nsf.gov[22276] ERROR: readtcp(): select() > timeout on socket 5 > Apr 17 20:03:41 tornado idd.cise-nsf.gov[22276] ERROR: one_svc_run(): RPC > layer closed connection > Apr 17 20:03:41 tornado idd.cise-nsf.gov[22276] ERROR: Disconnecting due to > LDM failure; Connection to upstream LDM closed > Apr 17 20:03:41 tornado idd.cise-nsf.gov[22276] NOTE: LDM-6 desired > product-class: 20120417190341.076 TS_ENDT {{NEXRAD2|GEM|FNMOC|CONDUIT, > ".*"},{NONE, "SIG=2016e9a13c572e6707b0765b466ee2ea"}} > Apr 17 20:03:41 tornado idd.cise-nsf.gov[22276] NOTE: Upstream LDM-6 on > idd.cise-nsf.gov is willing to be a primary feeder In general, message like the above can be ignored unless you get a lot of them. They indicate that there was congestion in the network between idd.cise-nsf.gov and Tornado. > Strange thing is, I was running ldmadmin watch -f NEXRAD2 at the time and a > few products (4 total products from the two reconnects) did come through but > only at the exact instance the reconnect was made....then it stopped > again.....strange..... Would you please send me the output of the command "traceroute idd.cise-nsf.gov" executed by the LDM user on Tornado. > Adam Regards, Steve Emmerson Ticket Details =================== Ticket ID: XEI-555875 Department: Support LDM Priority: Normal Status: Closed