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: > I have not been getting any data from UNIWISC for the last day. Is > unidata2-new.ssec.wisc.edu still the right host the feed? Yes, idd.ssec.wisc.edu (aka unidata2-new.ssec.wisc.edu) is still a viable top level IDD relay. I just checked and see that the real server node of the idd.unidata.ucar.edu relay cluster that is trying to service the feed REQUEST from idd.ssec.wisc.edu is throwing errors related to the LDM registry, and this is likely the cause of data not being relayed to idd.ssec.wisc.edu. I am alerting Steve E. to this problem so that he can look at the situation in detail. In the interim, I setup a redundant feed for UNIWISC on idd.ssec.wisc.edu to one of the front-end accumulators to idd.ssec.wisc.edu, and that REQUEST is being serviced so you should once again receive UNIWISC products. 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: MGE-391500 Department: Support IDD Priority: Normal Status: Open