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

Re: 20020213: [Fwd: Re: [Fwd: 20020207: missing products]]

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: Re: 20020213: [Fwd: Re: [Fwd: 20020207: missing products]]
  • Date: Thu, 14 Feb 2002 12:00:33 -0700
On Feb 13, 12:14pm, Unidata Support wrote:
> Subject: 20020213: [Fwd: Re: [Fwd: 20020207: missing products]]
> >From: Harry Edmon <harry>
> >Organization: U. Washington
> >Keywords: 200202112021.g1BKLkx24875 LDM

Harry,

It looks like both air and sunny.atmos are having connection problems
according to the LDM logs on thelma;

> Feb 14 12:38:35 thelma sunny(feed)[17899]: topo:  sunny.atmos NMC2
> Feb 14 12:38:35 thelma sunny(feed)[17902]: topo:  sunny.atmos NMC2
> Feb 14 12:38:35 thelma sunny(feed)[17903]: topo:  sunny.atmos NMC2
> Feb 14 12:38:35 thelma sunny(feed)[17901]: topo:  sunny.atmos NMC2
> Feb 14 12:38:35 thelma sunny(feed)[17900]: topo:  sunny.atmos NMC2
> Feb 14 14:39:44 thelma air(feed)[18157]: topo:  air.atmos NMC2
> Feb 14 14:39:45 thelma air(feed)[18159]: topo:  air.atmos NMC2
> Feb 14 14:39:45 thelma air(feed)[18161]: topo:  air.atmos NMC2
> Feb 14 14:39:46 thelma air(feed)[18160]: topo:  air.atmos NMC2
> Feb 14 14:39:47 thelma air(feed)[18158]: topo:  air.atmos NMC2
> Feb 14 15:21:20 thelma air(feed)[18267]: topo:  air.atmos NMC2
> Feb 14 15:21:21 thelma air(feed)[18268]: topo:  air.atmos NMC2
> Feb 14 15:38:27 thelma sunny(feed)[18290]: topo:  sunny.atmos NMC2
> Feb 14 15:38:28 thelma sunny(feed)[18291]: topo:  sunny.atmos NMC2
> Feb 14 15:38:28 thelma sunny(feed)[18294]: topo:  sunny.atmos NMC2
> Feb 14 15:38:28 thelma sunny(feed)[18293]: topo:  sunny.atmos NMC2
> Feb 14 15:38:28 thelma sunny(feed)[18292]: topo:  sunny.atmos NMC2
> Feb 14 16:31:52 thelma air(feed)[18422]: topo:  air.atmos NMC2
> Feb 14 16:31:53 thelma air(feed)[18421]: topo:  air.atmos NMC2
> Feb 14 16:31:53 thelma air(feed)[18424]: topo:  air.atmos NMC2
> Feb 14 16:31:53 thelma air(feed)[18423]: topo:  air.atmos NMC2
> Feb 14 16:31:53 thelma air(feed)[18425]: topo:  air.atmos NMC2
> Feb 14 16:40:50 thelma sunny(feed)[18446]: topo:  sunny.atmos NMC2
> Feb 14 16:40:51 thelma sunny(feed)[18448]: topo:  sunny.atmos NMC2
> Feb 14 16:40:52 thelma sunny(feed)[18450]: topo:  sunny.atmos NMC2
> Feb 14 16:40:52 thelma sunny(feed)[18447]: topo:  sunny.atmos NMC2
> Feb 14 16:40:52 thelma sunny(feed)[18449]: topo:  sunny.atmos NMC2
> Feb 14 18:39:34 thelma air(feed)[18692]: topo:  air.atmos NMC2
> Feb 14 18:39:34 thelma air(feed)[18693]: topo:  air.atmos NMC2
> Feb 14 18:39:34 thelma air(feed)[18694]: topo:  air.atmos NMC2

and there seems to be a periodicity to the failures on sunny and to a
lesser degree on air.

I've looked around a bit on air and don't find anything obvious.  The SE
Toolkit usually shows a moderate or severe lack of memory on the system,
but otherwise OK.  I have a question about the network interfaces and the
split between 89, 175 and 176 subnets.  Is this for load balancing like
DNS round-robin, or to keep LDM or lab data off of a departmental network?

I'm going to look at why ~40 minutes after the hour is a point at which
a fair number of connection issues occur.

mike