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 Carol and Matthew, re: > Any idea when the AMPS feed will be available again? The problem of not being able to REQUEST an LDM feed from MMM is not on our side; the LDM is running on antidd.ucar.edu, but it is not able to contact the LDM on the MMM machine, pine.mmm.ucar.edu. I just sent an email to Jordan Powers and Kevin Manning asking if they know of any changes that were made on the MMM side about a month to a month and a half ago. re: > Were you able to connect aws.ssec.wisc.edu? Yes, the LDM on antidd.ucar.edu can contact aws.ssec.wisc.edu. We are not seeing any data from the REQUEST, however. Here are our LDM configuration file, ~ldm/etc/ldmd.conf, REQUEST lines: REQUEST EXP "^(USAP)" pine.mmm.ucar.edu REQUEST EXP "^(USAP|ANT|ANSP)" aws.ssec.wisc.edu REQUEST EXP "^SSEC_NAWIPS_AMRC-ARCTIC_4KM" aws.ssec.wisc.edu Please advise if the REQUESTs to aws.ssec.wisc.edu need to be updated. > Thanks, > Carol > > Carol Costanza > Antarctic Meteorological Research Center > University of Wisconsin-Madison Space Science and Engineering Center > 1225 W Dayton St, Rm 947, Madison, WI 53706 > Email: address@hidden > Web: http://amrc.ssec.wisc.edu > > On 09/24/2015 01:37 PM, Carol Costanza wrote: > > OK I just updated the ldmd.conf and restarted ldm > > > > Thanks, > > Carol > > > > Carol Costanza > > Antarctic Meteorological Research Center > > University of Wisconsin-Madison Space Science and Engineering Center > > 1225 W Dayton St, Rm 947, Madison, WI 53706 > > Email: address@hidden > > Web: http://amrc.ssec.wisc.edu > > > > On 09/24/2015 01:33 PM, Unidata IDD Support wrote: > >> Hi Carol, > >> > >> re: > >>> We are getting no denying connection from antidd.ucar.edu. I found the > >>> logs in /var/log/messages. > >>> > >>> We are getting some from motherloade.ucar.edu > >>> > >>> Sep 24 16:41:57 aws ldmd[42609] NOTE: Denying connection from > >>> "motherlode.ucar.edu" because not allowed > >> Ah Ha! This is because 'antidd' is an alias for 'motherlode', and it > >> looks > >> like DNS is resolving to 'motherlode' instead of 'antidd'. > >> > >> re: > >>> Do you have any other ideas to change the ALLOW for antidd? Should I > >>> try > >>> typing in the numerical IP address? > >> Yes. Please change your allow to: > >> > >> ALLOW ANY ^(antidd|motherlode)\.ucar\.edu$ .* > >> > >> and then restart the LDM on aws.ssec.wisc.edu. > >> > >> After the ALLOW is cleared up, lets work on your LDM logging problem. > >> > >> re: > >>> Just in case you want to check your request for aws: > >>> > >>> aws.ssec.wisc.edu - 128.104.109.234 > >> Our REQUEST lines to 'aws' are: > >> > >> REQUEST EXP "^(USAP|ANT|ANSP)" aws.ssec.wisc.edu > >> REQUEST EXP "^SSEC_NAWIPS_AMRC-ARCTIC_4KM" aws.ssec.wisc.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: BBX-177142 > >> Department: Support IDD > >> Priority: Normal > >> Status: Closed > >> > > > > 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: BBX-177142 Department: Support IDD Priority: Normal Status: Closed