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

[LDM #CSZ-262645]: errant LDM REQUESTs on sirocco.srcc.lsu.edu

Hi David and Yixin,

Recap of phone conversations with David:

1) The root causes of the data ingest-related problems seen on both
   sirocco and pavan turned out to be the HP router that they were
   both connected to.  As soon as sirocco's and pavan's network
   connections were moved to a different router, the repeated
   data REQUESTs to idd.unidata.ucar.edu and idd.ssec.wisc.edu
   disappeared, AND the data latencies being reported back to
   rtstats.unidata.ucar.edu dropped to zero.  Success!

2) the Novra S300 was power cycled to see if data ingest on
   mistral could be improved.

   Data ingest on mistral _was_ improved, but it is uncertain if
   the improvement was realized after moving sirocco and pavan to
   a new router, or after power was cycled on the S300 (the timing
   is uncertain).

3) As per David and my phone conversation, I installed LDM-6.11.2
   on both sirocco and mistral.

   mistral is now running the combined NOAAPort ingest processes
   contained in LDM-6.11.2 (i.e., noaaportIngester instead of
   dvbs_multicast and readnoaaport).  NOAAPort ingestion and relay
   appears to be working well now.  The proof can be seen in a comparison
   of datastream volumes between mistral and a non-LSU/SRCC ingest machine
   like jackie.unidata.ucar.edu.  Example:

NEXRAD3 ingest volume on mistral:

NEXRAD3 ingest volume on jackie.unidata.ucar.edu:

It appears that LDM-related things are now working correctly in SRCC!


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: CSZ-262645
Department: Support LDM
Priority: Normal
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.