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 again (again) Mike, The output from the LDM utility 'uldbutil' on the real-server backend machine that is feeding vulcan is reporting that the feed connection is in secondary mode: 32242 6 feeder weather.uwyo.edu 20190829215130.351585 TS_ENDT {{NIMAGE, ".*"}} alternate What other NIMAGE feed REQUEST(s) do you have in place on vulcan? Why is he asking this? If you have a ".*" REQUEST for NIMAGE to different upstream sites, your problem could possibly be explained by the LDM flipping between the two different upstream sites, and this could result in not receiving some products if the set of products being REQUESTed is different on the upstream machines. What I am driving at is - if you have: REQUEST NIMAGE ".*" idd.unidata.ucar.edu and REQUEST NIMAGE ".*" <upstream host that has only the NOAAPort GINI content of NIMAGE> You will experience problems in getting all of the products from idd.unidata.ucar.edu Please send us vulcan's LDM configuration file as an attachment. 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: CBT-761337 Department: Support LDM 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.