[IDD #UJG-569115]: Alternate NOAAport data feed

Hi Theo,

re: origins of request for NOAAPort feeds
> Indeed, our request for the secondary feed is related to the ingest system
> failure that Alan Hall mentioned.

OK, the pieces of the puzzle are fitting together now :-)

re: try a 'notifyme' to idd.cise-nsf.gov
> I tried the above command and I don't seem to be getting anything:
> 
> [ldm2@NWS-LDM2 ldm2]$ bin/notifyme -vl- -f WMO -h idd.cise-nsf.gov
> Nov 25 06:53:21 notifyme[1151] NOTE: Starting Up: idd.cise-nsf.gov: 
> 20101125065321.805 TS_ENDT {{WMO,  ".*"}}
> Nov 25 06:53:21 notifyme[1151] NOTE: LDM-5 desired product-class: 
> 20101125065321.805 TS_ENDT {{WMO,  ".*"}}
> Nov 25 06:53:21 notifyme[1151] INFO: Resolving idd.cise-nsf.gov to 
> 192.12.209.62 took 0.000607 seconds
> Nov 25 06:54:11 notifyme[1151] NOTE: LDM-5 desired product-class: 
> 20101125065321.805 TS_ENDT {{WMO,  ".*"}}
> Nov 25 06:54:11 notifyme[1151] INFO: Resolving idd.cise-nsf.gov to 
> 192.12.209.62 took 0.000224 seconds

Hmm... in a previous email you mentioned that nws-ldm2 was doing NOAAPort
ingest on port 387.  Is it possible that you changed your LDM build to use
port 387 by default on this machine?  If yes, it would account for your
'notifyme' not connecting and the comment about portmapper in the 'ldmping'
output below:

> 
> I don't pretend to be an expert, so please pardon my lack of knowledge.  I
> did do an ldmping, and got the following:
> 
> [ldm2@NWS-LDM2 ldm2]$ bin/ldmping idd.cise-nsf.gov
> Nov 25 07:02:23 INFO:      State    Elapsed Port   Remote_Host           
> rpc_stat
> Nov 25 07:02:23 INFO: Resolving idd.cise-nsf.gov to 192.12.209.62 took 
> 0.000396 seconds
> Nov 25 07:02:35 ERROR:      NAMED  12.025216    0   idd.cise-nsf.gov  can't 
> contact portmapper: RPC: Timed out
> Nov 25 07:03:00 INFO: Resolving idd.cise-nsf.gov to 192.12.209.62 took 
> 0.000199 seconds

I looked through the LDM log file on idd.cise-nsf.gov for indications that
your machine requested information (the 'notifyme') and was being denied, but I
didn't see anything.  This tells me that the request never got to the LDM
on idd.cise-nsf.gov, hence my question about the port you are trying to use.

For reference:

- all machines participating in the IDD use port 388

- your ~ldm/etc/ldmd.conf can contain a REQUEST line that specifies
  the port to use.  For instance:

  request  WMO  ".*"  idd.cise-nsf.gov:388

I don't believe that 'notifyme' allows one to specify the port on
the command line, so if the LDM on the machine you ran the 'notifyme'
on was built to use port 387 by default, we would expect a failure.

re:
> We should be good on the forward and reverse DNS entries for nws-ldm2 though:
> $ dig nws-ldm2.hpcc.ercbroadband.org
> ;; ANSWER SECTION:
> nws-ldm2.hpcc.ercbroadband.org. 54191 IN A      64.147.208.204
> 
> $ dig -x 64.147.208.204
> ;; ANSWER SECTION:
> 204.208.147.64.in-addr.arpa. 86400 IN   PTR     
> nws-ldm2.hpcc.ercbroadband.org.

OK.  I just verified the same on idd.cise-nsf.gov, so DNS should not be a
problem.

re:
> Thanks for your help.
> Happy Thanksgiving to you as well. :-)

No worries, and thanks!

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