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

[IDD #NDK-473548]: Missing American radars

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: [IDD #NDK-473548]: Missing American radars
  • Date: Tue, 16 Aug 2011 12:59:52 -0600
Hi again Luc,

I got a call from Jonathan in netops in Environment Canada (EC) yesterday 
evening
at 8:41 pm MDT regarding the ingest problems being seen for U.S. radar.
The message was more-or-less what we talked about yesterday, so I am left
assuming that there is still a problem.

In order to troubleshoot things here in UCAR/Unidata, we need more information:

- what is the fully qualified name of the EC machine that is requesting
  the radar data?

- what does the LDM log file indicate the problem is?

- how long has EC noticed the problem?

Comments:

- the toplevel IDD relay node named idd.unidata.ucar.edu is actually a
  cluster of machines; this makes tracing down problems harder when we
  don't know the name of the downstream machine (i.e., the EC machine)

- I reviewed the log files on all of the machines in our idd.unidata.ucar.edu
  cluster, and think that your machine is may be named ecdor130.cmc.ec.gc.ca.
  Is this correct?

  If this is correct, we are _not_ seeing any problems with the connections
  to your machine, which, in turn, should mean that the problem is on
  the EC side.

- troubleshooting this problem is made more difficult by your machine not
  providing real-time statistics back to us.  Would it be possible for
  you (EC) to start providing real-time stats from the machine that
  is having problems?

  This would allow us to compare receipt statistics on your machine with
  those on the real server node of our cluster that is providing the data
  and to compare your receipt values (volume, number of products, latency,
  etc.) against other machines that are also receiving data from the
  same machine in our cluster.

NB: if you are not the appropriate technical contact at EC, please forward
this email to him/her.

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