[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #LAB-620548]: ldm not downloading data



Hi Jordi,

re:
> We have advanced a bit but still not receiving data. Here it is the output
> for ldmping:
> 
> eady:~/data/data/conduit/gfs> ldmping idd.unidata.ucar.edu
> Oct 07 14:35:31 INFO:      State    Elapsed Port   Remote_Host
> rpc_stat
> Oct 07 14:35:31 INFO: Resolving idd.unidata.ucar.edu to 128.117.140.3 took
> 0.003736 seconds
> Oct 07 14:36:32 INFO: Resolving idd.unidata.ucar.edu to 128.117.140.3 took
> 0.001252 seconds
> Oct 07 14:37:32 INFO: Resolving idd.unidata.ucar.edu to 128.117.140.3 took
> 0.00157 seconds
> 
> It looks OK, but this is the output for notifyme:

Actually, this does not look OK.  A successful 'ldmping' would look like:

ldmping idd.unidata.ucar.edu
Oct 07 15:16:07 INFO:      State    Elapsed Port   Remote_Host           
rpc_stat
Oct 07 15:16:07 INFO: Resolving idd.unidata.ucar.edu to 128.117.140.3 took 
0.003426 seconds
Oct 07 15:16:07 INFO: RESPONDING   0.006607  388   idd.unidata.ucar.edu  

Your test did not get the RESPONDING message.

re:
> eady:~/data/data/conduit/gfs> notifyme -vl - -h idd.unidata.ucar.edu
> Oct 07 14:34:21 notifyme[19502] NOTE: Starting Up: idd.unidata.ucar.edu:
> 20141007143421.280 TS_ENDT {{ANY,  ".*"}}
> Oct 07 14:34:21 notifyme[19502] NOTE: LDM-5 desired product-class:
> 20141007143421.280 TS_ENDT {{ANY,  ".*"}}
> Oct 07 14:34:21 notifyme[19502] INFO: Resolving idd.unidata.ucar.edu to
> 128.117.140.3 took 0.002428 seconds
> Oct 07 14:34:21 notifyme[19502] ERROR: NOTIFYME(idd.unidata.ucar.edu): 7:
> Access denied by remote server
> 
> This last "access denied" is because of our configuration?

It is likely being caused by lack of reverse DNS (IP -> name).

re:
> The DNS address
> is still the same, but the IP address has changed from 130.206.76.191 to
> 130.206.30.83. I don't know if it can affect, I understand it is associated
> to eady.uib.es regardless of the address. Can you please give us some
> advice about what can be the problem?

Your new IP address does not resolve into any name:

% nslookup 130.206.30.83
Server:         128.117.140.56
Address:        128.117.140.56#53

** server can't find 83.30.206.130.in-addr.arpa.: NXDOMAIN

Without reverse DNS your feed REQUEST(s) will be denied.

Forward DNS, on the other hand, is correctly setup:

nslookup eady.uib.es
Server:         128.117.140.56
Address:        128.117.140.56#53

Non-authoritative answer:
Name:   eady.uib.es
Address: 130.206.30.83

The solution for the problem is to get your networking folks to
setup reverse DNS for your LDM machine.

re:
> Thanks,

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: LAB-620548
Department: Support IDD
Priority: Normal
Status: Closed