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.
Hi Gilbert, re: > The dish was running 6.12.14, all the others 16.12.13 at the time. > They are all on 6.12.14 now. > And yes, the exact same issue happened then as well. Only NEXRAD3 was > affected. The only thing I can think of is that the NEXRAD3 REQUEST to UW/AOS had become "stale" somehow. We have on occasion seen long standing connections from a downstream host to our IDD top level relay cluster simply stop moving data with no indications of there being any problems. A restart of the upstream LDM resulted in resumed data flow in pretty much all of the cases. Evidently your restart of your downstream LDM also resulted in a resumption of data flow, so that is an option. To be clear: we do _not_ know/understand why connections can sometimes get "stale". We see this very infrequently, but we know that it does happen. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: CHX-269374 Department: Support LDM Priority: Normal Status: Closed