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.
Gerry, > We're seeing some anomolous data transport times between the above > mentioned systems. According to some of our internal (SCOOP) metrics, > we're seeing data flow from weather.renci.org to scoop.cct.lsu.edu in > minutes (or less) while it's taking hours to get to sasquatch... > > Any thoughts for what I should look at? Execute a "notifyme" on Sasquatch, requesting notifications from weather.renci.org. Use verbose logging to the standard error stream ("-vl-" option). Do the timestamps on the log messages and the creation-times of the data-products indicate a large latency? Is the clock on Sasquatch correct? Is the clock on Weather correct? > Thanks, gerry > -- > Gerry Creager -- address@hidden > Texas Mesonet -- AATLT, Texas A&M University > Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983 > Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843 Regards, Steve Emmerson Ticket Details =================== Ticket ID: QBO-577023 Department: Support LDM Priority: Normal Status: Closed