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 Gyorgyi, re: > Thank you so much! No worries. re: > Neil (Smith of TAMU ATMO) always did the first kind, and I have just > continued with that practice. I thought that this would be the case. re: > We don't have PRIMARY or ALTERNATE at the end of the line. > Sometimes it could be useful, though. I agree with you, but the LDM developer pursued a different course... re: > Maybe I should try the second option with certain products. The redundancy has to with feeds, not specific products. re: > Sometimes for no obvious reason some products - especially models, gfs and > nam typically- just stop coming or get blotchy. > I could never figure out why. Second option could be a tool in my hand for > those troublesome days. I just took a look and saw that none of your machines are reporting real-time IDD stats, or, at least, if they are reporting, they are reporting using some other name(s). Reporting real time stats helps us to troubleshoot when feed problems arise, so I want to strongly encourage you to change the configuration on your machines to report those stats. If you aren't reporting stats, it is probably due to one or two different situations: - the 'EXEC "rtstats ..."' line in the LDM configuration file, ~ldm/etc/ldmd.conf is commented out If this is the case, simply uncomment the line and stop/restart your LDM. - if the 'EXEC "rtstats ..."' line is not commented out, then it should mean that the local, department, college or university firewall is not allowing outbound traffic to port 388 on our rtstats.unidata.ucar.edu machine This would not be usual given that the firewall(s) are configured to ALLOW LDM REQUESTs from both UCAR and Penn State machines, but it is possible. re: > Anyways, thank you so much for your help, No worries. 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: SER-849220 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.