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, A little while ago, we found a dead/unresponsive real-server backend node in the idd.unidata.ucar.edu cluster, and removed it. Tests run from machines remote from Unidata to which we have login access are now showing that they can REQUEST feeds from idd.unidata.ucar.edu. Can you, at your earliest convenience, try to see if you can once again get feeds from idd.unidata.ucar.edu? Before you change your LDM configuration file REQUEST(s), please try the following: <as 'ldm'> notifyme -vl- -f ANY -h idd.unidata.ucar.edu If this succeeds, you should be able to revert your feed REQUEST(s) back to idd.unidata.ucar.edu. Or, probably even better, you could replicate your feed REQUEST(s) and have one set request from idd.unidata.ucar.edu and the other from iddb.unidata.ucar.edu. 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: JXP-631388 Department: Support IDD Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.