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

[LDM #HMA-788722]: LDM problem

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.

  • Subject: [LDM #HMA-788722]: LDM problem
  • Date: Mon, 24 Dec 2007 08:54:33 -0700
John,

> In the hour since I reconfigured adiabat to pull only NEXRAD2
> products, it hasn't ingested any other than the handfull it did
> initially, at least according to 'ldmadmin watch'.
> Because of that I'm less inclined to blame bandwidth for the
> problem.  I still can't figure out why LDM refuses to pull the data
> from idd.unidata.ucar.edu.

I think NEXRAD2 data is flowing from idd.unidata to Adiabat but that
the data is too old and is being rejected.  This is consistent with
the output from the NEXRAD2, downstream LDM on Adiabat when sent
a USR2 signal.

I'm concerned about overlap in the REQUEST entries in the LDM
configuration-file.  REQUEST entries should either be disjoint in
the data that they request or identical: there should be no overlap;
otherwise, more bandwidth than necessary might be used.  I don't
know if this is the case with your entries because I don't know
what data the upstream LDM-s have.  If I had to, however, I would
modify the entries to the following:

request GEM ".*" ldm.meteo.ec.gc.ca
request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" marconi.rwic.und.edu
request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" 129.15.194.231
request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" 129.15.194.232
request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" 129.15.194.233
request EXP     "^IA\.rwis......\.sao"  mesonet.agron.iastate.edu
request EXP     "^IA\.snet......\.sao"  mesonet.agron.iastate.edu
request EXP ".*" pircsl4.agron.iastate.edu
request GPS ".*" suomildm1.cosmic.ucar.edu
request CONDUIT "[09]$" idd.unidata.ucar.edu
request CONDUIT "[18]$" idd.unidata.ucar.edu
request CONDUIT "[27]$" idd.unidata.ucar.edu
request CONDUIT "[36]$" idd.unidata.ucar.edu
request CONDUIT "[45]$" idd.unidata.ucar.edu
request NEXRAD2 ".*" idd.unidata.ucar.edu

The modifications are to the "ALL" request to the 129.15.194.*
hosts to exclude the data that's being requested from elsewhere.

I notice that Adiabat is currently received NEXRAD2 data OK.
Please keep an eye on it and keep me apprised.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: HMA-788722
Department: Support LDM
Priority: Normal
Status: On Hold