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: > We are still seeing this problem, and it seems to be getting worse. But > it is always just the NEXRAD3 feed. I took iddb.unidata.ucar.edu out of > our ldmd.conf file, but it did not make any difference. Any ideas? I suggest trying the following test: - comment out all of the NEXRAD3 feed REQUESTs in your LDM configuration file, ~ldm/etc/ldmd.conf Leave the other REQUESTs in-place. - add new, redundant REQUESTs for NEXRAD3 as follows: REQUEST NEXRAD3 ".*" idd.ssec.wisc.edu REQUEST NEXRAD3 ".*" idd.tamu.edu Your machines should already be ALLOWed to REQUEST from these two IDD relays, so the switch should go without any drama. 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: TML-937455 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.