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 Jordi, re: we've been waiting for you... > Yes, you're right! I've installed the software using this manual: > > http://www.unidata.ucar.edu/software/ldm/ldm-6.6.5/basics/source-install-steps.html Very good. re: > but now I don't really know how to test if everything is correct, that's > why I was asking about the config file. Is it correct as it is? How can I > test if everything's OK? The ldmd.conf file that you sent us is syntactically correct. The REQUESTs you have for CONDUIT data: REQUEST CONDUIT "(prod/gfs.*pgrb2.*[0]$)" idd.unidata.ucar.edu REQUEST CONDUIT "(prod/gfs.*pgrb2.*[1]$)" idd.unidata.ucar.edu REQUEST CONDUIT "(prod/gfs.*pgrb2.*[2]$)" idd.unidata.ucar.edu REQUEST CONDUIT "(prod/gfs.*pgrb2.*[3]$)" idd.unidata.ucar.edu REQUEST CONDUIT "(prod/gfs.*pgrb2.*[4]$)" idd.unidata.ucar.edu REQUEST CONDUIT "(prod/gfs.*pgrb2.*[5]$)" idd.unidata.ucar.edu REQUEST CONDUIT "(prod/gfs.*pgrb2.*[6]$)" idd.unidata.ucar.edu REQUEST CONDUIT "(prod/gfs.*pgrb2.*[7]$)" idd.unidata.ucar.edu REQUEST CONDUIT "(prod/gfs.*pgrb2.*[8]$)" idd.unidata.ucar.edu REQUEST CONDUIT "(prod/gfs.*pgrb2.*[9]$)" idd.unidata.ucar.edu will work IF there is both forward and reverse DNS for machine. In an earlier email, you wrote that your machine will have the following fully qualified name and IP address: eady.uib.es <-> 130.206.30.86 A quick check to see if there is forward and reverse DNS for this machine shows that there is not, or, at least, the IP address you sent previously does not match the DNS record for eady.uib.es: % nslookup eady.uib.es Server: 192.168.72.2 Address: 192.168.72.2#53 Non-authoritative answer: Name: eady.uib.es Address: 130.206.76.191 % nslookup 130.206.30.86 Server: 192.168.72.2 Address: 192.168.72.2#53 ** server can't find 86.30.206.130.in-addr.arpa.: NXDOMAIN BUT, forward and reverse DNS does exist for the following pair: eady.uib.es <-> 130.206.76.191 The questions for you now are: - is 130.206.30.86 the correct IP address for your new machine? If yes, then you need to work with your networking folks to get forward and reverse DNS setup for this machine. - if no, is 130.206.76.191 the correct IP for your new machine? If yes, forward and reverse DNS are setup correctly, and your machine should be able to REQUEST data from idd.unidata.ucar.edu. re: how to test if your machine can REQUEST data from an upstream LDM Do the following: <login as the user 'ldm' on your LDM machine> notifyme -vl- -f CONDUIT -h idd.unidata.ucar.edu If you are ALLOWed, 'notifyme' should return back a line that looks something like: Apr 29 19:23:39 notifyme[16887] NOTE: NOTIFYME(idd.unidata.ucar.edu): OK If 'notifyme' does not return a line that looks like this, there is a problem somewhere, and the first guess would be that there is not forward and reverse DNS for your machine. re: > Thanks for your attention. Best regards, 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: NZC-887525 Department: Support IDD Priority: Normal Status: Closed