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 Harry, re: > idd.unidata.ucar.edu stopped feeding data to one of my data ingest system - > freshair2.atmos.washington.edu at 2044 PST (0444 UTC). However, it is still > feeding my other system - freshair1.atmos.washington.edu. I have switch > freshair2 to feed from SSEC and NSF until this problem is resolved. OK. I have been looking at the CONDUIT and IDS|DDPLUS latency plots for idd.unidata.ucar.edu and freshair2.atmos.washington.edu... I see a hiccup in CONDUIT latencies on freshair2 for both December 30 and 31 at approx. 4-8 UTC. The latency blip is matched on idd.unidata.ucar.edu for the 30th, but not the 31st. freshair2 shows the same "outage" (no latency information at least) for both CONDUIT and IDS|DDPLUS while freshair1 does not... very strange indeed. I will continue to look through the LDM log files on the various cluster nodes that comprise idd.unidata.ucar.edu to see if I can find anything clue as to why the 4-8 UTC outages occurred. 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: OCU-795540 Department: Support IDD Priority: Normal Status: Open