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

19991005: thelma ldm

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: 19991005: thelma ldm
  • Date: Tue, 05 Oct 1999 14:00:05 -0600
>From: Harry Edmon <address@hidden>
>Organization: .
>Keywords: 199910051929.NAA04822

>I am having real problems getting products from thelma currently.  Do you see
>anyting unusual on your end?
>
>Here is my traceroute:
>
># traceroute thelma.ucar.edu
>traceroute to thelma.ucar.edu (192.52.106.21), 30 hops max, 40 byte packets
> 1  dustbuster-V3.cac.washington.edu (128.95.89.100)  1 ms  1 ms  1 ms
> 2  uwbr2-FE1-1-0.cac.washington.edu (140.142.153.24)  1 ms  1 ms  1 ms
> 3  adsgpop1-FE6-0-0.pnw-gigapop.net (198.32.171.1)  1 ms  1 ms  1 ms
> 4  cs-pos.sej.vbns.net (198.48.91.2)  3 ms  3 ms  4 ms
> 5  cs-atm0-0-21.ncar.vbns.net (204.147.129.169)  35 ms  34 ms  35 ms
> 6  thelma.ucar.edu (192.52.106.21)  36 ms  35 ms  35 ms
>
>
>pings are fine.
>
>
>--
>Dr. Harry Edmon                        E-MAIL: address@hidden
>(206) 543-0547                 FAX:    (206) 543-0308
>Dept of Atmospheric Sciences
>University of Washington, Box 351640, Seattle, WA 98195-1640
>

Harry,

I found that data was arriving at thelma with 1 hour latencies, so if you
were experiencing high latencies, this may have been the cause.
There were some gethostbyname failures in the log.

I have restarted the ldm and data seems to be catching up once again.

Steve Chiswell