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 Marck, re: > [ldm@dma-ldm ~]$ notifyme -vl- -f ANY -h oliver.unidata.ucar.edu > Oct 28 18:56:27 notifyme[4176] NOTE: Starting Up: oliver.unidata.ucar.edu: > 20131028185627.331 TS_ENDT {{ANY, ".*"}} > Oct 28 18:56:27 notifyme[4176] NOTE: LDM-5 desired product-class: > 20131028185627.331 TS_ENDT {{ANY, ".*"}} > Oct 28 18:56:27 notifyme[4176] INFO: Resolving oliver.unidata.ucar.edu to > 128.117.156.17 took 0.22014 seconds > Oct 28 18:56:28 notifyme[4176] ERROR: NOTIFYME(oliver.unidata.ucar.edu): 7: > Access denied by remote server > Oct 28 18:56:53 notifyme[4176] NOTE: LDM-5 desired product-class: > 20131028185627.331 TS_ENDT {{ANY, ".*"}} > Oct 28 18:56:53 notifyme[4176] INFO: Resolving oliver.unidata.ucar.edu to > 128.117.156.17 took 0.028827 seconds > Oct 28 18:56:53 notifyme[4176] ERROR: NOTIFYME(oliver.unidata.ucar.edu): 7: > Access denied by remote server > Oct 28 18:57:18 notifyme[4176] NOTE: LDM-5 desired product-class: > 20131028185627.331 TS_ENDT {{ANY, ".*"}} > Oct 28 18:57:18 notifyme[4176] INFO: Resolving oliver.unidata.ucar.edu to > 128.117.156.17 took 0.019202 seconds > Oct 28 18:57:18 notifyme[4176] ERROR: NOTIFYME(oliver.unidata.ucar.edu): 7: > Access denied by remote server OK, good. I saw in the LDM log file on oliver that notifyme connection attempts were received and rejected between 12:59:23 and 13:01:54 MDT from a machine whose IP address is 206.48.100.228. Since a traceroute indicates that this machine is in Aruba, I am assuming that it is yours. Please let me know if it is not. Based on my assumption that 206.48.100.228 is your machine, I have added a special ALLOW for all non-restricted feeds on each of the real server nodes of our toplevel IDD relay, idd.unidata.ucar.edu. Please test that you can REQUEST data from our relay using: <as 'ldm' on your machine> notifyme -vl- -f ANY -h idd.unidata.ucar.edu After verifying that you are now properly ALLOWed to REQUEST data, please add the following REQUEST to your LDM configuration file, ~ldm/etc/ldmd.conf: REQUEST IDS|DDPLUS ".*" idd.unidata.ucar.edu NB: - after making _any_ change to the ~ldm/etc/ldmd.conf file, one must stop/start/restart the LDM for the change to take effect: <as 'ldm' on your machine> -- edit ~ldm/etc/ldmd.conf ldmadmin stop ldmadmin start OR ldmadmin restart After you LDM is running, you can test to see if you are receiving data using: <as 'ldm'> ldmadmin watch and/or notifyme -vl- -o 60 As soon as it has been verified that data is flowing, we can talk about what to do to process the data out of your LDM queue. 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: VRK-635010 Department: Support IDD Priority: Normal Status: Closed