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

[LDM #NDJ-862794]: Problems accessing data from Southern Region HQ LDM

Justin,

I don't like the fact that your LDM log file seems to have the following:

Jun 9 05:39:46 vm-lnx-ncodfdev srh-ls-cpnrs2.srh.noaa.gov [6649] INFO: 
Connected to upstream LDM-6 on host srh-ls-cpnrs2.srh.noaa.gov using port 388
Jun 9 05:39:46 vm-lnx-ncodfdev srh-ls-cpnrs2.srh.noaa.gov [6649] INFO: 
Connected to upstream LDM-6 on host srh-ls-cpnrs2.srh.noaa.gov using port 388*

Was this a cut/paste typo?

> Over the last week I've been working with Southern Region HQ to set up an
> LDM feed of some of their datasets from one of their servers to a system
> here at NCEP NCO in College Park. We're having quite a bit of trouble
> getting data flowing.
> 
> I've got a broad request statement in my ldmd.conf:
> 
> REQUEST    EXP    ".*"    srh-ls-cpnrs2.srh.noaa.gov
> 
> And see in our ldmd.log that we're able to connect:
> 
> Jun  9 05:39:46 vm-lnx-ncodfdev srh-ls-cpnrs2.srh.noaa.gov [6649] NOTE: LDM-6 
> desired product-class: 20140609043946.309 TS_ENDT {{EXP,  ".*"},{NONE, 
> "SIG=6f3190414235798983edbec116d30292"}}
> Jun  9 05:39:46 vm-lnx-ncodfdev srh-ls-cpnrs2.srh.noaa.gov [6649] NOTE: LDM-6 
> desired product-class: 20140609043946.309 TS_ENDT {{EXP,
> ".*"},{NONE,  "SIG=6f3190414235798983edbec116d30292"}}
> Jun  9 05:39:46vm-lnx-ncodfdev srh-ls-cpnrs2.srh.noaa.gov [6649] INFO: 
> Resolving srh-ls-cpnrs2.srh.noaa.gov to 216.38.81.29 took 0.000739 seconds
> Jun  9 05:39:46 vm-lnx-ncodfdev srh-ls-cpnrs2.srh.noaa.gov [6649] INFO: 
> Resolving srh-ls-cpnrs2.srh.noaa.gov to 216.38.81.29 took 0.000739 seconds
> Jun  9 05:39:46 vm-lnx-ncodfdev srh-ls-cpnrs2.srh.noaa.gov [6649] INFO: 
> Connected to upstream LDM-6 on host srh-ls-cpnrs2.srh.noaa.gov using port 388
> Jun  9 05:39:46 vm-lnx-ncodfdev srh-ls-cpnrs2.srh.noaa.gov [6649] INFO: 
> Connected to upstream LDM-6 on host srh-ls-cpnrs2.srh.noaa.gov using port 388*
> 
> 
> Southern Region has told us that their ldmd.conf is allowing ANY feedtype.
> I've also run a notifyme to see whats available on their server and do see
> new data:
> 
> [ldm@vm-lnx-ncodfdev logs]$ notifyme -v -f EXP -h srh-ls-cpnrs2.srh.noaa.gov 
> <http://srh-ls-cpnrs2.srh.noaa.gov>
> 
> Jun  9 17:41:39 vm-lnx-ncodfdev notifyme[6333] INFO:   138670 
> 20140609174130.571     EXP 000  COERR1CIX
> Jun  9 17:41:39 vm-lnx-ncodfdev notifyme[6333] INFO:   226731 
> 20140609174131.393     EXP 000  LRD_OMNI
> Jun  9 17:41:39 vm-lnx-ncodfdev notifyme[6333] INFO:   226731 
> 20140609174131.393     EXP 000  LRD_OMNI
> Jun  9 17:41:41 vm-lnx-ncodfdev notifyme[6333] INFO:   481418 
> 20140609174141.014     EXP 000  NAT_N0Q_201406091740.gif
> Jun  9 17:41:41 vm-lnx-ncodfdev notifyme[6333] INFO:   481418 
> 20140609174141.014     EXP 000  NAT_N0Q_201406091740.gif*
> 
> 
> So I see data in the LDM queue that we should be able to pull, but our LDM
> never receives it. Our network and system administrators at NCEP have taken
> a look at our ncodfdev system and firewalls, but don't see where this
> connection is being blocked. Is there any other troubleshooting that you
> can suggest that we run either on our end or the southern region side to
> see if we can determine where the issue is?
> 
> Thanks,
> Justin Cooke
> NCEP Central Operations

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NDJ-862794
Department: Support LDM
Priority: Normal
Status: Closed