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

[IDD #NXZ-279916]: Fwd: LDM age?

Hi Gerry,

re:
> Peter Laws runs the 2 LDM nodes that generally feed the National
> Weather Center.

This is good to know.  I will update our site contact list to include
Peter.

re:
> We've been tweaking his requests ever since the NSF
> announcement. He just forwarded the following my way.
> 
> Note that the allows for his machines are:
> ALLOW   ANY-LIGHTNING-PCWS-WSI  ^ldmingest01\.nwc\.ou\.edu$
> ALLOW   ANY-LIGHTNING-PCWS-WSI  ^ldmingest02\.nwc\.ou\.edu$
> 
> Any suggestions on tweaks?

Is there additional information in the LDM log file for the machine
that is being denied?  Relevant log message included from below appears
to be:

Nov 20 10:02:22 ldmingest02 idd.tamu.edu[2219] ERROR: Disconnecting due to LDM 
failure; Upstream LDM says we're not allowed to receive requested products: 
20121120150222.810 TS_ENDT 
{{EXP|NXRDSRC|NEXRAD2|NEXRAD3|NPORT|NIMAGE|GEM|FNMOC|FAA604|DIFAX|NMC|FSL5|FSL4|FSL3|FSL2|WMO|SPARE|0x80000000,
 ".*"}}

For reference, I saw somewhat similar messages in the LDM queue on
the LDM node at California University of Pennsylvania (CALU).  There
their REQUESTs were being denied by idd.tamu.edu as being duplicates
even though their requests were definitely _not_ duplicates (I
setup their REQUESTs).

I'll have to get Steve involved in this one!

> 
> 
> ---------- Forwarded message ----------
> From: Peter Laws <address@hidden>
> Date: Tue, Nov 20, 2012 at 10:03 AM
> Subject: Re: LDM age?
> To: Gerry Creager <address@hidden>
> Cc: "Laufersweiler, Mark J." <address@hidden>, Karen Cooper
> <address@hidden>
> 
> 
> Also:
> 
> Nov 20 10:02:22 ldmingest02 idd.tamu.edu[2219] ERROR: Disconnecting
> due to LDM failure; Upstream LDM says we're not allowed to receive
> requested products: 20121120150222.810 TS_ENDT
> {{EXP|NXRDSRC|NEXRAD2|NEXRAD3|NPORT|NIMAGE|GEM|FNMOC|FAA604|DIFAX|NMC|FSL5|FSL4|FSL3|FSL2|WMO|SPARE|0x80000000,
> ".*"}}
> 
> Getting the same on the other node.
> 
> 
> On 11/20/12 09:58, Peter Laws wrote:
> >
> > That all worked (must remember to update config on the other node).
> >
> > Today I see that it's been nearly 24 h since either node got updated,
> > assuming I'm reading the last column correctly:
> >
> > Nov 20 15:58:03 pqmon NOTE: nprods nfree  nempty      nbytes  maxprods
> > maxfree  minempty    maxext  age
> > Nov 20 15:58:03 pqmon NOTE: 173035    48 1780042  7998294360    360216
> > 58   1592908    850256 85153
> >
> >
> >
> > On 11/15/12 13:35, Gerry Creager wrote:
> >>
> >> Order is no longer important, and PRIMARY||SECONDARY isn't either. I'd
> >> add something like
> >> REQUEST    GPS    ".*" idd.unidata.ucar.edu
> >> just for an alternate.
> >>
> >> gerry
> >>
> >> On Thu, Nov 15, 2012 at 11:41 AM, Peter Laws <address@hidden> wrote:
> >>>
> >>> On 11/15/12 11:37, Laufersweiler, Mark J. wrote:
> >>>>
> >>>>
> >>>> GPS only comes from one place and not getting MCIDAS from Unidata cuts 
> >>>> one
> >>>> machine hop out of the loop. Since UWisc is set to handle the load, if 
> >>>> the
> >>>> path to Unidata goes out, we still would at least get MCIDAS. Depends
> >>>> on how
> >>>> one wants to mitigate ones risk.
> >>>>
> >>>> I am no expert in the guts of the LDM, but I believe that the other
> >>>> advantage is the number of processes that can be spawned is limited per
> >>>> request process. While decoding of files and the number of children
> >>>> spawned
> >>>> is not an issue for your LDM, that you have a separate request spawning
> >>>> children for decodes, etc can be important for many.
> >>>>
> >>>
> >>>>> REQUEST         ANY-GPS-MCIDAS  ".*"    idd.unidata.ucar.edu
> >>>>> REQUEST         ANY-GPS-MCIDAS  ".*"    idd.tamu.edu
> >>>>> REQUEST         MCIDAS          ".*"    idd.aos.wisc.edu
> >>>>> REQUEST         GPS             ".*"    suomildm1.cosmic.ucar.edu
> >>>>> REQUEST         MCIDAS          ".*"    idd.ssec.wisc.edu
> >>>
> >>>
> >>>
> >>> OK - what would be a better way to organize this config then?  MCIDAS is
> >>> good per what you say, but what of GPS?
> >>>
> >>> Also, is order still important in these files?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Peter Laws / N5UWY
> >>> National Weather Center / Network Operations Center
> >>> University of Oklahoma Information Technology
> >>> address@hidden
> >>> College of Architecture, Regional and City Planning, MRCP '16
> >>> --------------------------------------------------------------------------
> >>> Feedback? Contact my director, Matt Younkins, address@hidden. Thank you!
> >
> >
> >
> 
> 
> --
> Peter Laws / N5UWY
> National Weather Center / Network Operations Center
> University of Oklahoma Information Technology
> address@hidden
> College of Architecture, Regional and City Planning, MRCP '16
> --------------------------------------------------------------------------
> Feedback? Contact my director, Matt Younkins, address@hidden. Thank you!
> 
> 

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: NXZ-279916
Department: Support IDD
Priority: Normal
Status: Open